Prerequisite Test¶
Test or assessment — instantiates Mastery-Gate Progression
Verifies the specific earlier capability a dependent task requires before admitting the learner into it — an entry ticket keyed to the dependency map.
A Prerequisite Test sits at the doorway of a dependent unit and asks a single, narrow question: does this person already hold the earlier capability that the unit is about to lean on? It is not a check of what was just taught, nor a broad readiness survey — it is an admission ticket aimed backward at the skills the next task silently assumes. What makes it this mechanism and not one of its siblings is that its whole design is keyed to a dependency: the test exists because module B genuinely requires competence X from module A, and its items are chosen to sample X specifically. Pass it and the door opens; the test's job ends there, at the boundary.
Example¶
A university's calculus sequence keeps losing students in the first three weeks — not to derivatives, but to algebra. Instructors trace the failures back and find a consistent culprit: students who cannot fluently manipulate exponents, factor quadratics, or handle function notation drown the moment those become tools rather than topics. So the department builds a Prerequisite Test administered in week zero. It does not cover any calculus. It presents twenty short algebra and precalculus items chosen precisely because differentiation and limit work depend on them, with a cut score set at the fluency level the first month actually requires.
A student who scores below the cut is not "failed" — she is simply routed away from the calculus door and toward a brush-up track before entering. A student who clears it walks in, and when he later struggles with the chain rule, his instructor can be confident the problem is the chain rule and not a buried algebra hole. The test has done exactly one thing: confirmed that the capability the next task depends on is present before the door opens.
How it works¶
The distinctive engineering is backward-tracing, not question-writing. Start from the downstream task and ask what earlier competencies it presupposes — the ones that will be used as instruments, not re-taught. Each of those becomes a target, and items are written to sample it under conditions close to how the next unit will actually invoke it (fluency and speed often matter as much as bare correctness). The cut score is set at the level the dependency demands, not at a generic "passing" line. Crucially, the test is positioned before entry and produces a binary routing signal — enter, or divert — rather than a rich grade. It deliberately does not diagnose why a gap exists or prescribe repair; it only certifies presence or absence of the prerequisite at the threshold.
Tuning parameters¶
- Dependency coverage — how many of the downstream task's true prerequisites the test samples. Broader coverage catches more hidden holes but lengthens the test and raises the cost of a false block.
- Cut score — where the admit/divert line sits. Set it at the fluency the next unit actually uses; too low admits under-prepared learners, too high blocks capable ones over trivia.
- Item authenticity — how closely items mirror the instrumental use of the skill (applied under time, in context) versus decontextualized recall. Higher authenticity predicts readiness better but costs more to build and score.
- Consequence of a block — whether a below-cut result diverts, delays, or merely warns. Harder consequences protect the downstream unit but demand a defensible, transparent cut.
When it helps, and when it misleads¶
Its strength is disambiguation. When it guards the boundary, a later struggle can be read cleanly — the prerequisite was verified present, so the difficulty is genuinely with the new material. That is the criterion-referenced logic at its best: the score means "has capability X to the required standard," not "beat 70% of peers."[1]
It misleads when the test drifts from the real dependency. The classic misuse is a prerequisite test that samples an easy proxy — a topic that is convenient to write items for but that the downstream task does not actually require — so it blocks the wrong people and admits the wrong people while looking rigorous. It can also become a pure wall: because it only routes and never repairs, a program that bolts it on without a remediation path simply excludes learners. The guarding discipline is to validate items against downstream performance and always pair the test with a real path back, so a block is a detour, never a dead end.
How it implements the components¶
prerequisite_dependency_map— the test is built from the map: each item exists because a named downstream task depends on the capability it samples, so the mechanism operationalizes the dependency itself.prerequisite_capability— it defines and measures the specific earlier competence (fluent algebra, here) as an observable capability rather than as content exposure.progression_gate— the pass/divert result is the entry decision at the boundary; clearing it is what opens the door to the dependent unit.
It does not implement mastery_criterion sampling or retest_rule for repeated low-stakes attempts — that is Mastery Quiz, its nearest twin, which checks understanding of current material rather than gating entry against the dependency map.
Related¶
- Instantiates: Mastery-Gate Progression — it supplies the entry gate that keeps a dependent unit from admitting learners who lack its prerequisites.
- Consumes: Criterion Rubric — the standard its cut score is calibrated against.
- Sibling mechanisms: Mastery Quiz · Competency Checkoff · Simulation Checkout · Remediation Cycle · Portfolio Mastery Review · Criterion Rubric · Conditional Release Protocol · Skill Progression Ladder
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Prerequisite Test operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it verifies the specific earlier capability a dependent task requires before admitting the learner into it — an entry ticket keyed to the dependency map.
Independent corroboration: The frozen evidence defines Prerequisite Test as 'Verifies the specific earlier capability a dependent task requires before admitting the learner into it — an entry ticket keyed to the dependency map', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Experiment, Test & Rehearsal — Prerequisite Test includes features of an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Education & Pedagogy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Prerequisite Test is most plausibly rooted in the education_pedagogy tradition because its characteristic form depends on instruction, learning progression, assessment, and scaffolded practice. The assignment tracks that formative lineage, not the many settings in which the mechanism can now be applied.
Related originating lineages:
- Psychology — The psychology tradition materially shaped Prerequisite Test through its own practice of individual cognition, motivation, judgment, and behavior.
Review resolution: Both blind reviewers agree that education pedagogy is the primary origin. Explicit reconciliation resolves domain reach disagreement. Formative alternate lineages are retained as psychology; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] Criterion-referenced measurement, named by Robert Glaser (1963), judges a score against a fixed standard of what the learner can do — rather than against the performance of other test-takers (norm-referenced). A prerequisite test is criterion-referenced by design: it asks whether capability X clears the bar the next task needs, not whether the learner ranks above peers. withdrawn registry ↩