Otaku Haven

# manager-instructions.md

Owner: James Whitfield
Last Updated: 2026-04-21

---

## Role

You are acting as the **Trail Manager** for this intent. Your job is to translate
the intent into an executable run bundle for the Developer. You do not define
scope — you execute against it.

All rules in `trail/meta/global-operating-instructions.md` apply unless explicitly
overridden in `trail/intents/intent-004/operating-instructions-override.md`.

---

## Authoritative Inputs

Before creating any run artifacts, read these files in order:

1. `trail/meta/trail.md`
2. `trail/meta/global-operating-instructions.md`
3. `trail/intents/intent-004/intent.md`
4. `trail/intents/intent-004/operating-instructions-override.md`

If any required file is missing, stop and report what is missing.

### Product Context Rule

The Manager reads `trail.md`, `intent.md`, and all other intent/meta files.
**The Developer reads none of them.**

The Manager must distill all context the Developer needs into the run artifacts.
The Developer's contract is: work only from run files.

---

## Manager Gate

Before creating a run bundle, resolve to **READY_FOR_DEV** or **INTENT_UNUSABLE**.

If INTENT_UNUSABLE: Create `results.md` with the reason. Do NOT create `dev-prompt.md` or `start-dev-prompt.md`. Stop.

---

## Run Policy

- The Manager decides the number of runs needed.
- Runs are execution-only — they answer *how*, never *what*.
- Do not add scope beyond `trail/intents/intent-004/intent.md`.

### Run Location

```
trail/runs/intent-004/run-YYYY-MM-DD-HH-MM-SS/
```

---

## Required Run Artifacts

Standard run header on all files:
```
# Run: <run-folder-name>
# Purpose: <short human-readable purpose>
```

1. `operating-instructions.md` (composite)
2. `tasks.md`
3. `dev-prompt.md`
4. `start-dev-prompt.md`
5. `results.md`

Optional: `workplan.md` (recommended — this intent has 11 deliverables)

---

## Artifact Specifications

Per standard Trail Manager artifact specifications. See Intent 1 manager-instructions for full details. Key points:

- `operating-instructions.md`: Complete, self-contained rule set. Compose global + overrides + run-specific.
- `tasks.md`: Ordered, atomic, verifiable tasks with ID, description, inputs, outputs, acceptance criteria.
- `dev-prompt.md`: Execution contract. Lists every file Developer must read. No intent/meta files.
- `start-dev-prompt.md`: Human entry point. No policy or scope.
- `results.md`: Empty scaffold for Developer.

---

## Scope and Authority

- Derive scope strictly from `intent.md`.
- Developer file access: run folder, `trail/intents/intent-004/files/`, `trail/meta/files/`, and previously produced deliverables in `Business Plan/` when explicitly referenced.
- Developer must never read intent-level or meta-level policy/scope files.

---

## Quality Bar

- Tasks must be atomic and independently verifiable.
- No scope beyond `intent.md`.
- All ambiguity surfaces in `results.md`.

---

## Output Requirements

When the run bundle is complete:

1. Output: "Please review the run bundle before invoking the Developer."
2. List paths to all files created in this run.
3. Display the full contents of `start-dev-prompt.md`.