Keystone
The concept · NSF 26-508

A coordination hub is a cast, not a form.

One AI-readiness need enters a single front door and travels one governed path, passed hand to hand across a coalition, stopped at four gates, and closed only when the outcome is independently verified. Here is who does what, how the loop runs, and how it proves itself.

The cast

Nine actors, one job each.

No one actor is the system. Coordination is the handoff between them, each with a single, bounded responsibility, so no role can quietly do another’s job.

The requester

a firm or worker

Arrives with an unmet AI question through one front door: never a phone tree, never a dead end.

The Concierge

the front door

Scrubs PII, classifies the need, and either routes it or logs it as demand: the hub never answers with a shrug.

The Hub

the backbone

The coordination engine and fiscal lead: it owns the case ledger, the coverage matrix, and the measurement - one core, not five tools to integrate.

The Router

the matcher

Matches the need to a ready seat by sector, language, and geography - and only offers a partner the hub may lawfully share with (a current data-sharing agreement).

The coalition partners

the seats

SBDC, workforce, extension, MEP, sector captains, the public-sector anchor - each holds a named seat backed by a signed commitment.

The delivering partner

the hands

Accepts the routed case, does the work, and reports a de-identified, evidence-tiered outcome: never a subject, never a name.

The Measurement Referee

the firewall

An independent, firewalled evaluator: it verifies the outcome against its evidence tier, so a self-report can never count as proof.

The Equity Guarantor

the reach check

The access-and-reach firewall: it clears a verified outcome, or returns it to measurement if the loop left someone out.

The Governance gate

the human review

A rights-impacting need parks here for mandatory human review: it can never be auto-answered by AI.

The orchestration

One path, four gates.

Every need walks the same nine stops. Four of them are gates that can stop the loop, which is how AI output never reaches a person unreviewed, and how an outcome only counts once it is verified.

#StopWhat happensGate
1IntakeThe Concierge takes a scrubbed, classified need into coordination.·
2TriageThe need is assigned a risk tier that decides which rails it rides.·
3GovernA rights-impacting need parks for a mandatory human decision.human review
4RouteThe router matches it to a ready seat, offered only with a current DSA.legal · DSA
5DeliverA partner accepts the seat and does the work with the requester.·
6OutcomeThe partner reports a de-identified, evidence-tiered result.·
7VerifyThe Measurement Referee checks the evidence: weak proof is rejected.measurement
8ClearThe Equity Guarantor clears the reach, or returns it to measurement.equity
9ResolveThe loop closes: it bridges the open demand and lifts Matrix Coverage.·

The loop closes at stop 9, and its signals (unmet demand, readiness scans) feed the next thing to coordinate. The loop is the product.

The map it fills

Covered means all three legs hold.

Matrix Coverage is honest by construction. A demand-bearing cell counts as covered only when an aligned credential, a mapped provider, and a verified closed loop all agree on it; a listing is not coverage. The gap it exposes is the root gap: the first leg that fails.

A live jurisdiction: two of four demand-bearing cells fully covered; the map reads 0.5. Finance has the credential and a provider but no verified loop yet; agriculture is still missing its credential.

Proof, not assertion

Every gain is a delta against t0.

The coordination-outcome standard captures the fragmented system at award start, then reports today as a delta against it, never against zero. “At award start X%, today Y%” is proof, not a vanity count, and it is stamped with the exact policy that produced the number, so a rule change can never be mistaken for real progress.

Coverage 0 → 50%, gap-closure 0 → 40%: every figure derived from the closed-case ledger, aggregate-only and PII-free.

What it senses

Two channels, and the gap between them.

Readiness is not one number. The hub senses two channels: whether the firm has adopted AI, and whether its workersare already using it. The gap between them is the signal: top-down rollout that never reached the floor, or shadow AI the firm hasn’t sanctioned. That is where coordination targets the next intervention.

The loop is the product.

Every actor has one job, every need one path, every gate a reason. Watch it run on a live hub, from a first question to a verified, closed loop.