The live catalog

One /packs dir, every host.

A pack is a directory under packs/public/<name>/carrying a frozen pack.json and the entry it names. This page is the catalog of what actually ships: the dogfood pack that attacks the linter, and the 9 hosts that load the same SPEC v1 grammar. Every count is a receipt from that host's own tree. For crosslinks to each repo and site, see the showcase.

What ships in packs/public/

packstruct carries one pack of its own, and it attacks the linter itself. Four attacks, one contract each - a new EXPLOITED or a regression of any recorded verdict fails CI.

attackprofilewhat it proves
hostile-manifest-fuzzscenarioevery malformed pack.json answers in-bounds: parseable verdict JSON, violations carried with {pack,norm,message}, exit 0/1 - never 5xx, never a deep stack trace
entry-path-containmentscenarioentry values escaping the pack dir (traversal, absolute, file URL, null byte) are flagged by the entry norm - an outside file that happens to exist never silences the refusal
over-strict-drift-canaryscenariospec-allowed shapes (extra manifest keys, empty armedByKey) are never over-strictly flagged - the linter is STRICT only against spec norms
clean-pack-canaryscenariothe happy path stays clean: a well-formed pack lints exit 0, so a green run is earned, not assumed

The manifest grammar itself - schemaVersion, name, description, version, entry, armedByKey - is on the spec page; the dogfood source lives at packs/public/packstruct-lint-shapes/.

The hosts, by profile

One manifest surface, two execution profiles. A host declares which profile it loads; the manifest never forks. Every host below lints its packs through the same packstruct lint --deep.

hostprofilepacksidswhat it loads packs for
packstruct (dogfood)scenario15The spec attacks itself: four hostile-manifest campaigns drive the real lint CLI and grade it against SPEC v1 section 5.
crashtestscenario947Adversarial QA for agent-built apps: seeded, in-process attacks against real handlers, graded into a hardening ledger CI fails on.
vantscenario24290The agent OS: 24 attack packs that measure its own defenses (kernel, mcp, relay, brain, walls) against the surfaces it promises.
gistoryscenario115E2EE multi-device sync: one chain-relay dialect pack attacks its push/pull sync surface in-process, no sockets.
prestructscenario16AI-first SEO prerender: prestruct-proxy attacks its own HTTP render proxy pair (VPS + Worker) over the real wire.
poststructcheck12-Audit what shipped: walks baked HTML and verifies head, links, and site hygiene against a contract, one check pack per SSG shape.
govstructcheck1442The controller layer for a family of repos: its compliance rules ARE check packs, so governance is a portable /packs surface.
eyestructcheck6-Eyes for production agents: deterministic look / look-diff with a committed visual memory, its capture and canon lanes riding as check packs.
monoforgecheck16The fleet factory: forge-shapes verifies a stamped tree ships its receipt, resolves every path, and holds the truth-slot law.

69 packs across 9 hosts plus the dogfood pack, all linted clean. ids is the declared-id census from lint --deep; - means the packs carry file checks rather than named ids.

Running a packdir

The linter validates the manifest grammar once, at author time and at load. The conformance harness verifies a host's loader honors the spec, so the implements: packstruct@1 pin is verifiable, not honorary.

# manifest + entry + id-census grammar
npx packstruct lint packs/ --deep

# machine-readable verdict
npx packstruct lint packs/ --json

# verify a host loader honors the spec
npx packstruct audit-conformance .

packstruct@1.1.0 is on npm; the conformance harness ships with it, and the dogfood pack above is the proof-of-work.