packstruct docs

Showcase

packstruct is only worth anything if real projects load it. They do: 69 packs across nine live hosts, every one linted clean through the same packstruct lint --deep lane. Each row below is a real repo with a real packs/ directory - the counts are receipts from that repo’s own tree, not a claim on this page. The branded version with crosslink cards is at packstruct.creadev.org/showcase.

A host is a repo that ships a packs/ directory and declares which entry profile it loads. The manifest never forks; only the execution semantics do.

The hosts

Host Profile Packs Ids What it loads packs for
packstruct (dogfood) scenario 1 5 The spec attacks itself: four hostile-manifest campaigns drive the real lint CLI against SPEC v1 section 5.
crashtest scenario 9 47 Adversarial QA for agent-built apps: seeded, in-process attacks against real handlers, graded into a hardening ledger CI fails on.
vant scenario 24 290 The agent OS: 24 attack packs that measure its own defenses (kernel, mcp, relay, brain, walls).
gistory scenario 1 15 E2EE multi-device sync: one chain-relay dialect pack attacks its push/pull sync surface in-process.
prestruct scenario 1 6 AI-first SEO prerender: prestruct-proxy attacks its own HTTP render proxy pair (VPS + Worker).
poststruct check 12 - Audit what shipped: walks baked HTML and verifies head, links, and site hygiene, one check pack per SSG shape.
govstruct check 14 42 The controller layer: its compliance rules ARE check packs, so governance is a portable /packs surface.
eyestruct check 6 - Eyes for production agents: its capture and canon lanes ride as check packs.
monoforge check 1 6 The fleet factory: forge-shapes verifies a stamped tree ships its receipt and holds the truth-slot law.

Ids is the declared-id census from lint --deep; - means the packs carry file checks rather than named ids.

The two profiles

The rest of the family

Engines and rigs that compose with the spec without shipping a /packs directory of their own: