Organize generic and Seriatim modules by domain
This commit is contained in:
@@ -1,8 +1,9 @@
|
||||
# Module And Validator Internals
|
||||
|
||||
Production stage implementations live under `internal/modules`; production
|
||||
validators live under `internal/validators`. The selectable keys, configuration
|
||||
options, reference slots, and default validator chain are canonical in the
|
||||
Production module implementations and generic validators live under
|
||||
`internal/modules`; the current D&D validators live under `internal/validators`.
|
||||
The selectable keys, configuration options, reference slots, and default
|
||||
validator chain are canonical in the
|
||||
[module](../config.md#implemented-production-modules) and
|
||||
[validator](../config.md#implemented-production-validators) catalogs in
|
||||
Configuration.
|
||||
@@ -36,7 +37,7 @@ evidence. The resolver and materializer behavior is described in
|
||||
|
||||
## Input Adapter
|
||||
|
||||
### `internal/modules/input/seriatim`
|
||||
### `internal/modules/seriatim/input/transcript`
|
||||
|
||||
The adapter decodes the supported transcript JSON, selects the source identity,
|
||||
computes the raw-input digest, validates segments, and maps each segment into a
|
||||
@@ -50,7 +51,7 @@ rules are defined in the
|
||||
|
||||
## Chunkers
|
||||
|
||||
### `internal/modules/chunk/generic`
|
||||
### `internal/modules/generic/chunk/units`
|
||||
|
||||
The generic chunker validates the source document, walks units in configured
|
||||
windows, clones each selected unit, and emits deterministic ordered chunk IDs.
|
||||
@@ -99,14 +100,14 @@ The durable payload and manifest metadata shapes are defined in the
|
||||
|
||||
## Merger And Normalizer
|
||||
|
||||
### `internal/modules/merge/appendorder`
|
||||
### `internal/modules/generic/merge/appendorder`
|
||||
|
||||
The merger preserves extract-result order. It passes through one JSON result,
|
||||
concatenates a common top-level array field across multiple JSON objects, and
|
||||
otherwise emits an array of the decoded values. It rejects invalid JSON and
|
||||
non-JSON media types, and it preserves compatible schema provenance.
|
||||
|
||||
### `internal/modules/normalize/noop`
|
||||
### `internal/modules/generic/normalize/noop`
|
||||
|
||||
The normalizer defensively clones the accepted merge result, including payload
|
||||
bytes, metadata, warnings, and schema provenance, without changing its logical
|
||||
@@ -114,7 +115,7 @@ content.
|
||||
|
||||
## Output Encoder
|
||||
|
||||
### `internal/modules/output/json`
|
||||
### `internal/modules/generic/output/json`
|
||||
|
||||
The JSON encoder sorts normalized results by lane, derives collision-checked
|
||||
safe logical names, pretty-prints JSON payloads, and assembles the logical index,
|
||||
@@ -127,6 +128,9 @@ paths and schemas.
|
||||
|
||||
## Generic Validators
|
||||
|
||||
The generic validator implementations live under
|
||||
`internal/modules/generic/validate`.
|
||||
|
||||
The unconditional accept and reject validators provide deterministic production
|
||||
registrations used primarily for controlled composition and tests.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user