Document the new configuration and processing workflow

This commit is contained in:
2026-11-10 17:52:14 +00:00
parent 926fa26a31
commit ba1d5d2367
61 changed files with 832 additions and 765 deletions

View File

@@ -17,7 +17,7 @@ implementation is pending. The
The current [CLI](../cli.md) accepts one glossary input for a processing run.
The [pipeline configuration](../config.md) supports repeated glossary stages,
but does not select different glossary inputs for each occurrence. Glossary
files currently have a separate [YAML input contract](../integrations/transcript-glossary-files.md#glossary-yaml-contract).
files currently have a separate [YAML input contract](../integrations/transcript-glossary-files.md#glossary-collections).
Make glossaries and glossary collections reusable, composable configuration
assets loaded and composed by ConfigKit. Allow ordered stages to select different resolved

View File

@@ -573,6 +573,11 @@ Verify existing partial-success and unavailable-candidate evidence survives.
## Stage 14: Finish the cutover documentation, examples, and attribution
**Completed.** Canonical guidance, the decision record, migration guide,
maintained projects, release procedure, and dependency attribution reflect the
cutover. Controlled-provider project checks and documented offline inspections
passed; historical example links point to the unchanged v3.0.0 tag.
Update canonical owners as behavior lands; use this stage to reconcile them.
Follow the [documentation policy](../policy/documentation.md) and glossary
[durable record](glossary-stages.md#durable-decision-record).