Legacy evidence story

Legacy evidence needs a claim ledger before it needs a bigger headline.

This concept page shows how TraceMap may orient reviewers around legacy-adjacent static evidence after a theme has public-safe proof. Until then, the public story is the evidence model, the hidden claim ledger, the promotion gate, and the safety boundary.

Public claim level: concept. Shared site principle: No public conclusion without evidence.

Evidence model

The useful public unit is a labeled evidence row, not a broad support claim.

Rule IDEach public conclusion must name the deterministic rule or rule family that produced the evidence.

Evidence tierRows distinguish compiler-resolved symbols, structural patterns, syntax or textual fallback, and unknown gaps.

Coverage labelReduced analysis remains useful, but it stays labeled partial when builds or project loading fail.

ProvenancePublic-safe rows need repository and commit identity, extractor versions, file paths, line spans, supporting IDs, and limitations.

Artifact boundaryPages may name scan-manifest.json, facts.ndjson, index.sqlite, report.md, and logs/analyzer.log as output types without exposing raw private contents.

Current claim ledger

Every legacy theme remains hidden pending validation.

WCF/service-reference mapping

Label: hidden pending validation.

Future public-safe evidence may summarize config endpoints, service contracts, operation evidence, generated clients, .svc hosts, or ASMX hosts only after redacted proof exists.

Boundary: no public results are claimed from this concept page.

WCF metadata normalization

Label: hidden pending validation.

Future public-safe evidence may describe metadata descriptors and normalization decisions as static evidence with rule IDs and limitations.

Boundary: no binding, endpoint, or compatibility result is claimed here.

.NET Remoting detection

Label: hidden pending validation.

Future public-safe evidence may summarize namespace or type usage, MarshalByRefObject boundaries, channel registration, registration APIs, and config markers.

Boundary: no hosted service, activation, or security result is claimed here.

WebForms event flow

Label: hidden pending validation.

Future public-safe evidence may summarize markup event bindings, code-behind handler resolution, designer fields, and possible static paths to backend code.

Boundary: no browser path or event execution result is claimed here.

Legacy data metadata

Label: hidden pending validation.

Future public-safe evidence may summarize DBML, EDMX, typed DataSet, TableAdapter, provider, and connection-name metadata with hashes, counts, and safe descriptors.

Boundary: no storage presence, query execution, schema compatibility, or production data result is claimed here.

Build diagnostics

Label: hidden pending validation.

Future public-safe evidence may summarize target framework, project style, toolset, SDK, restore, generated-file, and coverage diagnostics.

Boundary: a failed build is never described as a clean repository result.

Flow composition

Label: hidden pending validation.

Future public-safe evidence may compose bounded static paths over existing facts while preserving reduced-coverage and analysis-gap labels.

Boundary: no full impact result or release decision is claimed here.

Promotion gate

A hidden row moves only when the proof moves.

hidden -> conceptAllowed only after local or private details are removed and the copy describes the story shape rather than a public result.

concept -> demoRequires checked-in public-safe artifacts, generated summaries, rule IDs, evidence tiers, coverage labels, and visible limitations on main.

dev-only -> mainRequires promotion to main before the site describes the behavior as true on main.

demo -> stronger claimRequires an implementation-state update naming the exact artifact path, validation command, and supporting rules.

Safety boundary

This page is a public-safe story shape, not a legacy support announcement.

No runtime proof, UI reachability, production traffic, deployment state, endpoint performance, exploitability, database existence, package compatibility, incident cause, release approval, or release safety is claimed by this concept page.
Static evidence summaries should use labels, counts, hashes, rule IDs, evidence tiers, coverage labels, supporting IDs, limitations, commit provenance, and extractor versions.
Private sample identities, local paths, repository remotes, raw generated artifact contents, source snippets, SQL text, config values, connection strings, secrets, and credential values stay out of public copy.
AI impact analysis, LLM calls, embeddings, vector databases, and prompt-based classification are not part of the TraceMap scanner or reducer story.

Next reading

Follow the boundary back to current public pages.

Legacy validation concept Legacy modernization evidence map Public roadmap Evidence model Limitations Proof path index Evidence packet guide Validation Docs map