what

One spec, a lint CLI, a harness.

packstruct is two artifacts: the normative SPEC that defines a/packs directory, and a zero-dependency CLI that checks a manifest against it.

The manifest (pack.json, v1)

A pack is a directory under packs/public/<name>/ carrying a frozen pack.json: schemaVersion: 1, a kebab-case name matching its directory, a dotted version, a one-line description, a relative entry that must exist, and an optional armedByKey. Every field is checked, and every refusal names the field it refused.

The profiles

A pack declares what it is for through a profile. The scenario profile is what crashtest, vant, gistory, and prestruct load: a module that returns attack verdicts. The check profile is what poststruct, govstruct, eyestruct, and monoforge load: a module that returns pass/fail findings. One grammar, two declared shapes, so a host knows what a pack will do before it runs it.

The CLI and the conformance harness

The linter walks a /packs directory and refuses a malformed manifest with a field-named message. The conformance harness goes further: it proves a loader honors every case in the spec, so a host cannot claim conformance it does not have.

# lint a /packs dir against SPEC v1
npx packstruct lint packs --deep

# prove a host loader honors every spec case
npx packstruct audit-conformance . --loader "node loader.mjs {packs}"

See who loads itNext: about the projectConformance harness docs