# G8 Local Document Pipeline Plan

> Date: 2026-04-18
> Status: Initial implementation slice

## Plan Intent

Start `G8` after the safe `G7` classification slice.

This plan only establishes boundary classification and fail-closed behavior. It does not implement runnable local storage, SQL, or document generation orchestration.

## Phase 0: Boundary Freeze

Tasks:

1. use `95598供电服务月报` as the P0 boundary sample
2. define a repo-local representative fixture
3. keep `G8` separate from `G1`, `G1-E`, `G6`, `G7`, and `G3`

Acceptance criteria:

1. `G8` is no longer a `G1` candidate
2. `G8` is not collapsed into generic host bridge workflow

## Phase 1: Analyzer Classification

Tasks:

1. add `local_doc_pipeline` as a workflow archetype
2. detect `definedSqlQuery`
3. detect `docExport`
4. detect `selectData` / local config service persistence
5. prioritize `G8` over `G6` when both signals exist

Acceptance criteria:

1. `g8_local_doc_pipeline` fixture classifies as `local_doc_pipeline`
2. local pipeline actions are visible in deterministic facts

## Phase 2: Fail-Closed Gate

Tasks:

1. add `g8_local_doc_pipeline_detected`
2. add `g8_fail_closed`
3. block generation before runnable output

Acceptance criteria:

1. generation returns a controlled error
2. error message includes `local_doc_pipeline`
3. no pseudo-runnable skill is produced

## Phase 3: Regression

Tasks:

1. run scene generator regression
2. run family regression
3. run family policy regression
4. run canonical regression

Acceptance criteria:

1. all target regressions pass
2. no existing family baseline regresses

## Next Step

After this safe G8 slice, the boundary-reassignment sequence has a code-backed fail-closed guard for `G1-E`, `G6`, `G7`, and `G8`.