Choose the question
Narrow the packet to one claim and audience before gathering proof.
Review packet assembly
Prepare one public-safe review handoff before anyone repeats the claim.
This concept guide is a human checklist for gathering public-safe material from existing TraceMap evidence surfaces. It helps reviewers keep the claim, proof path, rule context, coverage, limitations, validation evidence, gaps, and next owner together.
Public claim level: concept. No public conclusion without evidence. This is not a generated packet-builder feature.
Packet question
The packet starts with the claim being reviewed and the audience receiving it.
One claimWrite the bounded sentence or question under review before collecting evidence.
One audienceName whether the handoff is for a reviewer, manager, teammate, service owner, database owner, release owner, or another human owner.
One proof pathAttach a public-safe route, summary, documentation page, rule catalog reference, report-family summary, or private review location named without raw material.
One next ownerRecord who owns the remaining source, test, telemetry, service, database, release, or review question.
Required ingredients
Every packet is incomplete until these fields travel together.
| Ingredient | Public-safe handling |
|---|---|
| claim being reviewed | The exact bounded sentence or question. |
| audience | The receiver for the handoff. |
| proof path | A public-safe trail or named private review location. |
| public claim level | concept for this page unless a later proof surface says otherwise. |
| rule ID or rule family | A deterministic rule basis plus limitation; use a family when the exact ID is not public-safe. |
| evidence tier | Tier1Semantic, Tier2Structural, Tier3SyntaxOrTextual, or Tier4Unknown. |
| coverage label | Transcribe the label from the cited evidence surface without strengthening it. |
| commit SHA | Name the scan context when the public-safe summary exposes it; otherwise record a limitation. |
| extractor version | Name the extractor context when public-safe; otherwise record a limitation. |
| public-safe file path and line span | Use checked-in demo paths or sanitized references, never source excerpts. |
| limitations | State what the evidence cannot prove. |
| non-claims | Keep unsupported runtime, release, safety, ownership, and completeness wording out of the claim. |
| next owner | The person, role, or process responsible for the next question. |
| validation evidence | A public-safe test, command family, review result, or validation summary. |
| unresolved gaps | Reduced, unknown, private-only, syntax-only, or pending review evidence that remains open. |
Assembly workflow
Use the same order every time, especially when the evidence is partial.
Collect public-safe evidence
Use existing TraceMap surfaces and keep a proof path attached to each statement.
Attach limitations
Carry coverage labels, evidence tiers, reduced or unknown coverage, and rule limitations beside the claim.
Name next owners
Assign the remaining human, telemetry, test, release, service, database, code, or review question.
Run claim checklist
Use the review claim checklist; the process cannot upgrade unsupported evidence.
Stop conditions
Block public handoff when a mandatory stop condition is present.
Handoff notes
Write the audience, non-claims, validation evidence, unresolved gaps, and next owner without adding raw or private material.
Stop conditions
Stop assembly when the packet would make the claim stronger than the evidence.
- missing proof path: the public statement needs a public-safe proof path or explicit private-only limitation.
- private-only support: internal evidence may guide follow-up, but public copy waits for a public-safe summary.
- raw artifact leakage: do not include raw facts, raw SQLite content, analyzer logs, source snippets, raw SQL, config values, secrets, local paths, raw remotes, generated scan directories, private names, or hidden validation details.
- unknown or reduced coverage without label: restore the coverage label before handoff.
- unsupported runtime, release, or safety wording: remove claims about runtime behavior, production traffic, endpoint performance, outage cause, release approval or safety, operational safety, production proof, or complete coverage.
- no next owner: the packet must say who handles the remaining question.
- no validation evidence: name what was checked or visibly state what validation is missing.
Handoff notes
Write notes that preserve evidence metadata instead of rephrasing it away.
Review questionThe claim, audience, and bounded public wording.Evidence metadataProof path, rule ID or rule family, evidence tier, coverage label, commit SHA, extractor version, and public-safe file span.LimitsLimitations, non-claims, unresolved gaps, and any unavailable public-safe fields.Follow-upValidation evidence, next owner, and the remaining review or non-static question.Neighboring surfaces
Use assembly for the pre-handoff checklist, not as another catalog.
/packets/General evidence packet artifact model.
/packets/examples/Synthetic evidence packet shapes and stop states.
/manager-packet/Manager-facing summary framing.
/team-evidence-handoff/Receiver-specific handoff language.
/handoff/template/Reusable field template for one bounded static-evidence handoff.
/incident-evidence-handoff/Incident-adjacent static evidence transfer.
/review-room/Meeting agenda for known, partial, and missing evidence.
/decisions/evidence-record/Post-review record for the human owner decision, rejected interpretation, follow-up owner, and residual risk.
/review-claim-checklist/Decision ritual for whether a sentence may be repeated.
/test-planning/Question translation layer for handing static evidence to test owners.
/proof-source-catalog/Route and claim mapping to public-safe source material.
/proof-paths/, /limitations/, /validation/Proof trails, claim boundaries, and public-safe validation context.
Non-claims
TraceMap keeps this workflow bounded to deterministic static evidence and human review.
- TraceMap does not prove runtime behavior, production traffic, endpoint performance, outage cause, release approval or safety, operational safety, complete coverage, AI impact analysis, LLM analysis, autonomous review, or generated packet-builder behavior.
- TraceMap does not replace human review, source review, ownership decisions, telemetry, logs, traces, APM, tests, release controls, incident response, manager judgment, service ownership, or database ownership.
- The workflow helps humans prepare bounded review handoff material from existing static evidence surfaces; it does not approve the claim.