# Local-Doc Runtime Roadmap Plan

> Date: 2026-04-19
> Parent Decision: `2026-04-19-residual-runtime-roadmap-prioritization-plan.md`
> Parent Residual Bucket: `local_doc_pipeline`
> Status: Draft

## Plan Intent

Plan the bounded closure path for the five `local_doc_pipeline` residuals selected by the residual runtime roadmap prioritization decision.

## Fixed Input Bucket

Only these scenes are in scope:

1. `sweep-033-scene`
2. `sweep-034-scene`
3. `sweep-042-scene`
4. `sweep-051-scene`
5. `sweep-074-scene`

## Initial Phases

### Phase 0: Freeze Local-Doc Residual Baseline

Capture current generation reports and missing pieces for the five scenes.

### Phase 1: Local-Doc Evidence Inventory

Classify document source, attachment dependency, local service dependency, and output artifact expectation.

### Phase 2: Minimal Local-Doc Contract Design

Define the smallest contract that can distinguish runnable local-doc pipelines from policy-held local-doc pipelines.

### Phase 3: Bounded Implementation Slice

Implement only the contract recovery or fail-closed detail required by the five-scene bucket.

### Phase 4: Follow-Up Sweep And Reconciliation

Rerun only the five target scenes and publish candidates. Do not update the official board inside this phase.

## Forbidden Scope

1. host-bridge runtime roadmap;
2. bootstrap target normalization;
3. G4/G5;
4. full attachment runtime implementation unless explicitly required by the minimal contract;
5. official board update.

## Stop Statement

Stop after the local-doc five-scene follow-up and reconciliation candidates are published. A later official board reconciliation plan must consume the result.