Review claim checklist
Check the sentence before anyone repeats it.
This concept-level checklist turns TraceMap's public claim boundary into a small review ritual for managers, reviewers, agents, and engineers preparing public or internal summaries.
Public claim level: concept. No public conclusion without evidence. This checklist is a repeat-before-reuse control; it is not a proof catalog, release gate, operational decision, or impact conclusion.
Ritual
Every repeatable claim keeps its evidence attached.
Write the exact claim statementReview the sentence as it will be repeated, not a stronger or friendlier paraphrase.
Attach proof vocabularyKeep the proof path, rule ID or rule family, evidence tier, coverage label, limitation, and non-claims beside the sentence.
Separate level from outcomePublic claim level is
shipped, demo, concept, or hidden; review outcome says what the reviewer should do next.Record source status and ownerSource branch or main-dev status is part of the proof path, and owner follow-up names the responsible role plus requested action.
Checklist row
Use one row per claim under review.
| Field | Allowed or required value | Review check |
|---|---|---|
| claim statement | The exact public claim or internal review statement. | Internal statements still need evidence before they move outside their original context. |
| public claim level | shipped, demo, concept, or hidden. |
Discovery metadata may use main, but a checklist row maps that to shipped. |
| proof path | A public-safe page, generated summary, documentation page, rule catalog page, report summary, demo artifact, or proof path entry. | No proof path means the claim cannot be upgraded by confidence, seniority, repetition, or manager pressure. |
| rule ID or rule family | Specific rule ID when public-safe; otherwise rule family plus a limitation. | No evidence without a rule ID or documented rule-family limitation. |
| evidence tier | Tier1Semantic, Tier2Structural, Tier3SyntaxOrTextual, or Tier4Unknown. |
Do not present syntax-only or unknown evidence as semantic proof. |
| coverage label | The label transcribed from the cited public-safe artifact or summary. | Reduced, partial, unknown, unavailable, or future-only labels stay visible and force downgrade or owner follow-up unless a public proof surface says otherwise. |
| limitation | The row's canonical limitation field. | State what the evidence cannot support; do not bury the limit in surrounding prose. |
| non-claims | What this specific claim must not imply. | Page-level non-claims apply to every row; row-level non-claims catch claim-specific overreach. |
| source branch or main-dev status | main, checked-in public demo, dev-only, future-only, hidden, or local-only. |
main or checked-in public demo evidence can support stronger wording than dev-only, future-only, hidden, or local-only evidence. |
| owner follow-up | Responsible role and requested action. | Use owner follow-up needed when the claim cannot be repeated until that owner action happens. |
| reviewer | Synthetic role label in examples; real reviewer only in private working material. | Do not publish real internal reviewer identities in example or template rows. |
| review date | Synthetic example date or private working date. | Do not publish real internal review dates, timing, cadence, or sequencing in examples. |
| decision | repeat with proof, downgrade before repeating, owner follow-up needed, do not repeat, or internal only. |
The outcome controls reuse; it does not upgrade the evidence level. |
Stop conditions
Some rows cannot be repeated yet.
missing proof pathHold or downgrade the claim until a public-safe proof path exists.private-only artifactUse private evidence for internal follow-up only until a public-safe summary exists.hidden claim detailAbstract or omit hidden detail; do not publish unreleased names, private sample identities, counts, cadence, sequencing, or in-flight status.unsupported demo claimA concept checklist is not evidence that the underlying behavior is shipped or demo-backed.forbidden wordingDo not repeat runtime, release, operational, complete-coverage, AI impact, or LLM analysis wording as a TraceMap claim.Illustrative examples
Example rows use synthetic placeholders only.
| Claim statement | Level | Proof path | Rule | Tier | Coverage | Limitation | Non-claims | Status | Owner follow-up | Reviewer | Review date | Decision |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Public demo summary preserves partial coverage labels. | demo |
Proof path index | public.demo.summary.v1 |
Tier2Structural |
PartialAnalysis |
Demo rows describe checked-in public samples and keep reduced labels visible. | Not complete coverage or product-wide parity. | checked-in public demo | Docs owner role: keep proof link attached. | Reviewer role | Example date | repeat with proof |
| A future review workflow should require owner notes. | concept |
Review-room agenda | review-workflow rule family | Tier2Structural |
future-only |
Concept guidance is not shipped product behavior. | Not release approval or operational proof. | future-only | Workflow owner role: publish public-safe proof before upgrade. | Reviewer role | Example date | owner follow-up needed |
Non-claims
The checklist does not turn static evidence into operational proof.
- TraceMap does not prove runtime behavior, production traffic, endpoint performance, outage cause, release safety, operational safety, AI impact analysis, LLM analysis, or complete product coverage.
- TraceMap does not replace telemetry, logs, traces, tests, source review, ownership decisions, incident response, or release approval.
- A successful checklist does not assign impact status or say a system is safe, unsafe, approved, blocked, root cause, validated for release, production proven, or complete.
- Future agents must not repeat a claim after dropping its rule ID, evidence tier, coverage label, limitation, non-claims, or proof path.
Private material
Name artifact families without publishing raw internals.
Forbidden public page contentRaw
facts.ndjson, raw index.sqlite, analyzer logs, raw source snippets, raw SQL, config values, secrets, local absolute paths, raw repository remotes, generated scan directories, and private sample names.Allowed source-of-truth categoriesFact streams, SQLite indexes, reports, rule catalog entries, commit metadata, coverage labels, generated summary families, and documented limitations may be named as local or public-safe categories.
Public proof path ruleRaw artifacts are not public proof links; cite reviewed summaries, public pages, docs, rule catalog pages, or demo artifacts instead.
Adjacent surfaces
This checklist answers one narrow question.
Review roomMeeting agenda for known, partial, and missing evidence; not proof that a claim is repeatable.
Manager FAQStakeholder explanation of static evidence boundaries; not the source of proof.
Proof path indexEvidence-trail index for public-safe proof paths; use it to find the cited support.
Claim ledgerVocabulary source for claim levels; this checklist applies the vocabulary to a sentence under review.
Proof-bounded routes