55 lines
3.3 KiB
Markdown
55 lines
3.3 KiB
Markdown
# Integration: Audita
|
|
|
|
Narratio invokes Audita v2's `process INPUT --glossary PATH --output PATH`
|
|
subprocess for `polish`. The configured timeout and parent cancellation bound
|
|
execution. Narratio passes explicit `--config`, `--overlay`,
|
|
`--proposal-profile`, `--validation-profile`, `--transcript-description`,
|
|
`--output-schema`, and `--modules` only when selected. An omitted module list
|
|
leaves Audita's default sequence in place; `modules: []` passes an explicit
|
|
empty argument and runs no correction modules. Order and repetitions are kept.
|
|
Narratio passes no debug, work-directory, or reporting flags, leaving those
|
|
choices to Audita's own configuration.
|
|
|
|
Audita owns its ConfigKit file, backend and profile definitions, native config
|
|
discovery, and their validation. Narratio does not create an Audita
|
|
configuration or infer downstream overlay/profile names from its own selected
|
|
pipeline overlay. An empty Narratio Audita selector adds no CLI override.
|
|
The [configuration reference](../config.md#audita-selection-and-credentials)
|
|
owns Narratio's fields and defaults. Audita's
|
|
[v2 migration guide](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.0/docs/migrations/v2.md)
|
|
owns its downstream file format.
|
|
|
|
Each name in `pipeline.audita.credentials` is a ConfigKit secret reference
|
|
resolved when Narratio loads the pipeline. Narratio forwards only the selected
|
|
names and their captured, nonempty values under those exact names, in the
|
|
minimal child environment; it never maps them to a fixed alias or rereads the
|
|
parent environment. Every name is registered for captured stdout/stderr and
|
|
failure-diagnostic redaction. Audita resolves credentials for all configured
|
|
backends, including unselected ones, so operators must list every backend
|
|
credential that its selected configuration needs. The downstream files and
|
|
provider output remain Audita's responsibility, outside Narratio's
|
|
captured-stream redaction boundary.
|
|
|
|
The corrected transcript is the only canonical polish output. A successful
|
|
invocation must produce a valid JSON transcript with a top-level `segments`
|
|
array within Narratio's 64 MiB bound. Exit zero is accepted even if Audita's
|
|
ordinary reports describe recoverable model errors or no corrections. Narratio
|
|
does not parse report status, counts, or Markdown. It discovers only
|
|
`errors.yml`, `recoveries.yml`, and `report.md` next to the requested output,
|
|
each subject to a 16 MiB read bound. Missing reports are allowed, for example
|
|
when Audita reporting is disabled externally. Available reports are diagnostic
|
|
references, not canonical artifact outputs. See Audita's
|
|
[ordinary output contract](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.0/docs/integrations/output-files.md)
|
|
for their schemas, and [operations](../operations.md) for placement and
|
|
publication.
|
|
|
|
On nonzero exit, Narratio preserves the original subprocess error and
|
|
available run-local evidence; it never promotes a transcript merely because
|
|
the file exists. The adapter returns safe paths, exit details, and selection
|
|
metadata on failure. Narratio's `audita.generated.v2` YAML records the
|
|
invocation, including arguments, paths, and credential names but never values;
|
|
it is a diagnostic record, not a generated Audita config file.
|
|
|
|
Maintained Narratio examples: [full annotated pipeline](../../examples/pipeline.full.annotated.yml)
|
|
and [production-shaped pipeline](../../examples/pipeline.production.yml).
|