RicheyWorks · RicheyWorks · May 16, 2026
@@ -28,7 +28,7 @@ Recommended first paths:
 - I want the shortest public-facing overview: start with [`EXECUTIVE_SUMMARY.md`](EXECUTIVE_SUMMARY.md), then use [`PRODUCTION_READINESS_SUMMARY.md`](PRODUCTION_READINESS_SUMMARY.md) for the production-candidate snapshot, [`SRE_DEMO_HIGHLIGHTS.md`](SRE_DEMO_HIGHLIGHTS.md) for the product-value/guardrail one-pager, and [`DEMO_WALKTHROUGH.md`](DEMO_WALKTHROUGH.md) for a local demo script.
 - I want to verify tests and coverage: start with [`TESTING_COVERAGE.md`](TESTING_COVERAGE.md), then inspect the `jacoco-coverage-report` workflow artifact and CI skipped-test log output.
 - I want to verify real HTTP proxy behavior: start with [`REVERSE_PROXY_MODE.md`](REVERSE_PROXY_MODE.md), [`REVERSE_PROXY_HEALTH_AND_METRICS.md`](REVERSE_PROXY_HEALTH_AND_METRICS.md), [`REVERSE_PROXY_RESILIENCE.md`](REVERSE_PROXY_RESILIENCE.md), [`PROXY_OPERATOR_STATUS_UI.md`](PROXY_OPERATOR_STATUS_UI.md), the source-visible `LocalOnlyRealBackendProxyValidationTest`, and the reviewer export from `LocalProxyEvidenceExportTest` under `target/proxy-evidence/local-proxy-evidence.md`.
-- I want to inspect request-level routing decisions: open `/routing-demo.html` and use the Reviewer Workflow Checklist, Evidence Associations, Association Legend, Routing Proof Summary, Scenario Comparison, Reviewer Confidence Signals, and Evidence Navigation reviewer path for selected scenario-to-decision mapping, selected strategy/backend, scenario-to-scenario what-changed notes, visible input signal deltas, unhealthy-candidate degradation/recovery notes, local verification commands, routing-to-evidence dashboard links, copyable association summary, an end-to-end reviewer walkthrough, and explicit not-proven limits.
+- I want to inspect request-level routing decisions: open `/routing-demo.html` and use the Reviewer Workflow Checklist, How This Proof Works, Evidence Associations, Association Legend, Routing Proof Summary, Scenario Comparison, Reviewer Confidence Signals, and Evidence Navigation reviewer path for selected scenario-to-decision mapping, selected strategy/backend, scenario-to-scenario what-changed notes, visible input signal deltas, unhealthy-candidate degradation/recovery notes, local verification commands, routing-to-evidence dashboard links, copyable how-to reviewer explanation, copyable association summary, an end-to-end reviewer walkthrough, and explicit not-proven limits.
 - I want to run local proxy demos: start with [`PROXY_DEMO_STACK.md`](PROXY_DEMO_STACK.md), [`PROXY_DEMO_FIXTURE_LAUNCHER.md`](PROXY_DEMO_FIXTURE_LAUNCHER.md), and [`PROXY_STRATEGY_DEMO_LAB.md`](PROXY_STRATEGY_DEMO_LAB.md).
 - I want to adapt proxy mode to local/private backends: start with [`REAL_BACKEND_PROXY_EXAMPLES.md`](REAL_BACKEND_PROXY_EXAMPLES.md).
 - I want to choose the right run profile: start with [`OPERATOR_RUN_PROFILES.md`](OPERATOR_RUN_PROFILES.md) for local demo, packaged jar, prod API-key, cloud-sandbox API-key, OAuth2, proxy-loopback, and container recipes.
@@ -83,6 +83,10 @@ Use the Evidence Associations panel on `/routing-demo.html` to connect selected
 
 The Association Legend keeps the proof language readable: scenario = demo input state, strategy = selected routing method, backend/server = selected local candidate from the sample response, signals = local/demo metrics used for explanation, and evidence pages = reviewer navigation aids, not production certification. This association map does not prove production traffic, live cloud behavior, real tenant behavior, registry publication, container signing, or production certification.
 
+### Cockpit How-Question Guide
+
+Use the How This Proof Works panel on `/routing-demo.html` when a reviewer asks how to interpret the selected decision, reproduce the proof, read edge cases, understand strategy choice, or follow evidence support. The copyable how-to reviewer explanation is browser-local text assembled from visible page guidance and local comparison state only: no upload/share endpoint, no server-side export/PDF/ZIP generation, no external calls, no telemetry, no production traffic proof, no live cloud proof, no real tenant proof, no registry publication proof, no container signing proof, no GitHub settings mutation proof, and no production certification claim.
+
 ## Reviewer Demo Path
 
 Use this path when a reviewer wants to understand the project and verify the current evidence story in about five minutes without enabling live private-network behavior.
@@ -95,7 +99,7 @@ What can be proven quickly:
 2. Operator evidence dashboard: open `http://localhost:8080/operator-evidence-dashboard.html` for local/CI evidence locations, smoke output paths, dry-run artifact metadata, and the local-only `GET /api/enterprise-lab/operator-evidence-summary` response.
 3. Evidence timeline: open `http://localhost:8080/evidence-timeline.html` for local/CI evidence stages, generated evidence locations, the dry-run artifact name, and a reusable run template.
 4. Evidence export packet: open `http://localhost:8080/evidence-export-packet.html` for the reviewer handoff checklist, packet template, reviewer packet share checklist, browser-local Markdown/JSON packet downloads, browser print/save-as-PDF styling, dashboard links, CI artifact name, not-proven boundaries, and the local-only `GET /api/enterprise-lab/evidence-export-packet` response. The downloads, print flow, and share checklist are generated in the browser and do not send, upload, or create server-side files, PDFs, or share artifacts.
-5. Local routing/cockpit behavior: open `http://localhost:8080/routing-demo.html` for the Reviewer Workflow Checklist, Evidence Associations, Association Legend, Routing Proof Summary, Scenario Comparison, Reviewer Confidence Signals, Evidence Navigation reviewer path, selected scenario-to-decision mapping, selected strategy/backend, scenario-to-scenario what-changed notes, visible input signal deltas, degradation/recovery notes, local verification commands, routing-to-evidence dashboard links, copyable evidence association summary, copyable end-to-end reviewer walkthrough, and explicit not-proven boundaries; then open `http://localhost:8080/` and `http://localhost:8080/load-balancing-cockpit.html`.
+5. Local routing/cockpit behavior: open `http://localhost:8080/routing-demo.html` for the Reviewer Workflow Checklist, How This Proof Works, Evidence Associations, Association Legend, Routing Proof Summary, Scenario Comparison, Reviewer Confidence Signals, Evidence Navigation reviewer path, selected scenario-to-decision mapping, selected strategy/backend, scenario-to-scenario what-changed notes, visible input signal deltas, degradation/recovery notes, local verification commands, routing-to-evidence dashboard links, copyable how-to reviewer explanation, copyable evidence association summary, copyable end-to-end reviewer walkthrough, and explicit not-proven boundaries; then open `http://localhost:8080/` and `http://localhost:8080/load-balancing-cockpit.html`.
 6. Local proxy forwarding evidence: run `mvn -Dtest=LocalProxyEvidenceExportTest test`, then inspect `target/proxy-evidence/local-proxy-evidence.md` and `target/proxy-evidence/local-proxy-evidence.json`.
 7. Private-network profile dry-run evidence: run `mvn -Dtest=PrivateNetworkProxyDryRunEvidenceTest test`, then inspect `target/proxy-evidence/private-network-validation-dry-run.md` and `target/proxy-evidence/private-network-validation-dry-run.json`.
 8. Private-network live loopback proof: run `mvn -Dtest=PrivateNetworkLiveValidationExecutorTest test`, then inspect `target/proxy-evidence/private-network-live-loopback-validation.md` and `target/proxy-evidence/private-network-live-loopback-validation.json`.
@@ -135,6 +139,7 @@ Safety boundaries preserved by this path:
 | Where is the reviewer evidence export packet? | Static browser dashboard and local summary API | `/evidence-export-packet.html`, `GET /api/enterprise-lab/evidence-export-packet`, `src/main/resources/static/evidence-export-packet.html` | Reviewer handoff checklist, reviewer packet share checklist, browser-local Markdown/JSON downloads, browser print/save-as-PDF styling, copyable packet template, evidence paths, dashboard/API links, CI artifact metadata, not-proven boundaries, residual risks, and follow-up gates | Reviewers can assemble, download, print, or share-check a consistent human-readable handoff packet from existing local/CI evidence without server-side file creation, uploads, releases, signatures, registry publications, or production-readiness claims | Production certification, registry publication, container signing, live cloud validation, real tenant proof, server-side export/share artifact creation, or GitHub settings mutation |
 | How do routing decisions connect to reviewer evidence pages? | Static browser routing demo association panels | `/routing-demo.html`, `RoutingDecisionDemoTest`, `src/main/resources/static/routing-demo.html` | Evidence Associations, Association Legend, copyable evidence association summary, selected scenario-to-decision mapping, selected strategy/backend mapping, key input signal mapping, scenario comparison delta, evidence page links, export packet handoff link, and local/demo-only not-proven boundaries | Reviewers can trace how a synthetic scenario, routing decision, selected backend, visible signals, scenario delta, evidence pages, timeline, and handoff packet relate without adding server-side exports or external calls | Production traffic proof, live cloud proof, real tenant proof, production certification, registry publication, container signing, upload/share endpoint behavior, or server-side export/PDF/ZIP generation |
 | How should a reviewer walk the routing cockpit end-to-end? | Static browser routing demo workflow panels | `/routing-demo.html`, `RoutingDecisionDemoTest`, `src/main/resources/static/routing-demo.html` | Reviewer Workflow Checklist, Reviewer Confidence Signals, copyable end-to-end reviewer walkthrough, Evidence Navigation links, and local/demo-only not-proven boundaries | Reviewers can follow a repeatable local sequence from sample scenario to routing comparison, proof summary, scenario deltas, evidence dashboards, timeline, and evidence export packet without leaving static/browser-local surfaces | Production deployment certification, live cloud validation, real tenant traffic proof, production SLA/SLO evidence, upload/share endpoint behavior, server-side export/PDF/ZIP generation, registry publication, or container signing |
+| How should reviewers interpret routing proof details and edge cases? | Static browser routing demo how-question guide | `/routing-demo.html`, `RoutingDecisionDemoTest`, `src/main/resources/static/routing-demo.html` | How This Proof Works, How to Interpret This Decision, How to Reproduce This Proof, How to Read Edge Cases, How Strategy Choice Matters, How Evidence Supports the Decision, copyable how-to reviewer explanation, and local/demo-only not-proven boundaries | Reviewers can answer how the selected backend was chosen, how strategy and input signals influenced the proof, how edge cases should be read, how to reproduce the local proof, and how evidence pages support the decision without leaving static/browser-local surfaces | Production traffic proof, live cloud proof, real tenant proof, production certification, registry publication, container signing, GitHub settings mutation proof, upload/share endpoint behavior, or server-side export/PDF/ZIP generation |
 | How do routing proof scenarios compare? | Static browser routing demo and local compare API | `/routing-demo.html`, `RoutingDecisionDemoTest`, `src/main/resources/static/routing-demo.html` | Routing Proof Summary, Scenario Comparison, Evidence Associations, Evidence Navigation reviewer path, previous/current scenario names, selected strategy/backend delta, input signal deltas, degradation/recovery notes, routing-to-evidence dashboard links, copyable local reviewer summary, copyable evidence association summary, and copyable end-to-end reviewer walkthrough | Reviewers can compare the packaged normal-load baseline against edited local demo payloads using same-origin local API responses, browser-local copy text, and static links to the reviewer/operator/timeline/export packet pages | Production deployment certification, live cloud validation, real tenant traffic proof, production SLA/SLO evidence, server-side export/share artifact creation, registry publication, or container signing |
 | What governance changes are prepared but manual? | Repo-side governance hardening packet | [`MANUAL_GITHUB_GOVERNANCE_HARDENING.md`](MANUAL_GITHUB_GOVERNANCE_HARDENING.md), [`../.github/CODEOWNERS`](../.github/CODEOWNERS) | CODEOWNERS coverage, current observed ruleset state, manual settings checklist, stale-review recommendation, and evidence expectations | Reviewers can see ownership and target governance decisions without assuming GitHub settings were changed | Applied ruleset mutation, required review enforcement, branch-protection mutation, or production governance certification |
 | Is this enterprise-ready? | Current enterprise-readiness audit | [`ENTERPRISE_READINESS_AUDIT.md`](ENTERPRISE_READINESS_AUDIT.md) | Current `main`/`v2.5.0` audit, GitHub ruleset and alert snapshot, Enterprise Lab transition decision, remaining gaps | Reviewers can distinguish Enterprise Lab readiness from production enterprise readiness | Production gateway certification, deployment approval, real IdP tenant proof, live cloud validation, or container signing |