straymark-audit-prompt

To generate a unified audit prompt, run the preparation command for your Charter ID with the prepare flag. This resolves the Charter status and embeds the Charter content, AiLOGs, git diff, and discipline rules into a single self-contained audit prompt file on disk.

The best way to prevent copy/paste drift across multiple auditors is to generate a single canonical audit prompt file on disk. Auditor-side CLIs can then read this unified instruction set directly from the filesystem, ensuring consistent context across all model sessions.

You can resolve preparation-only placeholder content by executing the charter audit command with the prepare flag. This resolves the Charter status and generates the complete audit prompt without requiring operator intervention or manual copy/paste.

You should not run audit prompt preparation on a closed Charter. The workflow applies to Charters in in-progress or declared status; if the Charter is closed, the system will surface a warning indicating that the audit checkpoint process is not applicable.

The generated audit prompt file is written to a canonical filesystem directory specific to the Charter ID. Targeting this standard path allows multiple auditor-side CLIs to automatically locate and consume the same embedded Charter, AiLOG, and git diff instructions.

Yes, the generated audit prompt embeds discipline rules including SOLO LECTURA and evidence-citation/severity calibration. This ensures that all auditors consuming the prompt apply the same governance and compliance standards during the Charter audit checkpoint.