itzamna-project-operations

To safely automate repository configuration updates, use a human-gated workflow that performs read-only verification and generates draft diffs for approval. This prevents agents from overwriting CLI-generated artifacts by requiring explicit human consent before any writes.

A human-gated workflow for agent memory and context files is a process where agents draft proposed updates and diffs for maintainer review. It ensures safe handling of short-term memory files by logging approvals and never overwriting authoritative files without explicit consent.

You verify .itzamna and .context directory structure by running a read-only inspection that checks for expected templates and configuration presence. This verification occurs before any modification, ensuring the repository meets structural requirements prior to proposing updates.

Yes, you can append Itzamna references to CLI-generated files through a non-destructive proposal mechanism. The system detects files lacking references and drafts append-only changes, requiring human approval before applying any modifications to avoid breaking existing artifacts.

The best way to draft and review diffs for project memory and context templates is to generate proposed content with clear rationale for maintainer review. This human-gated approach produces auditable changes and a concise final status report summarizing findings.

Agents overwrite repository configuration when lacking a human gate to enforce read-only verification before writes. Implementing a gated proposal mechanism prevents unsanctioned edits by requiring explicit human consent and logging all approvals prior to applying modifications.