# Local-Doc Runtime Roadmap Design

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

## Intent

Define the next bounded roadmap for the five remaining `local_doc_pipeline` residuals.

This roadmap exists because official board reconciliation identified five explained structured fail-closed scenes that require local document runtime and attachment/document handling semantics.

## Fixed Input Bucket

The roadmap is limited to the five official board residuals with:

1. `currentFrameworkStatus = framework-structured-fail-closed`
2. `currentFrameworkArchetype = local_doc_pipeline`
3. `currentFrameworkNextAction = future-local-doc-runtime-roadmap-input`

## Target Scenes

1. `sweep-033-scene` / `供电可靠率指标统计表`
2. `sweep-034-scene` / `供电可靠性数据质量自查报告月报`
3. `sweep-042-scene` / `国网金昌供电公司营商环境周例会报告`
4. `sweep-051-scene` / `嘉峪关可靠性分析报告`
5. `sweep-074-scene` / `同兴智能安全督查日报`

## Roadmap Goal

Move the five local-doc residuals from generic structured fail-closed to one of:

1. runnable local-doc contract;
2. named local-doc runtime missing capability;
3. explicit non-goal that remains policy-held.

## Boundary

This design must not:

1. modify host-bridge runtime;
2. open bootstrap target normalization;
3. add a new family;
4. update the official board without a dedicated reconciliation step;
5. treat local document runtime as generic paginated enrichment.

## Required Work Areas

1. local document source evidence extraction;
2. document artifact contract;
3. attachment/input dependency modeling;
4. local pipeline execution seam;
5. fail-closed reasons specific to local-doc runtime.

## Acceptance Criteria

1. The five target scenes remain the only input bucket.
2. Each scene has a local-doc runtime decision.
3. Any implementation step remains bounded to `local_doc_pipeline`.
4. Follow-up reconciliation is explicit and separate.