The showcase

One grammar, many hosts.

packstruct is only worth anything if real projects load it. They do: 69 packs across 9 live hosts, every one linted clean through the same packstruct lint --deep lane. Each card below is a real repo with a real packs/ directory - the counts are receipts from its own tree, not a claim on this page.

The hosts

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.

packstruct

scenario

The spec attacks itself: four hostile-manifest campaigns drive the real lint CLI and grade it against SPEC v1 section 5.

1 pack5 idspackstruct@1.1.0

crashtest

scenario

Adversarial QA for agent-built apps: seeded, in-process attacks against real handlers, graded into a hardening ledger CI fails on.

9 packs47 idspackstruct@1.1.0

poststruct

check

Audit what shipped: walks baked HTML and verifies head, links, and site hygiene against a contract, one check pack per SSG shape.

12 packspackstruct@1.1.0

govstruct

check

The controller layer for a family of repos: its compliance rules ARE check packs, so governance is a portable /packs surface.

14 packs42 idspackstruct@1.1.0

eyestruct

check

Eyes for production agents: deterministic look / look-diff with a committed visual memory, its capture and canon lanes riding as check packs.

6 packspackstruct@1.1.0

vant

scenario

The agent OS: 24 attack packs that measure its own defenses (kernel, mcp, relay, brain, walls) against the surfaces it promises.

24 packs290 idspackstruct@1.1.0

gistory

scenario

E2EE multi-device sync: one chain-relay dialect pack attacks its push/pull sync surface in-process, no sockets.

1 pack15 idspackstruct@1.1.0

monoforge

check

The fleet factory: forge-shapes verifies a stamped tree ships its receipt, resolves every path, and holds the truth-slot law.

1 pack6 idspackstruct@1.1.0

prestruct

scenario

AI-first SEO prerender: prestruct-proxy attacks its own HTTP render proxy pair (VPS + Worker) over the real wire.

1 pack6 idspackstruct@1.1.0

The entry profiles

Every pack declares what it is for through a profile the host owns. One grammar, four declared shapes.

scenario scenario

A module that returns attack verdicts - hostile scenarios driven against a transport, isolated, with the armed-key ceremony available. Loaded by crashtest, vant, gistory, prestruct, packstruct.

check check

A module that returns pass/fail findings - declarative, pure-reading verifiers over files on disk. No transport, no network by default. Loaded by poststruct, govstruct, eyestruct, monoforge.

memory memory

A module that carries a durable memory store - records under the host-owned memstruct grammar (vant's markdown brain). Declared; the memory tier. Bound to memstruct; engine receipt is vant's store.

sync sync

A module that reconciles two memory stores - a pure merge under the host-owned memstruct contract (gistory's merge). Declared; the replicated tier. Bound to memstruct; engine receipt is gistory's merge.

The rest of the family

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

freestruct

engine

Post-build SEO layer for static doc sites: it runs after any SSG and injects the head the docs need.

coreforge

rig

The shell the family ships sites from: landing + docs rig + CI/release plumbing, brand as data.

railyard

composer

The forge yard: the parent service that routes the forges and holds the mounts registry.

Host onboarding in the docs