Revise the architecture plan to reflect an input -> chunk -> process -> merge -> normalize -> output workflow

This commit is contained in:
2026-07-03 08:54:23 -05:00
parent 32be4ee85e
commit 88042174b3
10 changed files with 426 additions and 160 deletions

View File

@@ -6,10 +6,10 @@ This is a staged implementation plan for
[`2-framework-composition.md`](2-framework-composition.md). It is intended for
an LLM coding agent to follow stage by stage.
This plan implements only checkpoint 2. Do not implement real input adapters,
real extractors, source chunking, LLM provider clients, prompt assets, response
schema registries, diagnostics run directories, production config loading, or
D&D artifact schemas in this pass.
This plan implements only checkpoint 2. Do not implement real input modules,
real process modules, source chunking, LLM provider clients, prompt assets,
response schema registries, diagnostics run directories, production config
loading, or D&D artifact schemas in this pass.
## Policy Context
@@ -21,8 +21,8 @@ Follow:
Required boundaries:
- framework packages must stay source-agnostic and domain-agnostic;
- input adapter registry code must not import concrete adapter packages;
- extractor registry and runner code must not import concrete extractor
- input adapter registry code must not import concrete input module packages;
- extractor registry and runner code must not import concrete process module
packages;
- runner code should operate on `SourceDocument`, not transcript-specific
structures;
@@ -130,7 +130,7 @@ Cover:
- sorted `RegisteredKeys`;
- nil registry behavior.
Use fake adapters only. Do not add concrete adapter packages.
Use fake adapters only. Do not add concrete input module packages.
### Validation
@@ -196,7 +196,7 @@ Cover the same cases as the input adapter registry:
- sorted `RegisteredKeys`;
- nil registry behavior.
Use fake extractors only. Do not add concrete extractor packages.
Use fake extractors only. Do not add concrete process module packages.
### Validation
@@ -478,7 +478,8 @@ go test ./...
### Goal
Prove the extractor registry and runner compose without adding real extractors.
Prove the extractor registry and runner compose without adding real process
modules.
### Files To Add
@@ -501,7 +502,7 @@ Assertions:
- extractor execution follows configured key order;
- approved artifacts are in deterministic order;
- rejected artifacts are in deterministic order;
- no concrete adapter or extractor packages are imported.
- no concrete input module or process module packages are imported.
### Validation
@@ -527,7 +528,7 @@ Check:
- no package names mention transcripts, Seriatim, D&D, spells, NPCs, items, or
combat;
- no concrete adapter or extractor package exists;
- no concrete input module or process module package exists;
- no LLM provider code exists;
- no prompt, response schema, diagnostics, config, or source chunking package
was added;