read-verify

To prevent hallucinated changes, enforce a read-before-edit workflow that loads the current file state before applying modifications. This ensures current state awareness by requiring a Read(filepath) call to lock edits to the latest content before executing Edit(filepath, ...).

Unintended modifications in collaborative environments occur due to stale context and context drift. Enforcing a read-before-edit workflow verifies current content and locks edits to the latest state, which reduces merge conflicts and prevents accidental edits across development sessions.

You can enforce reading a file before editing by applying session recency checks and requiring Read(filepath) before Edit(filepath, ...). This workflow guarantees current state awareness by locking modifications to the latest loaded file content.

Yes, the read-before-edit workflow applies during both code and document edits across development sessions. It ensures current state awareness by prompting a Read to verify current content before applying any modifications to the file.

Relying on manual file reading without enforcement risks stale context and hallucinated changes if skipped. Automated enforcement eliminates this limitation by applying session recency checks and requiring Read(filepath) before allowing Edit(filepath, ...) to proceed.