Fast Track with Eligibility Rules¶

Routing policy — instantiates Catalytic Pathway Enablement

Routes pre-qualified low-risk cases down a lower-friction lane using explicit eligibility rules, without softening the acceptance standard the ordinary lane enforces.

Most of the friction in a permitted transformation is paid by cases that never needed it — routine, low-risk instances that are dragged through the same heavyweight review as the hard ones. Fast Track with Eligibility Rules lowers the barrier for exactly those cases by pre-sorting rather than by doing the work any faster: an explicit eligibility rule decides which cases may enter the low-friction lane, and everything else is routed to the full pathway untouched. Its defining move — the one that separates it from simply "cutting red tape" — is that the acceptance standard is held invariant: the fast lane changes the route, never the bar a case must clear. Speed comes from the eligibility gate being cheap and reliable, and from an honest reroute that pushes a case back to full review the moment it stops looking routine.

Example¶

A municipal building department is drowning in permit applications. Most are trivial — a like-for-like water-heater swap, a service-panel replacement by a licensed contractor — but each waits weeks in the same queue as a structural addition. The department publishes an over-the-counter fast track: an application qualifies if the work is on a fixed list of low-risk scopes, under a value threshold, and submitted by a licensed contractor. A qualifying water-heater permit is now issued same-day at the counter; anything touching structure, egress, or the value cap is routed to full plan review as before. The code itself — the acceptance standard — is identical on both lanes.

The result is that roughly the routine majority of permits clear in minutes, and reviewers get their time back for the applications that actually need judgment. The rule earns its keep only while the eligibility signals stay hard to game: the day a contractor learns to split one large job into several "small" permits, the fast lane starts admitting cases it was never meant to, and the department has to tighten the rule or audit its way back.

How it works¶

Gate on cheap, reliable signals. Eligibility turns on attributes that are objective and hard to fake (scope on a fixed list, a value cap, a verified credential) — not on a reviewer's discretion, which is the friction being avoided.
Hold the standard invariant. The fast lane omits steps, never requirements: a fast-tracked case must still satisfy the same substantive standard, just with lighter process.
Reroute on doubt. Any case that reveals complexity mid-stream is bumped back to the full pathway, so the fast lane's error is a delay, not a bad approval.

Tuning parameters¶

Eligibility breadth — how wide the qualifying criteria are. Wider admits more cases and lifts throughput, but raises the chance a genuinely risky case slips through on a technicality.
Risk threshold — where the low-risk cutoff sits. Conservative thresholds protect the standard; aggressive ones chase throughput and invite misrouting.
Audit / sampling rate — how many fast-tracked cases are pulled and re-checked against the full standard. Higher sampling catches drift early at the cost of the speed you just bought.
Reroute trigger — how readily a case is bounced to full review. A hair-trigger protects quality but erodes the lane's value; a sticky one lets complex cases finish on the wrong track.
Sunset / review cadence — how often the eligibility rule itself is re-examined against real outcomes and gaming attempts.

When it helps, and when it misleads¶

Its strength is leverage without new capacity: when a large, cleanly separable fraction of cases is genuinely routine, a fast track deflects them off the scarce full-review pathway and frees it for the cases that need it — no extra reviewers required.

The failure modes cluster around the eligibility gate. If the qualifying signals are gameable, applicants cream-skim — reshaping or splitting cases to qualify — and the risky residue quietly accumulates on the fast lane.^[1] The subtler failure is standard erosion: under throughput pressure, "fast" slides into "lax," steps that were meant to be skipped become requirements that are waived, and the fast lane becomes the default while quality drifts. The classic misuse is loosening eligibility to hit a throughput target and calling the result efficiency. The discipline that keeps it honest is to audit a random sample of fast-tracked cases against the full standard and to watch the reroute rate — a fast lane that never bounces anything is not sorting, it is rubber-stamping.

How it implements the components¶

Fast Track fills the routing and eligibility side of the archetype — which cases reach the facilitator and on what terms — not the facilitator itself:

substrate_access_condition — the eligibility rule is the access condition: it defines which cases may reach the low-friction lane, in what form and readiness.
selectivity_rule — the fast lane accelerates only the intended low-risk class and deliberately withholds acceleration from everything else, rather than speeding all cases indiscriminately.
permitted_pathway_boundary — the invariant acceptance standard and the protective reviews that may not be bypassed are exactly the boundary this policy is built to preserve.

It does not embody the barrier-lowering facilitator itself (that is Heterogeneous Catalyst Bed, Reusable Broker or Convener Service, or Workflow Automation or Macro), and it does not measure whether the fast lane keeps its selectivity — that is Turnover and Selectivity Assay.

Instantiates: Catalytic Pathway Enablement — Fast Track supplies the eligibility gate that decides which substrate reaches the facilitator's low-friction pathway.
Consumes: Barrier Height Estimation — sizing which cases clear the bar cheaply is what makes the eligibility rule defensible.
Sibling mechanisms: Turnover and Selectivity Assay · Prevalidated Transformation Template · Inhibitor and Poison Screen · Embedded Specialist Review Lane · Interface Contract Design

Notes¶

Fast Track governs routing, not the transformation itself — it presupposes a working pathway and simply decides who takes the short way round. That is what separates it from a permanent barrier removal: nothing is torn down, the full lane still exists, and the standard is unchanged. If the goal were to remove the friction for everyone rather than to sort cases onto it, that is a different pattern than catalysis.

References¶

[1] Cream-skimming (cherry-picking) — selecting or reshaping the easiest cases to post good throughput while the standard for the remainder quietly slips. The standard corrective is auditing fast-tracked cases against the full standard and monitoring what gets rerouted. ↩