2.0 KiB
G8 Local Document Pipeline First Slice Report
Date: 2026-04-18 Scope:
G8classification and fail-closed safety slice
Summary
The first G8 implementation slice is complete.
This round added the local_doc_pipeline archetype and a repo-local representative fixture for the 95598供电服务月报 boundary family.
The result is intentionally fail-closed: G8 can now be identified and prevented from falling back into G1/G1-E/G6, but runnable local storage, SQL analysis, and document-generation orchestration is not implemented yet.
Assets Updated
src/generated_scene/ir.rssrc/generated_scene/analyzer.rssrc/generated_scene/generator.rstests/fixtures/generated_scene/g8_local_doc_pipeline/index.htmltests/scene_generator_test.rs
Behavioral Result
The representative fixture validates:
workflowArchetype = local_doc_pipeline- localhost dependency evidence includes
localhost:13313 - local pipeline actions include
definedSqlQuery - local pipeline actions include
docExport - local pipeline actions include
selectData - generation fails closed with
local_doc_pipeline
Boundary Correction
The first test run showed that G8 could be captured by G6 because the fixture also contains host bridge actions.
The classifier now prioritizes local document pipeline evidence over generic host bridge evidence. This preserves the intended family boundary:
G6: host bridge driven query progressionG8: local persistence, SQL analysis, and document production after data capture
Validation
Executed:
cargo test --test scene_generator_test -- --nocapture
cargo test --test scene_generator_p1_family_test -- --nocapture
cargo test --test scene_generator_family_policy_test -- --nocapture
cargo test --test scene_generator_canonical_test -- --nocapture
All target regressions passed.
Result
G8 is now safely separated from G1/G1-E/G6 at classification time.
The family remains fail-closed until a formal local document pipeline runtime contract is implemented.