The backbone behind a State or Territory TechAccess hub.
Keystone turns NSF 26-508’s mandate into running software: one coordinated front door, a partner network, closed-loop case tracking, and verified outcomes, so every constituent reaches the right help, and you can prove it to your state and to NSF.
One engine, the whole loop.
Not five tools to integrate: one core that classifies the need, routes it to a ready partner, tracks it to a resolution, and measures what happened.
A front door, not a dead end
A plain-language Concierge answers from approved, dated partner content, or hands off to a named human at a bright line. Needs it can't yet meet are logged as demand, never dropped.
A partner network that's ready
An HSDS-aligned registry of partners and the services they offer (capability, capacity, recertification, and data-sharing agreements) so every route lands somewhere real and in-force.
Closed-loop coordination
Consent-gated routing with mandatory loop-closure: every referral tracked to a resolution. The hub holds a pointer and a status - never the work product, never the person's data.
Outcomes you can defend
Only verified outcomes count, and metrics are aggregate-only. Loop-closure is the headline number; everything is derived from the case ledger, never hand-entered.
Measurement that holds up to a funder.
Every number is derived from the closed-case ledger, aggregate-only, and PII-free by construction: never hand-entered, never a vanity count.
Only verified outcomes count: evidence-tiered and past the Measurement Referee before they reach a report.
Small cells are suppressed (20 CFR 603), and the number suppressed is reported: no silent truncation.
Running today as a working demo across 6 states (California, Indiana, Iowa, Nevada, New Jersey, Virginia). The methodology is built to survive a single audit.
Built to be trusted with public data and public decisions.
The differentiators a state CIO and an NSF reviewer actually ask about - not fine print.
It never makes things up
The Concierge answers only verbatim from approved, dated, attributed sources. After Moffatt v. Air Canada, where a company was held to what its chatbot said, Keystone is built so the operator owns the words.
PII-free by construction
Intake is scrubbed; the hub holds taxonomy codes and pointers, not personal data. Individual wage and employment matching stays at the workforce-agency seat under 20 CFR 603.
Human-in-the-loop AI
Aligned to OMB M-25-21: human oversight, AI impact assessment, and appeals for affected individuals, with public, auditable use. AI is a constrained tool here, never the decision-maker.
Speaks federal standards
HSDS for the service directory; NAICS, O*NET, and CTDL taxonomies; row-level tenant isolation per jurisdiction. Built to slot into how agencies already work.
Built for the TechAccess mandate.
NSF 26-508 funds a backbone organization that coordinates existing programs; it does not deliver training itself. Keystone is that backbone, in software.
The problem
Help exists, but it's fragmented. Constituents hit dead ends, and good programs go unfound.
The mechanism
One front door classifies the need, routes it to a ready partner, and closes the loop - every time.
The outcome
More constituents reach the right help, and the hub can prove access, reach, and results.
Maps to the Areas of Responsibility: the AI Learning & Resource Navigator (the registry + Navigator), AI deployment support (routing + the Corps roster), the state strategic plan (demand signals + the Gap Map), and the required metrics (verified outcomes).
An evidence base for all 56 jurisdictions.
Before a single case, Keystone builds an audited, citation-backed readiness profile for every state, DC, and territory: a three-stage pipeline across ~26 federal sources, cross-checked by independent AI agents. The demo runs on 6; the evidence base spans all 56.
See it run.
Explore a live hub, or open the front door your constituents would use.