Repository navigation
curriculum(APP18): competency-derived JavaScript language and async evidence - #165
Merged
christophersesugh merged 1 commit intoNov 18, 2026
Merged
Conversation
…dence and cumulative utility Signed-off-by: Christopher S. Aondona <christohybrid185@gmail.com>
christophersesugh
force-pushed
the
curriculum/app18-competency-first-reassessment
branch
from
November 18, 2026 12:57
ee8e1ee to
3ee4eb2
Compare
christophersesugh
deleted the
curriculum/app18-competency-first-reassessment
branch
November 18, 2026 13:00
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.
M3 / APP18 — competency-first academic reassessment
1. Baseline, authority and scope
mainatc0a01421b4c95bc661bd785121e3b737d7964f42after approved APP17 PR curriculum(APP17): competency-derived semantic HTML/CSS and cumulative evidence #163 was merged, with approved APP1 PR curriculum(APP1): competency-derived Web foundations realignment #161 already present. Head:curriculum/app18-competency-first-reassessment.v0.2.0,draft, 12 modules, 82 numbered instructional entries, 11 observable outcomes, five required summative assessments. Direct prerequisiteSEF10; provisional 12–16 weeks/10–14 focused hours per week.curriculum/APP/APP18.mdalone. No SEF, APP17/APP19/APP21, AI/SYS, APP program catalog, normative spec, prereq, classification, course version, duration or readiness change. No simultaneous APP18-specific competency-review PR detected at start.2. Independently derived exit competence and disciplinary evidence
Exit capability: An SEF graduate with programming and mathematical/algorithmic preparation can predict actual JavaScript language behavior, implement cohesive functions and modules around explicit data invariants, inspect object and scope failures, enforce safe runtime data contracts, reason about promise scheduling and error propagation, reproduce a maintained local toolchain, test adverse cases, and independently defend one modifiable JavaScript utility. Learners must be able to diagnose an unfamiliar bounded change rather than follow a tutorial.
Boundary and ownership:
Research benchmarks (sources, not a template or accreditation):
exports, host-dependent module resolution and CJS interop.process.nextTickand queueMicrotask documentation — event order can differ between Node ESM and CommonJS; do not claim universal Node/browser event-loop timing.3. Outcome dispositions and semantic continuity
Retain APP18-O1–O11, unchanged IDs and published meanings. Their decisions remain: O1 language vs host; O2 values/coercion/precision/Unicode; O3 control flow/decomposition; O4 lexical scope/closures/
this/aliasing; O5 objects/prototypes/collections; O6 runtime contracts/explicit failure; O7 cohesive ESM APIs; O8 asynchronous work and scheduling; O9 supported local Node toolchain; O10 tests/debugging/cost; O11 independent integrated delivery/change/defense. No indispensable outcome was removed to reduce source length.Clarify rather than replace: O5's prototype-data observation and O6's untrusted-boundary enforcement are distinct, not two identical JSON/data-parsing classes. O8's Promise-failure criterion is strengthened to demonstrate continuing in-flight work after
Promise.allrejection and nonautomatic cancellation; this makes the existing outcome assessable rather than inventing a new language capability. O9 remains small local project reproduction, not APP21 system/runtime service specialization. Historical completion decisions must remain version-scoped.4. Every module's lesson decisions
undefined/null distinctions, numeric/BigInt safety, UTF-16/code point/grapheme differences.this, alias semantics and negative cases.JSON.parsealone.eval/unsafe merge and contract-preserving revision.package.json, lockfile, install-script risk and project reproduction in M9. Keep ESM live bindings, cycles, APIs, Node resolution/CJS caveats and independent consumer tests as genuinely module-design responsibilities.all/allSettled, cooperative cancellation and deterministic failure diagnostics. Add explicit aggregate rejection ≠ automatic cancellation test.Result: 12 retained conceptual modules; 82 → 65 numbered lesson entries. Module length remains unequal because there is no pedagogical rule requiring equal-sized modules. Do not interpret the reductions as a numerical quality score; no core JavaScript mechanism or required outcome was dropped.
5. Required summative evidence and adversarial cases
All five existing stable assessment IDs are retained with separately decidable evidence; only two contracts require substantive clarification. The same evolving source may be used:
JSON.parseis not equated to prototype pollution; a later unsafe merge can introduce it.Promise.allrejects while other already-started jobs continue counterexample and comparison withallSettled. A timeout/abort signal is not inherently cancellation of an arbitrary Promise/underlying operation; no arbitrary sleep timing tests.Cross-check: each required outcome has an independently examinable required work/criteria/evidence path. Every assessment explicitly specifies Outcomes, Work, Criteria and Evidence, with negative/failure cases and no hidden hosted infrastructure. Reproducible tests alone are insufficient evidence of conceptual semantics, scope or async understanding.
6. Cross-course, catalog and historical implications
SEF10prerequisite and dependent APP19/APP21 and APP9 closure unchanged; this language-foundation course never becomes TypeScript/React/Node-server course.v0.2.0, original outcomes/assessment IDs, samedraftstatus and provisional 12–16-week estimate. Workload needs actual learner/assessor timing; shortening lesson entries is not evidence the learner duration should be shortened.7. Locator, severity, consequence and disposition
Promise.alltest previously did not independently require evidence remaining work continues; a competent-looking solution could imply automatic cancellation. Required counterexample and correct recovery policy added.8. Verification, independent challenge and limits
OutcomesandLessonssections, all lessons numbered correctly, 65 numbered entries, 11 declared outcome IDs, five required assessment IDs, andOutcomes/Work/Criteria/Evidencefor every assessment, with all outcomes appearing in required assessment definitions. No static mismatch observed.tests/test_app_catalog.pyandtests/test_curriculum_inventory.pyfor hardcoded APP18 module/lesson count expectations; none found in these tests. This does not replace running the checks.testedorverifiedclaim. Require project CI and maintainer pedagogical review before merge.9. Decision and branch discipline
Ready for maintainer scrutiny / CI, not an audited-verified learner-ready course. Target
maindirectly on this focused branch; do not merge PR #150 and do not merge/delete this branch without maintainer action. Next in established M3 dependency-valid order after merge: APP19 — TypeScript Programming.