TraceMap Public Roadmap

Claim levels

Every public page should know what kind of proof it has.

ShippedTrue on main, backed by repository code, docs, rules, tests, or validation commands that can be inspected.

DemoReproducible from checked-in samples or public-safe generated summaries, with the limits visible in the output.

ConceptFuture-facing or planning copy that names the desired workflow without implying it exists yet.

HiddenNot suitable for public copy yet, usually because the proof is local-only, private, raw, unredacted, or still not validated.

Claim ledger

Public wording stays tied to proof paths and limitations.

Public claim level, evidence status, and public wording status are separate axes. A stronger label is not earned by repetition; it is earned only when the proof path changes.
Claim label	Public claim level	Evidence status	Proof path	Limitation	Source-of-truth artifact family	Public wording status
Repository docs and main-backed CLI surfaces	`shipped`	`evidence-backed`	Docs map, capability matrix, and repository docs on `main`.	True on main does not remove maturity caveats, coverage labels, or rule limitations.	Repository docs, validation guide, rule catalog, checked-in CLI source, and test commands.	`live`
Public demo proof rows	`demo`	`partial/reduced coverage`	Demo proof upgrades, demo result, and proof path index.	Demo evidence comes from checked-in public samples and keeps partial analysis labels visible.	Public-safe demo summary, generated report families, rule IDs, evidence tiers, coverage labels, and limitations.	`demo-only`
Optional adapter and unavailable demo rows	`demo`	`gap-labeled demo evidence`	Proof path index rows with `not_requested`, `unavailable`, or `Tier4Unknown` labels.	Gap labels stay visible and must not be restated as parity, success, or clean coverage.	Public-safe demo summary fixture and proof path rows that preserve explicit gap labels.	`demo-only`
Incident, review-room, manager, and adoption concepts	`concept`	`future-only`	Incident review orientation, review room, and manager brief.	Concept pages orient future workflows; they are not shipped capability pages and need public-safe proof before promotion.	Concept route copy, discovery metadata, proof-path links, and documented non-claims.	`future-facing`
Legacy validation and legacy evidence story	`concept`	`not-yet-backed`	Legacy validation concept, legacy evidence story, and limitations.	No stronger support claim exists until a redacted public-safe artifact can show rule IDs, tiers, coverage, and limitations.	Concept pages, validation notes, route metadata, and future sanitized summary requirements.	`future-facing`
Internal-only public wording bucket	`hidden`	`hidden/internal`	No public proof-path or capability-matrix row; this aggregate exists only to keep hidden wording out of public claims.	Do not disclose unreleased capability names, internal route names, private samples, export specifics, counts, cadence, sequencing, or in-flight status.	Local-only validation material until a public-safe summary is reviewed and intentionally published.	`hidden from public navigation`
Unsupported public overclaims	`hidden`	`not-yet-backed`	Limitations and this ledger's non-claims section.	Runtime behavior, production traffic, endpoint performance, outage cause, release safety, operational safety, AI impact analysis, LLM analysis, and complete product coverage wording is forbidden.	Public non-claims, validation guards, and documented limitations.	`forbidden`

The source of truth remains SQLite indexes, fact streams, reports, rule catalog entries, commit metadata, coverage labels, and documented limitations. This ledger is a presentation and governance layer over those deterministic outputs.

Vocabulary mapping

Every public status resolves to one ledger label.

This mapping is the single source for comparing roadmap, capability matrix, proof path index, and discovery metadata labels against ledger labels.
Axis	Existing-surface vocabulary	Claim-ledger label	Resolution note
`claim-level`	`shipped`, `shipped navigation`, `main`, repository docs on `main`, `main with maturity caveats`	`shipped`	Main-backed wording remains limited by maturity caveats and row-specific limitations.
`claim-level`	`demo`, `demo guidance`, `main/demo`, `public-demo`, `public-safe generated summary`, route metadata `publicClaimLevel: demo`, proof-path public status `demo`	`demo`	Demo wording must keep checked-in samples, generated summaries, and proof notes visible.
`claim-level`	`concept`, `concept-only`, `future`, `future-only`, `dev`, `dev-only`, route metadata `publicClaimLevel: concept`, proof-path public status `future`	`concept`	Future-facing and dev-branch-only wording is not upgraded until main or demo proof exists.
`claim-level`	`hidden`, `hidden pending validation`, no capability-matrix row, no proof-path-index counterpart, internal-only aggregate placeholder	`hidden`	Hidden rows are omitted or abstracted without counts, cadence, sequencing, or unreleased names.
`evidence-status`	`Tier1Semantic` or `Tier2Structural` with `Full` or `FullEvidenceAvailable` coverage	`evidence-backed`	Rule IDs, evidence tiers, and proof paths are public-safe and specific.
`evidence-status`	`Partial`, `PartialAnalysis`, `Reduced`, `ReducedCoverage`, or `Tier3SyntaxOrTextual`	`partial/reduced coverage`	Rule-family or proof-path references exist, but coverage gaps remain labeled.
`evidence-status`	`not_requested`, `unavailable`, `Tier4Unknown`, or explicit gap labels on demo rows	`gap-labeled demo evidence`	Gap labels remain visible and are not restated as clean coverage or parity.
`evidence-status`	Proof-path-index `future` entry with no resolvable artifact yet	`future-only`	Proof path is not available yet, so the row is not evidence-backed.
`evidence-status`	No capability-matrix row and no proof-path-index counterpart	`hidden/internal`	Use one aggregate placeholder and disclose no unreleased detail.
`evidence-status`	`UnknownAnalysisGap`, no cited artifact, or no public-safe proof path	`not-yet-backed`	No proof path exists; the claim remains future-facing or forbidden.

Current public surface

The site already has proof-backed entry points.

Capability matrix

Status: demo with per-row main, demo, dev, and future labels. It maps workflows to proof paths without treating the matrix as a completeness promise.

Read capabilities

Public demo result

Status: demo. It explains the generated summary rows, available sections, upgraded proof rows, and public-safe artifact boundary.

Read demo result

Demo proof upgrades

Status: demo. It records combined reports, paths, reverse lookup, portfolio, diff, impact, and release-review evidence from public samples.

Read proof upgrades

Demo proof assets

Status: demo. It provides public-safe visual orientation for generated report summaries without treating visuals as source evidence.

Read proof assets

Evidence packet guide

Status: demo guidance. It shows how managers, reviewers, architects, and engineers should read static evidence packets without overstating them.

Read packet guide

Legacy validation

Status: concept. It describes how messy old repositories should be validated safely before any support claim is upgraded.

Read legacy validation

Legacy evidence story

Status: concept. It keeps WCF, Remoting, WebForms, data metadata, build diagnostics, and flow composition themes hidden until public-safe proof exists.

Read legacy evidence story

Legacy modernization evidence map

Status: concept. It turns modernization planning into reviewer questions over static evidence, hidden surface families, coverage gaps, and proof paths.

Read evidence map

Incident review orientation

Status: concept. It frames static evidence as review or incident-follow-up orientation, not runtime proof, P1 root cause, or release approval.

Read incident review orientation

Vault export

Status: concept. It frames a future optional human exploration layer over the same evidence packet, not a new source of truth.

Read vault concept

Docs map

Status: shipped navigation. It points back to repository docs that define requirements, validation, acceptance, decisions, and adapter contracts.

Read docs map

Next proof upgrades

The next site phases should turn gaps into visible evidence, not louder copy.

Demo proof upgradesThe six formerly deferred demo rows now have reproducible public-demo evidence; keep future copy tied to the proof-upgrades ledger and its visible limits.

Legacy validation summaryMove from concept to demo when redacted local validation output can show labels, counts, rule IDs, evidence tiers, coverage, and limitations without raw private details.

Legacy evidence storyKeep hidden theme rows hidden until a reviewed public-safe artifact can support a narrower public label.

Legacy modernization evidence mapKeep the planning map at concept level until each row has public-safe proof, claim-ledger status, and visible limitations.

Incident review orientationKeep as concept until public-safe evidence can show a complete review packet and still separate static orientation from runtime proof, production cause, and release approval.

Public-safe visualsThe demo proof assets phase adds visual examples only as orientation over generated summaries, reports, facts, indexes, rule IDs, coverage, and limitations.

Vault export demoUpgrade the vault story only when an implementation lands and the export remains a human exploration layer over SQLite, facts, reports, and the rule catalog.

Upgrade rules

A claim changes status only when the evidence changes.

concept -> demoRequires checked-in samples, public-safe generated summaries, and visible limitations.

demo -> shippedRequires the relevant capability to be true on main and traceable to repository code, docs, tests, rules, or validation commands.

hidden -> conceptRequires removing local/private details and reframing the work as future-facing planning copy.

hidden -> demoRequires redaction plus reproducible public-safe evidence, not just a local result.

dev -> shippedRequires promotion to main before the site presents the capability as generally available.

Non-claims

The roadmap keeps several tempting claims out of public copy.

No public conclusion without evidence.
TraceMap does not prove runtime behavior, production traffic, deployment state, endpoint performance, or release safety.
Runtime behavior, production traffic, endpoint performance, outage cause, release safety, operational safety, AI impact analysis, LLM analysis, and complete product coverage wording is forbidden.
TraceMap site copy should not refer to the scanner or reducer as AI analysis.
Concept pages do not make a feature shipped, and hidden local validation does not make a public demo.
Public pages must not publish raw source snippets, SQL, config values, secrets, local absolute paths, raw repository remotes, or private sample identities.

Source material

Follow the roadmap back to current proof.

Capability matrix Proof source catalog Review claim checklist Public demo Current demo result Demo proof upgrades Demo proof assets Evidence packet guide Incident review orientation Legacy validation concept Legacy evidence story Legacy modernization evidence map Vault export concept Docs map Validation Limitations GitHub repository

The public roadmap is a claim ledger, not a promise board.