The controller layer for a family of repos. One manifest of members, one render surface per deployment shape, one doctor verb that verifies every adopter serves the same truth.
The crosslink mesh - the apps menu, the README tables, the status registry - stops being hand-typed N times and becomes governed data with teeth. The apps menu is payload #1, not the product: governance over how members link, state, and pin themselves is the product.
- Zero dependencies. Node ESM, exit codes 0/1/2.
- General and clean. Nothing here knows your project's name. The repo is a tool: no Creadev data in
src/,README.md, or the config schema - the reference deployment lives in a composer, not here. - Refusing, not warning. A doctor that warns into green is politeness theater; govstruct refuses nameably at author time.
- Statically emitted. Surfaces are build-time artifacts, never runtime fetches - a bot reads a plain anchor.
- Composed, not competing. govstruct governs identity and conformance; a composer like railyard governs transport and dispatch. They meet at
repo+role: govstruct says who a member is, the composer's mount registry says where its bytes come from. - Enforced by the suite's arms. The spec is packstruct's
/packs; crashtest attacks the loader, eyestruct watches the rendered pane, and poststruct audits what shipped. govstruct composes them rather than re-implementing them.
govstruct lint # manifest grammar
govstruct render <target> # apps | react | partial | readme | registry
govstruct doctor [--suite] [--fleet] [--network] # adopter gate, suite battery, fleet meter, or the online leg
govstruct check # the source-consistency check packs
govstruct registry # the suite roll-up (env / pins / floors / versions)
govstruct iso [--coverage] # the ISO 9001 / 27001 evidence orientation
govstruct surface [--verify] # the surface stability contract a consumer binds to
govstruct lock # archive + sha256 receipt
govstruct names <id> # check a candidate id against npm, GitHub, the roster
govstruct migrate --status # report / preview a spec or field migration
govstruct init [<dir>] # scaffold a one-member family
govstruct stamp <record.json> # register a stamped member (the write path)
govstruct retire <id> # tombstone a member, keeping its aliases (the lifecycle)
govstruct audit verify # walk the audit ledger chain (offline)
govstruct verdict rollup # read fresh receipts, poll the rest (the verdict bus)
govstruct impact <id> # the propagation path: who depends on <id>
Exit codes are the family ladder: 0 all honored, 1 any refusal, 2 usage error. Every refusal carries a code from spec/refusals.json (the shared vocabulary); a code the vocabulary does not name is itself refused.
Status: 1.1.1, pre-alpha - first build complete (all verbs green). The release ladder is in DEPLOY.md: 0.9.x publishes manually with npm publish (the OIDC lane refuses 0.x), and 1.0.0+ publishes from v* tags. The design lives in labs/prd-govstruct.md.
MIT.
npm test # the spine: node --test + the two-way fixtures
npm run check # the compliance check packs (S1-S7)
npx crashtest run # the lint contract under a hostile member-block corpus
govstruct doctor --adopters # gate each declared adopter's govstruct pinnpm test, the dogfood, and the adopter gate (compliance.yml) all run on every push to main and staging (.github/workflows/). Zero runtime dependencies; the only install surface is the dev tooling the dogfood lanes pull in.