Summaries are linked to sources
Each packet category identifies the local tool that produced it and preserves available timestamps. Open the source tool when the underlying detail needs review.
RELEASE PACKET BUILDER
Put the evidence
in one handoff.
Consolidate the current browser-local job signals into one exportable snapshot with explicit missing and blocking categories. The packet is a record of what the tools know, not an automatic authorization to print.
✓ Local state✓ Explicit status✓ Exportable evidence
Build a portable release snapshot
The packet reads supported browser-local signals and packages summaries plus timestamps. It does not include selected image bytes, proof images or arbitrary uploaded documents.
Evidence inventory
Signals found0supported categories
Blocking signals0explicitly unresolved
Packet stateDRAFTsummary only
A release packet should preserve the assumptions that produced the decision.
Missing stays missing
The packet does not auto-fill absent cost, risk, approval or file evidence. A clean export can therefore show an incomplete record instead of presenting a polished but invented sign-off.
JSON is intentionally portable
The export is plain structured data that can be archived with a job. It contains text and numeric summaries from supported local signals, not the original image files.