file-save-protocol

To ensure persistent analysis outputs, use a deterministic protocol that writes a mandatory JSON artifact and a Markdown summary to a designated output path. This enforces fixed naming conventions and validates successful writes to prevent data loss and hallucination.

Silent save failures happen when write operations lack enforced error handling. A deterministic saving protocol validates successful file writes and reports failures explicitly, preventing data loss by ensuring the JSON artifact and Markdown summary are confirmed at the specified output path.

The best way to audit JSON analysis artifacts is to generate a corresponding human-readable Markdown summary alongside the structured data. This dual-artifact approach enforces traceability and verifies that files are saved correctly using fixed path conventions.

Deterministic file saving prevents hallucination by enforcing a strict protocol that stores analysis results as persistent JSON and Markdown artifacts at a coordinator-provided output path. Validating successful writes eliminates ambiguous states and confirms the exact saved output.

You need a fixed naming convention when reproducible artifacts are required for auditing. Enforcing fixed paths and filenames guarantees that every analysis result is stored deterministically at the coordinator-provided output path, preventing misplacement and data loss.