Admissible Pathway Catalog¶
Document — instantiates Outcome-Attractor Pathway Design
Documents allowed route families, eligibility conditions, invariants, evidence requirements, and handoff rules.
An Admissible Pathway Catalog is the written register of which routes to the shared endpoint are legitimate and under what terms. It exists to convert an accumulating pile of one-off exceptions into a governed, enumerable set: for each allowed route family it records who is eligible to take it, what invariants it must not violate, what evidence proves it stayed within bounds, and how it hands off into the common final state. Its defining move is enumeration under conditions — it does not simulate whether a route converges, nor does it monitor a route in flight; it is the authoritative document that answers "is this path allowed, for this starting state, and what does it owe?" Everything downstream — onboarding flows, review cycles, reroute decisions — reads its answer rather than re-deciding admissibility case by case.
Example¶
A university lets students reach the same degree — a certified competency in statistics — from very different starting points: a full in-house course, an approved transfer from a partner college, a credit-by-examination route, and a prior-learning portfolio for working professionals. Left ungoverned, each department improvises which of these it will accept, and identical students get different answers depending on who reviews the file.
The Admissible Pathway Catalog fixes this by naming the four route families explicitly. For each it records the eligibility condition (the portfolio route is open only to applicants with three years of relevant work), the invariants that cannot be traded away (every route must demonstrate the same three learning outcomes; none may waive the statistics-literacy requirement), the evidence a route must supply (a proctored assessment, a signed articulation agreement,[n1] a rubric-scored portfolio), and the handoff rule that lets the registrar post the credit into one canonical transcript state. A student and an advisor can now look up, in one document, whether the portfolio route is open to them and exactly what it will require — before anyone invests effort in a path that was never going to be admissible.
How it works¶
The catalog is authored, not computed, and its discipline is in what each entry must contain:
- One entry per route family, never per case. A route earns a catalog entry because it recurs and has a reason to exist; genuine one-offs stay exceptions until the pattern is real.
- Eligibility as a gate, not a preference. Each entry states the condition under which its route is permitted, so choosing among admissible routes is a separate, later decision.
- Invariants attached to every route. The same non-negotiables are restated per entry so a reader never has to infer them; a route that cannot show it preserves them is struck from the catalog.
- Evidence and handoff written as obligations. Each entry names the proof of compliance it owes and the interface it must deliver into, so the endpoint receives a uniform handoff regardless of route.
The result is a living reference document with an owner and a change history, not a static appendix.
Tuning parameters¶
- Granularity of route families — a few broad families or many narrow ones. Fine granularity captures real differences but multiplies entries to maintain; coarse families are cheaper but hide sub-cases that behave differently.
- Eligibility strictness — how tightly each route's entry gate is drawn. Tight gates prevent misuse but push edge cases toward reroute; loose gates increase reach but raise the monitoring burden elsewhere.
- Evidence bar per route — how much proof of invariant-preservation a route must carry. A higher bar buys confidence at the cost of friction on legitimate but unusual starts.
- Handoff standardization — whether every route delivers into one identical interface or several endpoint-compatible variants. One interface is simplest downstream; variants ease authoring but expand what the endpoint must accept.
- Revision cadence — how often the catalog is reopened to admit new routes or retire dead ones. Rare revisions ossify; constant churn undermines the catalog's authority.
When it helps, and when it misleads¶
Its strength is that it kills the "unstated real route" problem: when every legitimate path is written down with equal standing, no single route can quietly become the only respected one while the others decay into stigmatized exceptions. It gives applicants a way to self-select out of impossible paths early, and it gives auditors a fixed reference against which any in-flight route can be checked.
Its failure mode is that a catalog documents intent, not reality. A route can be listed as admissible long after it has silently stopped preserving its invariants, and the tidy register lends false legitimacy to a path nobody has actually verified lately — the map is mistaken for the territory. Worse, an over-strict or under-maintained catalog turns into a bureaucratic gate that suppresses exactly the legitimate route variation the archetype exists to protect. The guarding discipline is to bind each entry to an evidence obligation and a revision cadence, so admissibility is periodically re-earned rather than presumed permanent, and to treat any recurring exception as a signal that the catalog is missing a family rather than that the applicant is wrong.
How it implements the components¶
admissible_pathway_set— the catalog is this set made explicit: one authoritative entry per allowed route family.path_invariant_specification— each entry restates the invariants its route must preserve, making them a condition of admission.pathway_choice_rule— the eligibility condition per entry defines which starting states may take which route.handoff_interface_contract— each entry names the handoff obligation by which its route delivers into the shared endpoint.
It does not test whether an output actually meets the endpoint standard (endpoint_equivalence_test) — that belongs to Endpoint Equivalence Test Suite — nor does it monitor routes in flight (path_progress_observability), which is Pathway Health Dashboard's job.
Related¶
- Instantiates: Outcome-Attractor Pathway Design — the catalog supplies the enumerated, condition-tagged set of admissible routes the rest of the design governs against.
- Consumes: Normalized Endpoint Contract supplies the handoff target each catalog entry must deliver into.
- Sibling mechanisms: Attractor Basin Simulation · Endpoint Equivalence Test Suite · Guided Multi-Path Onboarding Flow · Multi-Route State-Transition Map · Normalized Endpoint Contract · Pathway Cohort Comparison · Pathway Health Dashboard · Reroute and Reentry Protocol
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The mechanism documents allowed route families, eligibility conditions, invariants, evidence requirements, and handoff rules, so its operative form is a static or prospective information artifact.
Independent corroboration: The frozen evidence defines Admissible Pathway Catalog as 'Documents allowed route families, eligibility conditions, invariants, evidence requirements, and handoff rules', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Education & Pedagogy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Education systems use articulation agreements and published pathway catalogs to specify eligible routes, transferable evidence, invariant requirements, and handoff into a common credential.
Related originating lineages:
- Engineering & Design — Interface contracts and invariant-preserving routes contribute the systems-design analogue.
- Law & Governance — Administrative rulemaking contributes authoritative eligibility conditions, equal application, evidence duties, exceptions, and appeal.
- Organizational & Management Science — Process architecture contributes route families, interface contracts, ownership, and controlled replacement of recurring one-off exceptions.
- Public Administration & Policy — Multiple lawful service pathways and case-routing criteria provide a mature administrative application.
Review resolution: Education systems formally publish multiple credit and transfer pathways with eligibility, equivalence, evidence, and handoff requirements, closely matching the mechanism's defining obligations. Law, public administration, organizational governance, and engineering interface contracts materially generalize the catalog, but education and pedagogy remain primary.
Attribution caveat: The generalized catalog resembles organizational governance, but formal articulation, prior-learning, and transfer pathways provide the clearest mature route-family practice.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- ERIC — Early Effects of North Carolina's Comprehensive Articulation Agreement
- EducationUSA — Community College Transfer and Articulation Agreements
Notes¶
[n1] An articulation agreement is a formal, published compact between institutions specifying exactly which credits transfer toward which requirements. It is the higher-education archetype of a catalogued admissible pathway: a route made explicit and binding rather than negotiated per student. ↩