# Phase 168.1: Analytical Runtime Surface And Proof Lane - Context

**Gathered:** 2026-04-13
**Status:** Ready for planning

<domain>
## Phase Boundary

This phase takes the richer analytical-check row contract from Phase `168`
and makes it visible on the runtime/read-path surfaces humans actually inspect.
It also closes the milestone with one bounded analytical cross-check proof lane.
It does not reopen the row-level analytical-review contract except for narrow
compatibility fixes needed to render the new runtime surface cleanly.

</domain>

<decisions>
## Implementation Decisions

### Runtime/read-path parity
- **D-01:** Keep `analytical_review.json` as the durable theory-packet artifact
  and keep `validation_review_bundle.active.json/.md` as the primary analytical
  read path. Phase `168.1` should surface the richer contract there rather than
  inventing a parallel runtime family.
- **D-02:** `status --json`, `runtime_protocol.generated.json/.md`, and the
  primary analytical review-bundle path must expose the same bounded analytical
  cross-check surface. The operator should not need to open raw
  `analytical_review.json` just to inspect the check rows.
- **D-03:** The runtime surface should stay structured, not summary-only. At
  minimum it must expose overall analytical status, candidate identity, counts,
  and per-check rows with kind, status, source anchors, assumption or regime
  context, reading-depth posture, and notes.

### Proof boundary
- **D-04:** Close the milestone with one dedicated bounded analytical
  cross-check acceptance lane. A dedicated acceptance script is preferred over
  silently overloading the older analytical-judgment acceptance.
- **D-05:** Keep the existing analytical-judgment acceptance lane working. The
  new proof lane augments it as the milestone-close proof, not as a
  replacement.

### Scope safety
- **D-06:** Do not reopen symbolic/CAS work, automatic route mutation, or
  multi-candidate analytical comparison. This phase is about runtime visibility
  and proof of the bounded analytical surface.
- **D-07:** If runtime surfaces need a new structured bundle field, keep it
  inside the existing `validation_review_bundle` contract so current consumers
  can evolve by extension rather than replacement.

### the agent's Discretion
- exact bundle field name for the structured analytical runtime surface
- whether the dashboard also renders the richer analytical cross-check section
  in addition to the required status/runtime/read-path surfaces
- whether the dedicated proof lane should reuse helpers from
  `run_analytical_judgment_surface_acceptance.py` directly or copy only the
  minimal isolated fixture setup it needs

</decisions>

<canonical_refs>
## Canonical References

**Downstream agents MUST read these before planning or implementing.**

### Milestone scope and phase handoff
- `.planning/ROADMAP.md` — Phase `168.1` goal and dependency on Phase `168`
- `.planning/REQUIREMENTS.md` — `REQ-ANX-03` and `REQ-VERIFY-01`
- `.planning/phases/168-analytical-check-rows-and-review-contract-expansion/168-01-SUMMARY.md`
  — confirms the richer analytical-check row contract now exists

### Core runtime/read-path surfaces
- `research/knowledge-hub/knowledge_hub/validation_review_service.py` —
  current validation-review bundle payload and markdown rendering
- `research/knowledge-hub/knowledge_hub/topic_shell_support.py` — dashboard and
  status-facing topic-shell renders that already reference the validation review
  bundle
- `research/knowledge-hub/knowledge_hub/runtime_bundle_support.py` — runtime
  protocol markdown and bundle composition
- `research/knowledge-hub/runtime/schemas/progressive-disclosure-runtime-bundle.schema.json`
  — current public runtime-bundle schema for `validation_review_bundle`

### Existing analytical proof lane and tests
- `research/knowledge-hub/runtime/scripts/run_analytical_judgment_surface_acceptance.py`
  — current analytical acceptance lane that must stay compatible
- `research/knowledge-hub/tests/test_aitp_service.py` — current analytical
  review bundle coverage
- `research/knowledge-hub/tests/test_runtime_scripts.py` — runtime-script
  invocation coverage
- `research/knowledge-hub/tests/test_schema_contracts.py` — public schema lock

</canonical_refs>

<code_context>
## Existing Code Insights

### Reusable Assets
- `validation_review_service.py` already decides when `analytical_review`
  becomes the primary review kind and already owns the machine/human bundle
  surfaces.
- `topic_shell_support.py` and `runtime_bundle_support.py` already render the
  validation-review bundle on dashboard/runtime protocol notes, but currently
  only as thin status/summary text.
- `run_analytical_judgment_surface_acceptance.py` already seeds an isolated
  analytical-review candidate and proves CLI `analytical-review -> verify ->
  status` compatibility.

### Established Patterns
- Runtime/read-path parity work in this repo usually adds one structured field
  to the machine payload, extends markdown renderers, then proves the path with
  one dedicated acceptance script plus one runtime-script invocation test.
- Public runtime-bundle surfaces are schema-locked, so any new structured field
  under `validation_review_bundle` must be mirrored into
  `progressive-disclosure-runtime-bundle.schema.json`.

### Integration Points
- `research/knowledge-hub/knowledge_hub/validation_review_service.py`
- `research/knowledge-hub/knowledge_hub/topic_shell_support.py`
- `research/knowledge-hub/knowledge_hub/runtime_bundle_support.py`
- `research/knowledge-hub/runtime/schemas/progressive-disclosure-runtime-bundle.schema.json`
- `research/knowledge-hub/runtime/scripts/run_analytical_judgment_surface_acceptance.py`

</code_context>

<specifics>
## Specific Ideas

- Preferred runtime shape: a structured analytical cross-check surface nested
  under `validation_review_bundle`, derived from the active analytical review.
- Preferred human read-path shape: one dedicated `## Analytical cross-check
  surface` section on the bundle note, echoed into runtime protocol and
  dashboard sections where the validation review bundle is already shown.
- Preferred proof shape: a dedicated
  `run_analytical_cross_check_surface_acceptance.py` script that asserts the
  richer analytical surface survives through bundle JSON, bundle markdown, and
  runtime protocol/status read paths.

</specifics>

<deferred>
## Deferred Ideas

- route mutation or contradiction adjudication driven by analytical outcomes
- multi-candidate analytical comparison bundles
- symbolic or CAS-backed analytical execution

</deferred>

---

*Phase: 168.1-analytical-runtime-surface-and-proof-lane*
*Context gathered: 2026-04-13*
