Fleet & enterprise - many repos, one contract
One pack grammar.
Every repo, provably.
The moment more than one team writes packs, "it loads on my machine" stops being good enough. packstruct is built for that scale: the spec is frozen and versioned, hosts carry an exact-pin receipt of the version they conform to, conformance is a command you can gate CI on, and governance itself can be expressed as packs. It is MIT, and it stays that way.
What enterprise actually needs
Four properties that separate a hobby spec from one you can build a fleet on.
1Frozen and versioned
v1 does not drift. Additive changes keep the schema number; removing or renaming is a major bump that must carry a migration note - old shapes, new shapes, refusal wording (SPEC §11). No host is broken by surprise.
2Provable conformance
A host does not claim conformance; it runs packstruct audit-conformance and passes. The claim is a command, so it is testable in CI and falsifiable by anyone.
3Receipts, not promises
Each host carries the packstruct version it conforms to as an exact devDependency and a receipt row. Hosts may lag each other; what is forced is the synchronized receipt when a bump happens (SPEC §8).
4Governance as packs
govstruct proves it: its compliance rules are check packs, so governance ships as a portable /packs surface instead of a wiki nobody re-reads.
An adoption path that scales
Four steps from "we have a packs folder" to "our whole fleet is gated on one grammar."
npx packstruct lint --deep over each repo's packs/ dir. You get a nameable list of every manifest that points at nothing, and every id collision.packstruct as an exact devDependency and a receipt row (version, the sha it was cut against, the lint result, the date). The pin is the promise; the receipt is the proof.lint and audit-conformance both exit 0/1/2. Wire them as a required check: a malformed manifest or a non-conforming loader fails the build by name.implements: packstruct@1 in your docs, and serve your verdicts with the family-status@1 dialect so every member can read every other member honestly.Every step above is already how the nine live hosts in the showcase run - you are adopting a lane with receipts, not a proposal.
Open source, and staying that way
packstruct is MIT-licensed. The spec, the CLI, and the harness are all open, and development happens in the open through pull requests with their gates run.
MIT, no strings
Read the code, run the linter, vendor the spec into your own governance. The honest summary of the license is: it is MIT. The terms and privacy pages carry the surface facts in plain language.
Open development
Changes land as pull requests with the battery green. The repository is the source of truth, and SPEC.md is the normative document - this site is a readable mirror.
Zero dependencies
The CLI ships with no runtime dependencies, so adopting it adds nothing to your supply chain. Published on npm as packstruct.
Extension is additive
Need a new profile or a new host-owned key? The spec has a path for that (§8, §10) that does not fork the manifest - so your extension benefits the whole family instead of splitting it.
Bring us a problem - we will take the issue
The fastest way to shape where the spec goes is to file what you need. These links open GitHub's own issue composer with the right template prefilled - you review and press submit there. Nothing is sent from this site.
Adopt packstruct
You run a fleet (or one repo) and want to standardize on the grammar. Tell us the shape and we will help map the adoption path.
File an adoption issueRegister a new host
You built an engine that loads packs and want a receipt row and a conformance lane. This is the traveler on-ramp (SPEC §10).
Register a hostPropose a spec change
A new optional field, a new host-owned key, or a new profile. Additive proposals are welcome; non-additive ones come with a migration note (SPEC §11).
Propose a changeReport a bug
The linter, the harness, or the spec text. Paste what you ran and what happened - the repro is the whole value.
File a bugPrefer to see what is already open? Browse the issue tracker first - a good issue is a searchable receipt that helps the next adopter.