Repository navigation
curriculum(SEF5): competency-derived testing, design and review progression - #162
Merged
christophersesugh merged 1 commit intoNov 18, 2026
Conversation
Signed-off-by: Christopher S. Aondona <christohybrid185@gmail.com>
christophersesugh
force-pushed
the
curriculum/sef5-competency-derived-engineering-practice
branch
from
November 18, 2026 12:47
2cde443 to
f50540a
Compare
christophersesugh
deleted the
curriculum/sef5-competency-derived-engineering-practice
branch
November 18, 2026 12:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
M1 — SEF5 competency-derived software engineering practice review
Pinned main baseline:
23567c85e02c39ba4ac1773fdc4e5727e19c4471, after approved SEF4 #160.Review authority: temporary review protocol v1.0, deliberately unmerged draft PR #150, M0 inventory #152, binding OEE specs and the curriculum design guide.
Scope:
curriculum/SEF/SEF5.mdand its two directly related regression suites (tests/test_sef5_design_quality.py,tests/test_sef5_migration.py). No other course, program catalog, specification, architecture decision or public audit file changed. The PR targetsmaindirectly.1. Independent exit-competency reconstruction
A learner who has completed SEF2 must demonstrate the ability to make a deliberate, correct, reversible and independently reproducible engineering change to a real small Python CLI. This includes:
Comparative authority, not an imposed outline or accreditation standard:
pull_request_targetbehavior: read-only permissions, hostile contributed code and the danger of privileged workflow execution.Boundary: SEF2 owns programming, Python function/object basics and a beginner CLI. SEF5 owns quality of change and the evidence behind engineering decisions, not a second beginning-programming course. SEF9 owns project-level workflow, professional ethics, licensing, privacy, stakeholder accessibility and AI-assisted engineering governance. SEF10 independently integrates the complete program in a different bounded capstone. SEF5 teaches a readable, accessible review artifact of its own code but does not take over SEF9's wider professional-practice scope.
2. Outcome and assessment identity
The 15 current published outcome definitions (
SEF5-O1–O15) are byte-for-byte identical. The sevenSEF5-AS1–AS7assessment contracts (each Work, Criteria, Evidence and reviewer variation) are also byte-for-byte identical. No new outcomes, assessments, examination, compulsory application or readiness status is introduced. Existingdraft,v0.2.0, 10–12-week provisional duration, SEF2-only prerequisite, Python 3.11+ and offline-capable/no-paid-account route are unchanged.In particular, the existing AS4 20-run observation is retained as a specific published assessment obligation, not imposed as a universal per-course template. AS6 and AS7 already permit reuse of the same CLI code and prior evidence. The genuine independent reviewer required for the final handoff is not silently weakened into self-review, an imaginary peer, or a simulated hosted PR. Conversely, actual hosted CI and hosted Git accounts are not required.
3. Module-by-module realignment: mechanisms, dependency order and outcomes
The former course had 9 modules / 74 numbered lessons. A majority of the earlier
Maintainable Software,Design Boundaries,Code Maintenance,Software QualityandTested CLIcontent repeated the same interface/review/change concepts at differing textual depth without a new assessment capability. Similarly, testing and reliability were split across old M2 and M5, and a number of lessons were just isolated nouns (“Assertions,” “Refactoring,” “Logging,” “Code review”). No pedagogical evidence justified each repeated teaching boundary. A separate standalone quality module is warranted, but repeated initial explanations of coupling, interfaces or test layers are not.The replacement has 6 competency-owned modules, 51 explicitly described lessons, distributed
8/10/11/7/8/7. These counts are incidental to the ability and dependency reconstruction: there is no desired count or enforced numerical variation.unittestunit/real subprocess integration separation, negative input partitions, observed pre-fix failure, hypothesis-testing repair, temporary fixture state, injected clock/seed/order, actual flaky-test diagnosis, existing AS4 repeated-run exercise, and an application defect that corrected tests must still reject. Supports AS2 and AS4 without inventing a per-module test quota.qualityentry point, correct failure propagation, clean-checkout/Python/dependency reproduction, separate failing test and static-check fixtures, reviewed least-privilege workflow, the untrusted code versus privileged secrets boundary (includingpull_request_target), and honest local/hosted evidence distinction. Supports AS5.Every module has one nonempty mapping to existing published outcomes, distinct lesson tasks with falsifiable/observable cases, and optional formative practice. There are no invented resource or platform prerequisites.
4. Assessment evidence and validity
The outcomes O13–O15 are independently assessable by the existing AS7, not by a new ornamental module quiz. Source code, real output/status/persistence bytes, reviewer feedback and qualified claims remain inspection requirements. Structural coverage alone is not competency evidence.
5. Confirmed findings and dispositions
test_sef5_design_quality.pyandtest_sef5_migration.pyhard-coded nine modules; the former also froze titles. Resolve: test sequential structure regardless of count, mapped/current outcomes, individual described lessons, genuine prerequisite chain (Git and tests → refactoring → gates and review → final independently reviewed handoff), version/history and no fake hosted CI or paid gate.testedorverifiedstatus without real learner time and reviewer evidence.6. Cross-course effects, historical compatibility, verification
SEF2 continues to own basic Python, classes, validated file persistence and the beginner CLI; SEF5 reuses that actual prior artifact and increases engineering evidence rather than starting another CLI project. SEF9 continues to own planning, ethical responsibility, data stewardship, licenses, stakeholder communication and AI-assistant governance; local review quality is already a legitimate SEF5 competency, not a duplicate SEF9 professional curriculum. SEF10's capstone remains separate and requires actual prerequisite closure.
Verified against pinned
main:Learning outcomessection: byte-for-byte identical, 15 IDs.Required summative assessmentsthroughCompletion decision: byte-for-byte identical, seven complete published assessment contracts.CI is to be verified after PR creation. Academic text and green CI are not substitutes for independent learner review, provenance or pedagogical validation.
7. Maintainer approval, DCO, and next course
The GitHub connector writes unsigned API commits and cannot personally attest to the contributor's DCO. Before merging, the maintainer should verify the review and all checks, and squash these commits into one personally signed-off local commit in a clean checkout:
git fetch origin git switch curriculum/sef5-competency-derived-engineering-practice git pull --ff-only origin curriculum/sef5-competency-derived-engineering-practice git reset --soft 23567c85e02c39ba4ac1773fdc4e5727e19c4471 git commit -s -m "curriculum(SEF5): competency-derived engineering practice and review" git push --force-with-lease origin HEADKeep temporary draft PR #150 unmerged; it is the review protocol, not an integration branch. This course PR should merge to
mainonly after the required DCO and CI checks are green and the maintainer approves. Next review in M1 sequence after the merge: SEF8 — Mathematics for Numerical Computing & AI.