Replay the public corpus, then inspect the right artifact.
The one-command local workflow builds checked-in synthetic Web Forms projects, scans attached and separate provider layouts, retains bounded reports, and refuses unsupported or incomplete acceptance states. It does not need customer code or a database.
Public claim level: demo. The validation receipt below is bound to one exact public synthetic tree and durable Windows result. Workflow orientation without a matching projected artifact remains concept. Raw indexes, facts, logs, test receipts, binaries, source, and machine-local paths remain hidden.
Choose the replay
Local static replay and Windows publication are separate gates.
Default local replayUse PowerShell 7, the documented .NET toolchain, and a fresh output root. pwsh -File scripts/wlocal.ps1 -OutputRoot <fresh-output-root> exercises checked-in public fixtures only.
Authentic publication-RequireWindowsPublish additionally requires mapped and mapless ASP.NET publication on Windows. A non-Windows refusal or skipped Windows theory is not a pass.
Execution boundaryThe workflow builds and analyzes fixture artifacts. It does not launch a Web Forms site, execute fixture database methods, run SQL, or observe a user request.
Exact-tree recipe
Start clean and preserve failures.
Check out the exact tested head shown in the receipt, install the documented prerequisites, choose a new output root, and keep the result folder when a gate refuses admission. Later trees need their own result; this count is not current-head proof.
Website scan and provider scan combined after independent indexing.
The same admitted getter/constructor/profile/provider route shape.
No runtime service or provider selection claim.
separate-dll-only
Provider scan excludes VB source and retains compiled provider evidence.
Three terminal routes remain available through compiled candidates.
Compiled-only candidates do not prove source freshness or execution.
reversed
Provider-first combine order.
The admitted static route and command-state assertions remain the same.
Order independence is bounded to this synthetic corpus. validation.deep-projectless-corpus.v1 · Tier2Structural · bounded-exact-tree-synthetic-layout · exact-tree receipt.
missing
Website source and website DLL without the provider scope.
No invented database route; SelectorNoMatch and other Tier4Unknown gaps stay visible.
Missing evidence is not proof of runtime absence.
Four query views
Bounds and filters stay attached to the result.
allFor the four positive layouts, retains all three admitted static terminal candidates plus explicit gaps for the selected synthetic handler. The missing layout retains gaps and zero paths.
fillFilters to the independent Fill terminal. A zero-unresolved subset does not resolve command values excluded by the filter.
cappedRetains one path and a TruncatedByLimit Tier4Unknown gap. The cap is a coverage boundary, not a severity or completeness judgment.
repeatChecks admitted paths, gaps, and index bytes for deterministic equality. Repeat success does not prove that a prior intermittent failure was fixed. validation.deep-projectless-corpus.v1 · Tier2Structural · bounded-exact-tree-synthetic-layout · exact-tree receipt.
Selected public evidence
Reuse the projection; do not copy the retained run.
Claim level: concept. These examples come from the #806 allowlisted projection, whose illustrative hop IDs, tiers, and spans are not independent extractor-output proof.
Attached and separate
The projected Dynamic email lookup and Literal audit call preserve source, constructor, provider, and API-terminal categories while unresolved operands and branch feasibility remain explicit gaps.
The projected Independent Fill terminal keeps the provider DLL boundary and database API terminal visible without claiming that a runtime implementation was selected or rows were returned.
Missing-provider refusal preserves query gaps instead of inventing a route. The capped view preserves TruncatedByLimit rather than presenting one path as complete coverage.
Windows Server 2025; required mapped and mapless ASP.NET publication.
Counts
148 passed · 0 failed · 0 skipped
The test count includes 2 Windows publication cases, 2 profile dynamic-lookup cases, and 5 operator layouts. Four additional diagnostic-layout admission checks are recorded separately in the receipt.
Covers only the allowlisted privacy-projected input; it is independent of the source receipt.
This exact-tree result remains valid evidence for its named tree. It is historical with respect to later main revisions and must not be relabeled as validation of this page's implementation head.
Failure remains evidence
Refusal is not converted into partial success.
Fail-closed outcomes and owner next steps.
Condition
Outcome
Owner action
Existing output root
DEEP_CORPUS_OUTPUT_NOT_FRESH; tests do not start.
Choose a new empty destination.
Windows publication required on another platform
DEEP_CORPUS_WINDOWS_REQUIRED; no output is written.
Move the exact tree to a suitable Windows runner.
Test process fails
DEEP_CORPUS_TEST_FAILED;outputs-preserved; no admitted validation receipt.
Inspect retained failure evidence; do not call the corpus validated.
Required layout, wizard case, or Windows publication case missing
Run again from a fresh root and bind the new exact tree.
Cap, repeat, comparison, or unresolved-ledger mismatch
Corpus fails rather than reporting a partial pass.
Investigate the changed assertion and retain the failed output.
Non-claims and remaining gaps
The demo stops at deterministic static evidence.
No runtime page, fixture method, database command, branch, provider dispatch, parameter value, or returned-row observation.
No customer compatibility, private application coverage, migration parity, complete cross-service tracing, physical drive-I/O measurement, release approval, or safety-to-run claim.
Candidate bridges, unresolved values, Tier4Unknown gaps, result caps, and partial/reduced coverage remain visible; missing evidence is not runtime absence.
PR #803 diagnostics and scheduling repairs are not ancestors of this page's exact main boundary and are not described as shipped.
No raw SQLite, facts.ndjson, analyzer log, TRX, source snippet, raw SQL, command body, configuration, credential, connection material, private identity, local path, customer artifact, or unpublished validation output is public.
No LLM call, embedding, vector database, or prompt-based classification is part of this evidence.
Continue from reproduction to review.
Use the guided setup for operator choices, the source + compiled proof for the projected chain, review handoff for owner questions, validation for repository-wide gates, outputs for retention boundaries, and limitations before drawing a conclusion. The later review-workbench story will add a dedicated walkthrough.