Built on the standards
The standards are meant to be used.
These are the things built on the standards: browser tools that put the discipline to work directly, and the MCP servers that make the standards callable inside any AI assistant. Each one is described here and linked out to where it lives, the same way the site hands off to the grants work.
The tools
Precision, put to work in the browser.
Precision Council for AI (PC4AI)
Read more →A browser evaluation council: independent agents score a candidate without seeing each other, a chair converges them, and it grades how independent that convergence actually was. Runs on your own provider keys. The council logic is the Golem Foundation's Octant Council Builder; the contribution here is the independence guard.
Precision Toolkit for AI (PT4AI)
Read more →A workbench of precision tools that carry the rigor of metrology, linguistics, and forecasting into coordination, evaluation, and meaning. The edge is holding an arbitrary claim to account in place, with an observer-independence test as the crux.
Design Suite for AI (DS4AI)
Read more →A family of small, dependency-free web primitives, one for each thing a shipped page owes a reader that a look-at-it review cannot see and that fast, AI-assisted building drops: readable color, operable controls, honest states, a hardened surface, findable metadata, stable delivery. The MISSING standard names the six gaps; a surface that closes all six is MISSING Conformant.
Callable in an AI
The standards, inside any assistant.
Four MCP servers make the standards callable tools rather than documents to read, so an AI assistant can run them directly on the work in front of it. Each is published on both npm and JSR.
Frame Language
@proof-of-coord/frame-languageThe Dimensional Frame Language precision discipline as callable tools: the watchlist, the admissibility cases, and a text auditor for own-voice writing.
Structural Integrity (CSIS)
@proof-of-coord/structural-integrityStructural access to the ten Coordination Structural Integrity Suite standards, as tools an assistant can run directly.
Evidence Integrity
@proof-of-coord/evidence-integrityThe evidence integrity standards as callable tools: CROSS obligation gates, WALKRI field discipline, ORE ingestion grading, and STRUCK exit obligations.
In outside use
Adopted beyond our own tools.
The clearest sign a standard does real work is a project that was not built to showcase it reaching for it anyway.
The Regen Web3 Toolkit
The repository →An open coordination toolkit from the Regen and Greenpill community that adopts these standards as its structural-integrity and review lens. Its documentation credits CSIS as an external standard developed by Durgadas and treats it as the toolkit’s structural-integrity framework; the framework enforces a CRAFT non-self-adjudication rule in its code, runs a CSIS review lens at its contribution gate, and models the standards as first-class objects in its knowledge base. The toolkit scopes this plainly as informed by the standards, not conforming to them.
Where it credits the standards →