# An exporter-generated fixture pack

This is actual statusgen output against the existing public Assay fixture. It is not a customer change, real release, executed acceptance test or approval. The illustrative admin-only export story on the website is a different teaching example.

Generated on 6 October 2026 with installed statusgen v1.0.32. The fixed `-generated` parameter is 2026-10-06T00:00:00Z. The exporter completed with exit 0; its requirement verdicts remain `partial` and `could-not-check`. The deliberate missing link appears in the report and the manifest's `omitted` array.

## Reproduce

In a checkout of the public medici-finance/assay repository containing revision fc5afe37f, create an empty sibling directory named `fixture`. Run the following commands from the repository root, using `../fixture` consistently:

```sh
git archive fc5afe37f \
  docs/release-notes/v0.0.0-fixture.md \
  docs/streams/audit-pack-example \
  docs/streams/requirements/apfixture-ok.md \
  docs/streams/requirements/apfixture-unresolved.md | tar -x -C ../fixture
statusgen --root ../fixture --export-audit-pack \
  --release v0.0.0-fixture -o audit-pack.tgz \
  -generated 2026-10-06T00:00:00Z
```

Use statusgen v1.0.32 for byte comparison. `provenance.json` records the tool and archive hashes, command and selected input paths. Two local exports were byte-identical. Every bundled content file matches its SHA-256 in `manifest.json`.

Read `audit-pack-report.json` and `manifest.json` together. Hashes support comparisons with a trusted reference; they are not signatures. The pack contains authored requirements, a todo fixture brief and a declared fixture scope. It does not automatically include performance, action or application security logs.