REZANOVA-CAS-CALCULATOR: Instructions file for Codex

Calcwiz Agent Policy

Authority And Read Order

• AGENTS.md is the authoritative workflow and agent-governance file for this repository.
• CLAUDE.md and GEMINI.md are compatibility stubs only; they must defer to AGENTS.md and must not define competing policy.
• Before substantial work, every agent must read in this order:
  • AGENTS.md
  • .memory/PROTOCOL.md
  • .memory/current-state.md
  • the active .memory/sessions/<task-id>/... dossier when one exists
• If any workflow or memory file conflicts with AGENTS.md, follow AGENTS.md and update the lower-priority file afterward.

Memory Policy

• After finishing any task that changes code, architecture, tooling, UX behavior, or project workflow, append a concise dated note to .memory/journal/YYYY-MM-DD.md before sending the final response.
• If the task locks in a durable product or engineering decision, also append a dated bullet to .memory/decisions.md.
• If the task leaves an unresolved design or roadmap choice, append a dated bullet to .memory/open-questions.md.
• Durable memory under .memory/ is expected to be tracked in git; temporary task tracking belongs in .task_tmp/ and must stay ignored.
• Update .memory/current-state.md and the active .memory/sessions/<task-id>/... dossier whenever a meaningful task or verified gate completes.
• Memory completeness is a commit gate for meaningful work: before committing code, tooling, UX, architecture, or workflow changes, either stage the required durable-memory updates or record a short explicit reason in the active session/verification note explaining why no durable memory update was required.
• Do not mark a milestone complete when .memory/current-state.md, .memory/decisions.md, session dossier, or journal updates required by the change are missing.
• .memory/current-state.md is a current operating snapshot, not an append-only milestone log. The memory-protocol validator enforces this and the gate fails if any rule is broken:
  • Keep it under the 500-line protocol cap and at most 14 level-2 (##) headings.
  • No milestone-id headings (e.g. ## OOE-RS12, ## DISPLAY-SCHEDULER-POLISH1); finished-milestone records belong in the journal, .memory/decisions.md, session dossiers, or the .memory/research/milestones/ archive.
  • Refresh the Last updated: YYYY-MM-DD line on every meaningful update.
• Daily current-state catch-up is mandatory: if a journal or session dossier exists for a newer date than .memory/current-state.md, npm run test:memory-protocol fails. Before committing the first meaningful work of a new day, refresh .memory/current-state.md so it reflects the current repo posture for that day.
• When updating .memory/current-state.md, replace or trim superseded postures in place rather than appending. When a section grows stale or the file nears the cap, move the oldest superseded content into the current month's .memory/research/milestones/current-state-milestone-archive-YYYY-MM.md (create the monthly file if absent) — never let history accumulate in the snapshot.
• Keep memory updates short, factual, and human-readable. Prefer bullets.
• Do not make runtime behavior depend on .memory/.
• If .memory/ is missing, recreate the existing structure before writing notes.
• Follow .memory/PROTOCOL.md for the durable-memory schema, attribution fields, journal format, and handoff rules.