misp-mcp: Instructions file for Codex

AGENTS.md - Working In This Repo

This repo is Brigade-wired. These are the operating rules for any agent working here.

Every Session

For substantial work, first gather context:

1. Read this file - operating rules and the memory handoff contract.
2. Read the repo's README and CONTRIBUTING (if present) for build, test, and style expectations.
3. Skim your harness's handoff inbox (.codex/memory-handoffs/) for recent notes from other sessions.
4. Read SAFETY_RULES.md once. Hard boundaries.

For tiny read-only commands, do the command directly and avoid loading unrelated context. Do not ask permission for normal context gathering.

Definition of Done

Before you report work as complete:

1. Run the project's checks (tests, linters, type checks, build). If you do not know them, look in README, CONTRIBUTING, pyproject.toml / package.json, or the CI config before guessing.
2. Report the actual result. Never claim success you did not observe; paste the command you ran and its output.
3. If a check could not run, say so and name the blocker instead of guessing.
4. If the session produced durable knowledge, confirm a Memory Handoff was written (see below).

Memory Owner

The configured memory owner is codex. Side harnesses may keep local session context, but durable knowledge must be written as a Memory Handoff in your harness's own inbox (.codex/memory-handoffs/). The memory owner ingests those handoffs into canonical durable memory; reviewed repo-local notes land under .learnings/.

If you are not the memory owner, do not edit SAFETY_RULES.md, rules/, or .learnings/ as canonical memory unless the user explicitly asks for that file edit. Do not create a second canonical memory system.

Memory Handoff (Mandatory)

If a session discovers durable knowledge - architecture decisions, workflow changes, non-obvious fixes, setup gotchas, security findings, reusable commands, durable research, or user preferences - create a handoff at the end of the task.