requirements-verbatimlisted

# requirements-verbatim Record requirements, decisions, approvals, and constraints exactly as the user stated them, into a durable on-disk log. The log is the ground truth for what was asked. It outranks memory, paraphrase, and model inference (see the authority order below). Its single job: nothing the user approved can be lost, altered, or quietly reinterpreted between now and when the work is verified. ## When this fires - The user states a requirement, gives a GO, sets a constraint, or makes a decision. - The user approves or rejects a proposal (log what was approved, verbatim). - You (or a subagent) are handed a requirement and are about to act on it: log it first. - Before any compaction (see the credo `compact-plus` skill): the verbatim log must already hold everything approved, because a compact must not be able to lose or alter it. This fires inside subagents too. A subagent that receives a requirement from the main agent logs the verbatim source itself rather than trusting a paraphrase. ## Where it lives Append-only log files under `.credo/process/requirements/` in the current project (the credo per-project namespace created by `scripts/credo-init.sh`). One dated file, for example `.credo/process/requirements/2026-07-04.md`, appended to across the day. - Append only. Never edit or delete an existing entry. A correction is a NEW entry that references the earlier one; the original stays. - Write atomically (temp file plus `mv -f`) per the credo persistenc