Teammate
Lead with implementation context, nearby code review, and follow-up questions. Keep summary, proof path, rule ID/rule family, evidence tier, coverage label, limitations, non-claims, local-only artifacts, and next owner/action visible.
Team evidence handoff
Hand a packet to the next receiver without losing the proof boundary.
A TraceMap handoff is concept-level language for giving a teammate, reviewer, manager, or agent the same bounded static evidence packet: what the summary says, where the proof path starts, which rule family explains the evidence, how coverage is labeled, and who owns the next action.
Public claim level: concept. No public conclusion without evidence.
A handoff is complete only when the summary, proof path, rule ID/rule family, evidence tier, coverage label, limitations, non-claims, local-only artifacts, and next owner/action travel together.
The summary is a bounded statement of what static evidence supports, not a substitute for proof details. The proof path points to public-safe proof surfaces or private review locations, not private scanner output on the public site.
Handoff fields
Every receiver gets the same proof-bearing field set.
summaryBounded wording that repeats only what static evidence supports.
proof pathPublic-safe route, review note, or private review location that lets the receiver inspect the basis.
rule ID/rule familyThe deterministic rule context that explains why the evidence exists and where its documented limits begin.
evidence tierThe confidence boundary, using canonical labels such as Tier1Semantic, Tier2Structural, Tier3SyntaxOrTextual, or Tier4Unknown.
coverage labelThe scan or page label that keeps complete, partial, reduced, gap, demo, or concept status visible.
limitationsThe proof boundary that prevents the handoff from becoming a stronger claim than the evidence supports.
non-claimsExplicit statements about what the packet is not proving.
local-only artifactsPrivate working material that stays local unless a human creates a public-safe summary.
next owner/actionThe human owner or review process responsible for the next question.
Receiver patterns
Change the framing, not the evidence fields.
Reviewer
Lead with proof path, rule family, evidence tier, coverage label, limitations, and review gaps. Keep the same summary, non-claims, local-only artifacts, and next owner/action attached.
Manager
Lead with what can be repeated to stakeholders without overclaiming, what remains a non-claim, and which owner/action is next. Keep proof path, rule context, tier, coverage, and limitations nearby.
Agent
Lead with bounded instructions: preserve the proof path, keep local-only artifacts private, retain explicit non-claims, and return the same field set with the next owner/action named.
Neighbor boundaries
Use this route when one receiver needs the next bounded packet summary.
Packet guideUse /packets/ for packet artifact families; use this page for handoff language and receiver context.
Manager packetUse /manager-packet/ for manager-ready summaries; use this page across teammate, reviewer, manager, and agent receivers.
Review roomUse /review-room/ for a shared agenda; use this page for what one person hands to the next receiver.
Manager FAQUse /manager-faq/ for stakeholder questions; use this page for handoff phrases and fields.
Proof catalogUse /proof-source-catalog/ for proof-source families; use this page to preserve proof boundaries in communication.
Boundaries
The handoff preserves what is known, partial, missing, and owned next.
- It does not claim runtime behavior, production traffic, endpoint performance, outage cause, release safety, operational safety, AI impact analysis, LLM analysis, autonomous approval, or complete product coverage.
- It does not replace human ownership, tests, telemetry, release review, code review, source review, logs, traces, incident response, or manager judgment.
- Local-only artifacts are private working material. Do not publish raw facts, raw SQLite content, analyzer logs, raw source snippets, raw SQL, config values, secrets, local paths, raw remotes, generated scan directories, private sample names, credential-like values, or private URLs.
- Private repository evidence needs private review before any public-safe summary is written.
Proof and context