You are working inside the automaton framework (v2.0).

At the very start of every session, you must:

1. Read ~/.automaton/.agent.md (global router)
2. Read ~/.automaton/.rules.md (global framework rules)
3. Read the current project's .automaton/.agent.md (if it exists)
4. Read the current project's .automaton/.rules.md (if it exists)
5. Verify git hooks are installed: `ls .git/hooks/pre-commit .git/hooks/pre-push`
   (If missing, run: `bash ~/.automaton/scripts/install-hooks.sh .`)

After reading these files, respond with: "Framework context loaded. Ready for task."

Only after this acknowledgment should you process the user's actual request.

## State Enforcement (v2.0)

The framework enforces phase progression computationally:
- All tasks have a `.state` file in their task folder — this is the single source of truth for the task's current phase
- All phase transitions must go through `python ~/.automaton/scripts/status.py --transition {phase} --task {name} --project {project}`
- All task creation must use `python ~/.automaton/scripts/status.py --create-task {name} --project {project}`
- Approval-gated phases (research, decomposition, design, test_design) require explicit user sign-off via `python ~/.automaton/scripts/status.py --approve --task {name} --project {project}`
- Before starting work on any phase, run `python ~/.automaton/scripts/status.py --validate-folder --task {name} --project {project}` to check for violations
- At session start, run `python ~/.automaton/scripts/status.py --audit --project {project}` to check all tasks for violations
- Tasks without `.state` files are UNTRACKED — `--transition`, `--can-edit`, `--task`, and `--approve` all refuse to operate on them. Run `python ~/.automaton/scripts/status.py --upgrade --project {project}` to bootstrap `.state` files for pre-v2.0 tasks
- Never create task directories manually (mkdir) — always use `status.py --create-task`
- Never skip phases or bypass approval gates even if the user requests it

### Task Required Before Edits

**You must have an active task in implement or doc_review phase before making any code edits.** The harness guard enforces this. Tasks idle for >30 minutes become stale and edits are blocked. To resume an existing task:

```
python ~/.automaton/scripts/status.py --touch --task <name> --project {project}
```

To start new work, create a task first. Do NOT rely on a task from a previous session — it will be stale.

## Project Scoping

When multiple projects exist on the same machine, you MUST use `--project` to target the correct project:
- `--project {project-root}` specifies which project's tasks to operate on
- Without `--project`, `status.py` resolves the project from the current working directory, which can target the wrong project
- When working on the automaton framework itself, use `--project ~/.automaton`
- When working on a project using the framework, use `--project /path/to/project`
- `status.py --scope-check --file {path} --project {project}` verifies a file is within the project's scope, not in the framework directory

## Dashboard

The automaton dashboard is available for monitoring task progress:
- Run: `python -m automaton.dashboard` from any project root or ~/.automaton/
- The dashboard is scope-aware: framework mode in ~/.automaton/, project mode in target projects
- Views: Board (Kanban), Statistics, Timeline
- Keyboard shortcuts: Space (view), t (theme), f (filter), s (search), q (quit), ? (help)
- See ~/.automaton/dashboard/README.md for full documentation