Evidence Pack Index¶

Provenance-first catalog of every reproducible evidence pack in this guide. Each troubleshooting lab under labs/ ships an evidence/ directory containing the raw Azure captures — deployment JSON, CLI output, KQL results, gate verdicts, and curl probes — that back the lab's falsification claim. This page is the single entry point for auditing that evidence.

Use the Lab Finder when you know a symptom and want the matching reproduction lab. Use this page when you want to inspect the raw evidence a lab captured, verify its provenance, or reuse a capture as a baseline instead of redeploying.

What an evidence pack contains¶

Every evidence pack is captured in a single live-Azure window by the lab's own trigger.sh (failure cohort) and fix-and-capture.sh / verify.sh (recovery cohort), then PII-scrubbed before commit. A typical pack carries four artifact classes.

flowchart TD
    A[Lab trigger.sh + fix-and-capture.sh] --> B[Raw captures]
    B --> C[Deployment + CLI JSON]
    B --> D[System + Console log excerpts]
    B --> E[KQL result sets]
    B --> F[Gate verdict JSON]
    C --> G[PII scrub]
    D --> G
    E --> G
    F --> G
    G --> H[evidence/ directory + provenance README.md]
    H --> I[Lab guide references pack as falsification evidence]

PII-scrubbing guarantee¶

Every committed evidence artifact is scrubbed before it enters the repository, per the AGENTS.md PII rules:

• Subscription, tenant, object, and workspace GUIDs are replaced with the zero-GUID placeholder 00000000-0000-0000-0000-000000000000.
• Employee aliases are replaced with demouser; employee emails with user@example.com.
• Synthetic example identifiers (demo correlation IDs, ACR Tasks build-volume IDs) are retained deliberately to aid readability and are called out as synthetic in each provenance README.

If you find a raw Azure identifier in any evidence artifact, treat it as a P0 leak and open an issue.

Evidence pack catalog¶

All 30 evidence-bearing labs, alphabetical. Files / JSON / Gates are current artifact counts. Provenance marks whether the pack carries a dedicated evidence/README.md. Captured is the live-Azure capture date (from the provenance README, or the gate verdict timestamp where no README exists yet).

How to use an evidence pack¶

1. Audit a falsification claim. Open the lab guide's Falsification / Experiment Log section, then open the matching *-gate.json to see the exact predicate that was evaluated and its pass/fail verdict.
2. Reuse a capture as a baseline. When a smoking-gun signal is deterministic (for example MANIFEST_UNKNOWN in acr-pull-failure), the provenance README documents the JSONPath so you can validate a new predicate against the captured schema instead of redeploying.
3. Verify PII hygiene. Every artifact is scrubbed; the provenance README lists every substitution. Use it to confirm no raw Azure identifier survives before citing an artifact externally.

See Also¶

• Lab Finder — Symptom-first routing to the matching reproduction lab
• Lab Guides catalog — Browse every lab by difficulty and duration
• Evidence Map — Signal-to-lab evidence mapping
• Methodology — Detector map and the evidence-integrity model behind every gate
• KQL Query Library — Production queries that generated the KQL result sets in these packs
• Contributing Guide — PII rules and evidence-capture standards

Sources¶

• Azure Container Apps troubleshooting overview
• Monitor logs in Azure Container Apps with Log Analytics
• Troubleshoot container start failures
• Azure Container Apps revisions