Publish outputs to checked destinations and preserve failure evidence

This commit is contained in:
2026-11-16 03:52:35 +00:00
parent cea7e44232
commit b63c8af467
11 changed files with 656 additions and 336 deletions

View File

@@ -34,15 +34,20 @@ untouched until successful publication. Pipes and devices are opened only for
delivery, and a pipe can wait for its reader. If a transcript destination changes
between a regular file and a pipe or device during processing, Audita can report a
delivery failure while preserving the new destination. Parent directories for
required outputs must already exist.
required outputs must already exist. Publication uses the destinations resolved
during preparation. Give concurrent invocations separate destinations, and
choose separate report directories when retaining reports from multiple runs.
Enabled reports are initialized as `in_progress` before processing. The
transcript is published before final reports; the files do not form a single
transaction. A late report failure may therefore leave a published transcript.
Fatal errors and cancellation clean unpublished temporary resources and attempt
failed-status final reports. An uncatchable termination can leave `in_progress`
evidence. Read exit status and reports together rather than treating a file's
existence as proof of success.
After a required write failure or cancellation, Audita attempts to clean
unpublished temporary resources and publish failed-status reports. A cleanup
failure is reported with the earlier error. Cancellation observed after a
stream write still fails the invocation, even when some or all bytes reached
the reader. If failed reports cannot be rendered, available report evidence
remains. An uncatchable termination can leave `in_progress` evidence. Use the
exit status and report status to determine the outcome.
## Debug evidence
@@ -50,7 +55,9 @@ The shared `--debug` flag enables retained artifacts in a run directory beneath
`diagnostics.work_dir`; selecting a work directory alone does not enable capture.
Optional debug preparation or writes can produce warnings without
changing correction decisions or the required output result. Debug material can
include transcript content, prompts, responses, and correction decisions. Protect this material according to the sensitivity of the inputs and responses. Repair interactions
include transcript content, prompts, responses, and correction decisions.
Protect this material according to the sensitivity of the inputs and responses
and manage its retention. Repair interactions
and revalidation artifacts include proposal and attempt coordinates; the
correction ledger connects them to the original edit.