# Agent Configuration & Master Rulebook (.agent/config.md)

This is the primary source of truth for all AI agents working on **Claudomator**. These instructions take absolute precedence over general defaults.

## 1. Project Directory Structure (.agent/)

| File | Purpose |
|------|---------|
| `config.md` | **Main Entry Point** — Rules, workflows, and core mandates. |
| `worklog.md` | **Session State** — Current focus, recently completed, and next steps. |
| `design.md` | **Architecture** — High-level design, component table, and state machine. |
| `coding_standards.md` | **Technical Standards** — Go idioms, concurrency, and testing. |
| `mission.md` | **Mission & Values** — Strategic goals and agent personality. |
| `narrative.md` | **Background** — Historical context and evolution of the project. |
| `preferences.md` | **User Prefs** — Living record of user-specific likes/dislikes. |

## 2. Core Mandates

### ULTRA-STRICT ROOT SAFETY PROTOCOL
1.  **Inquiry-Only Default:** Treat every message as research/analysis unless it is an explicit, imperative command (Directive).
2.  **Zero Unsolicited Implementation:** Never modify files, directories, or processes based on assumptions.
3.  **Interactive Strategy Checkpoint:** Research first, present a strategy, and **WAIT** for an explicit "GO" before any system-changing tool call.
4.  **No Destructive Assumptions:** Always verify state (`ps`, `ls`, `git status`) before proposing actions.
5.  **Root-Awareness:** Prioritize system integrity and user confirmation over proactiveness.

### Living Documentation Mandate
1.  **Continuous Capture:** Agents MUST proactively update the files in `.agent/` as new decisions, patterns, or user preferences are revealed.
2.  **No Stale Instructions:** If a workflow or technical standard evolves, the agent is responsible for reflecting that change in the Master Rulebook immediately.
3.  **Worklog Integrity:** The `.agent/worklog.md` must be updated at the start and end of EVERY session.

## 3. Workflows

### Research -> Strategy -> Execution
1.  **Research:** Map codebase, validate assumptions, reproduce bugs.
2.  **Strategy:** Share a summary. Wait for approval if significant.
3.  **Execution (Plan-Act-Validate):
    - **Plan:** Define implementation and testing.
    - **Act:** Apply surgical, idiomatic changes.
    - **Validate:** Run `go test ./...`. Use `-race` for concurrency-heavy code.

## 4. Essential Commands

| Command | Action |
|---------|--------|
| `./claudomator serve` | Start API server |
| `go test ./...` | Run all tests |
| `go test -race ./...` | Run tests with race detector (recommended) |
| `./claudomator run <file>` | Run a task file directly |
| `./claudomator list` | List tasks via CLI |
| `./scripts/deploy` | Build and deploy binary |