Reintroduce normalize stage scaffold

architecture.md

@@ -18,6 +18,7 @@ Implemented:
 - real Seriatim subprocess adapter
 - real Audita subprocess adapter
 - real Scriptorium subprocess adapter
+- placeholder `normalize` stage producing `transcripts/normalized.json`
 - real `trim` stage producing `transcripts/trimmed.json`
 - real `analyze` stage for initial `session_recap` generation
 - optional Scriptorium render diagnostics (`render_debug`) before production run
@@ -38,10 +39,11 @@ Canonical stage order:
 2. `transcribe`
 3. `merge`
 4. `polish`
-5. `trim`
-6. `analyze`
-7. `archive`
-8. `notify`
+5. `normalize`
+6. `trim`
+7. `analyze`
+8. `archive`
+9. `notify`
 
 Boundary rules:
 
@@ -155,29 +157,30 @@ trim:
 
 ## 6. Transcript Tiers
 
-Narratio currently produces and uses three transcript tiers:
+Narratio currently produces and uses four transcript tiers:
 
 - `transcripts/merged.json`: canonical deterministic merged transcript from Seriatim merge
 - `transcripts/processed.json`: full polished transcript from Audita polish (includes pre/post-game content)
+- `transcripts/normalized.json`: placeholder normalized transcript (Seriatim-compatible schema pass-through for now)
 - `transcripts/trimmed.json`: gameplay-only polished transcript from trim stage
 
-Trim reads `transcripts/processed.json`, validates bounds IDs against that same transcript ID space, and writes `transcripts/trimmed.json`.
+Trim reads `transcripts/normalized.json`, validates bounds IDs against that same transcript ID space, and writes `transcripts/trimmed.json`.
 
 ## 7. Trim Stage (Current Implementation)
 
 Trim stage behavior:
 
-- stage order position: after `polish` and before `analyze`
-- discovers processed transcript from manifest polish outputs (`transcript_processed`) when present, else `work/<session_id>/transcripts/processed.json`
-- validates processed transcript JSON shape (`segments` array required)
-- when `trim.enabled: false` (or trim config omitted), deterministically copies processed transcript to `transcripts/trimmed.json` and records `trim_action=copy_disabled`
+- stage order position: after `normalize` and before `analyze`
+- discovers normalized transcript from manifest normalize outputs (`transcript_normalized`) when present, else `work/<session_id>/transcripts/normalized.json`
+- validates normalized transcript JSON shape (`segments` array required)
+- when `trim.enabled: false` (or trim config omitted), deterministically copies normalized transcript to `transcripts/trimmed.json` and records `trim_action=copy_disabled`
 - when `trim.enabled: true`:
   - runs Scriptorium bounds prompt using configured `trim.bounds.prompt_id`
   - writes bounds output to configured path (typically `artifacts/session_bounds.json`)
-  - parses and validates bounds output against the same processed transcript being trimmed
+  - parses and validates bounds output against the same normalized transcript being trimmed
   - converts bounds range to Seriatim keep selector (for example `10-868`)
   - runs Seriatim `trim` to produce `transcripts/trimmed.json`
-  - supports no-trim bounds actions (`none`/`copy`) by copying processed transcript unchanged
+  - supports no-trim bounds actions (`none`/`copy`) by copying normalized transcript unchanged
 - validates trimmed transcript JSON shape (`segments` array required)
 
 Expected trim outputs and diagnostics:
@@ -252,8 +255,8 @@ If prepared inputs or prompt/runtime configuration change (for example glossary
 
 Examples:
 
-- glossary or autocorrect changes usually require rerunning at least `merge`, `polish`, `trim`, and `analyze`
-- trim prompt/profile changes require rerunning at least `trim` and `analyze`
+- glossary or autocorrect changes usually require rerunning at least `merge`, `polish`, `normalize`, `trim`, and `analyze`
+- trim prompt/profile changes require rerunning at least `normalize`, `trim`, and `analyze`
 - session recap prompt/profile/input-source changes require rerunning `analyze`
 
 ## 12. Roadmap