1. identify the claim
Name the exact claim first; stop if it bundles several conclusions.
Reviewer quickstart
Inspect the claim, proof path, and limits before repeating the packet.
This concept guide helps a code reviewer, maintainer, reviewer agent, or engineering owner inspect a TraceMap evidence packet or public-safe proof trail in about five minutes. It is the first-stop orientation, not the complete review workflow.
Public claim level: concept. No public conclusion without evidence. This page is reviewer-facing guidance for static evidence packets, not a release gate, approval system, source-review substitute, test substitute, runtime observability substitute, or automated decision.
Start Here
Begin with the claim and stop if there is no evidence trail.
Name the claimWrite the exact sentence under review before reading supporting material.
Find the proof pathUse a public-safe route, summary, documented trail, or named private review location that does not expose raw material.
Keep fields attachedCarry claim level, rule, tier, coverage, commit or source context, extractor context, limitations, non-claims, validation evidence, gaps, and next owner together.
Stop on absenceMissing evidence creates a follow-up owner question, not a clean conclusion.
Five-Minute Review
Use the same order before a claim is repeated, upgraded, or routed.
2. find the proof path
Locate a public-safe route, summary, documented source trail, or named private review location; stop if the trail is absent.
3. check public claim level
Keep concept, demo, shipped, hidden, or other supported vocabulary from being upgraded by confidence or repetition.
4. read rule ID/family
Confirm the deterministic rule ID or documented rule family before repeating evidence-backed wording.
5. inspect evidence tier and coverage label
Read Tier1Semantic, Tier2Structural, Tier3SyntaxOrTextual, or Tier4Unknown with the coverage label.
6. check commit/extractor context
Check the commit SHA or source revision and extractor version or extractor family when public-safe; otherwise record the limitation.
7. read limitations/non-claims
Carry limitations and non-claims with the claim instead of treating them as footnotes.
8. name next owner
Route missing validation, source, test, runtime, release, or ownership questions to a human owner category.
9. stop on missing evidence
Do not repeat, upgrade, approve, or route a stronger claim when required evidence is missing.
Evidence Fields
Expect these public-safe fields before treating a packet as reviewable.
| Field | Reviewer check |
|---|---|
| claim | The exact sentence or question under review. |
| proof path | Public-safe route, summary, documented trail, or named private review location. |
| public claim level | The visible claim-strength boundary for this page or packet. |
| rule ID or rule family | Deterministic rule basis and documented limitation. |
| evidence tier | Tier1Semantic, Tier2Structural, Tier3SyntaxOrTextual, or Tier4Unknown. |
| coverage label | The exact coverage state from the cited evidence. |
| commit SHA or source revision context | Source revision context when public-safe and available. |
| extractor version or extractor family | Extractor context when public-safe and available. |
| file path and line span when public-safe | Checked-in public demo paths or sanitized source references, never raw source. |
| limitation | What the evidence cannot prove. |
| non-claim | What the reviewer must not infer. |
| validation evidence | Public-safe command family, review summary, test summary, or validation status. |
| unresolved gap | Reduced, syntax-only, unknown, private-only, or pending owner evidence. |
| next owner | The human owner category for the remaining question. |
Stop Conditions
Stop when the packet would make the public claim stronger than the evidence.
- missing proof path: no public-safe route, summary, documented trail, or named private review location.
- missing rule ID or rule family: no deterministic rule basis or documented family.
- missing evidence tier: tier strength is absent or unlabeled.
- missing coverage label: coverage state is missing from the cited evidence.
- missing limitation: the claim omits what the evidence cannot prove.
- missing public claim level: the route or packet does not show concept, demo, shipped, hidden, or another supported level.
- missing commit or extractor context without explicit limitation: source revision or extractor context is absent and not explained.
- no validation evidence: no public-safe validation status, test summary, review summary, or command family is named.
- no next owner: the remaining question has nowhere to go.
- private-only support presented as public proof: private evidence is treated as public support.
- raw artifact leakage: 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, raw command output, hidden validation details, or credential-like values appear in public copy.
- unsupported wording: runtime, release, safety, production, AI/LLM, autonomous approval, or complete-coverage language appears outside explicit boundary copy.
Safe Review Language
Use bounded verbs and keep unsupported conclusions out of the sentence.
Use
inspect, check, follow, review, compare, label, record, route, escalate, or cannot conclude from this packet.SayThis packet shows where to inspect the public-safe proof path, rule basis, tier, coverage, context, limitations, and next owner before repeating the claim.
AvoidDo not call a change, endpoint, service, vendor system, team, release, dependency, database reference, or packet approved, blocked, root cause, production-proven, complete, or impact-bearing from this quickstart.
RouteWhen evidence is missing, name the owner question instead of turning absence into confidence.
Escalation Owners
Route gaps to owner categories, not blame.
reviewer ownerClaim wording, packet scope, and repeat-or-hold decision.source review ownerSource-level interpretation when the static proof path is insufficient.code ownerImplementation area, ownership context, and next source question.service ownerService context beyond static packet evidence.database ownerDatabase reference or schema questions outside the public-safe packet.test ownerTest evidence, missing test summary, or validation gap.validation ownerValidation status, review summary, and command-family evidence.telemetry or runtime ownerRuntime observability, production, endpoint, or incident questions outside static evidence.release ownerRelease process questions that static evidence cannot approve.manager or decision ownerHuman decision routing when evidence is reduced, private-only, or missing.Non-Claims
The quickstart reads evidence packets; it does not expand what they prove.
- This quickstart and cited packets do not prove runtime behavior, production traffic, endpoint performance, outage cause, release approval, release safety, operational safety, or complete coverage.
- They do not perform AI impact analysis, LLM analysis, embeddings, vector database analysis, prompt classification, autonomous approval, or release approval.
- They do not replace tests, code review, source review, runtime observability, telemetry, service ownership, release controls, or human judgment.
- The reviewer may inspect, compare, record, route, or escalate; they cannot conclude from this packet when required evidence is missing.