Refresh documentation and policies and simplify releases

docs/internal/output-schemas.md

@@ -1,43 +1,31 @@
-# Audita Output Schemas
+# Output Encoding Internals
 
-## Scope
+## Scope and Ownership
 
-This document describes the implemented transcript output schema registry.
+`internal/core/outputschema` owns encoder registration and resolution. External
+JSON envelopes and segment fields are defined by the
+[output-file contract](../integrations/output-files.md#corrected-transcript);
+selectable values and defaults belong to
+[configuration](../config.md#pipeline-and-output).
 
-## Registry Ownership
+## Resolution and Encoding
 
-Output schema registry is owned by `internal/core/outputschema`.
+Configuration validation checks registry support. CLI orchestration resolves the
+selected encoder, passes the final transcript to it, and routes the encoded bytes
+to the destination defined by the [CLI contract](../cli.md#process-output-and-exit-behavior).
+An unsupported key fails validation or resolution rather than selecting an
+implicit fallback.
 
-Supported schema keys:
-- `bare-segments`
-- `audita-v1`
+The registry delegates bare segment serialization to the transcript schema
+package and uses an envelope encoder for the versioned form. Report construction
+receives the selected key separately; see [report assembly](diagnostics-reporting.md).
 
-## Schemas
+## Changing an Encoder
 
-`bare-segments`:
-- top-level JSON array of transcript segments.
-
-`audita-v1`:
-- top-level JSON object with:
-  - `schema: "audita-v1"`
-  - `version: "v1"`
-  - `segments: [...]`
-
-Segment fields include `id`, `speaker`, `start`, `end`, `text`, and optional `categories`.
-
-## Validation and Resolution
-
-Config validation and runtime resolution both reject unsupported schema keys.
-
-Unknown schema keys fail with `unsupported output schema` before output emission.
-
-## Output Emission
-
-The selected schema is used by `audita process` when writing:
-- output file (`--output`) or
-- stdout (when no `--output`).
-
-Report metadata records selected `output_schema`.
+Update registration, configuration validation, and serialization together. Inspect
+round-trip and shape tests, then update the external output-file contract if the
+serialized form changes. Keep internal helper changes separate from decisions
+about externally visible compatibility.
 
 ## Key Tests