write-evidence

To write checkpoint and status content, you can use a skill that enforces strict folder whitelist validation and performs atomic file writes. It computes collision-safe paths and optionally prepends an audit header to ensure deterministic persistence in agentic workflows.

Regex-based path validation is a mechanism that blocks file writes outside approved directory patterns, ensuring compliance. It checks the target path against a predefined whitelist before creating parent directories and writing content atomically.

To prevent file overwrites when saving evidence files, you can disable the overwrite option to trigger collision-safe behavior. This appends a UTC timestamp suffix to the filename, ensuring previous artifacts remain intact during automated pipeline runs.

You can add an audit header to generated markdown content by using a feature that prepends an HTML stamp to new files. This header records play, issue, step, and timestamp metadata, providing full traceability for agent-generated artifacts.

No, directory creation and atomic writes are restricted to an approved folder whitelist. Attempting to write outside these validated paths will be blocked to prevent unsafe or inconsistent writes and maintain strict compliance boundaries.