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

**Researched:** 2026-04-13
**Domain:** runtime/read-path analytical cross-check parity and bounded proof
closure
**Confidence:** HIGH

<research_summary>
## Summary

Phase `168` already made `analytical_review` row-first. The remaining gap is
runtime visibility:

- `validation_review_bundle` still only exposes thin summary/artifact rows
- dashboard/runtime protocol notes only echo the bundle at summary level
- there is no dedicated analytical cross-check proof lane yet

The repo already has the right architecture to close this narrowly:

- `validation_review_service.py` owns the primary machine/human bundle surface
- `topic_shell_support.py` and `runtime_bundle_support.py` already render that
  bundle into the main read paths
- `run_analytical_judgment_surface_acceptance.py` already proves the baseline
  CLI path and can act as a compatibility guard

**Primary recommendation:** add one structured analytical runtime surface under
`validation_review_bundle`, render it on the bundle note plus current
runtime-facing markdown consumers, extend the public runtime-bundle schema, and
close with one dedicated analytical cross-check acceptance script.

</research_summary>

<architecture_patterns>
## Architecture Patterns

### Pattern 1: Extend the existing bundle, do not create a parallel runtime family
The validation review bundle is already the current `L4` read surface. Put the
analytical cross-check payload there.

### Pattern 2: Machine payload first, markdown renderers second
Define a structured JSON surface first, then make dashboard/runtime/bundle notes
render it. This keeps `status --json` and runtime markdown aligned by design.

### Pattern 3: Dedicated proof lane plus compatibility baseline
Use one dedicated analytical cross-check acceptance script for milestone
closure, but keep `run_analytical_judgment_surface_acceptance.py` green to
prove backward compatibility.

</architecture_patterns>

<common_pitfalls>
## Common Pitfalls

- hiding the richer analytical surface only inside markdown prose instead of
  the machine-readable bundle
- widening the scope into a new artifact family instead of extending
  `validation_review_bundle`
- forgetting to update the runtime-bundle schema when adding the new structured
  surface
- treating the older analytical judgment acceptance as a sufficient dedicated
  proof lane

</common_pitfalls>
