Otaku Haven

# Run: run-2026-04-25-14-45-09
# Purpose: Produce formation, governance, and brand documents for Otaku Haven LLC

---

## Your Role

You are the **Developer** for this run. Your job is to execute the tasks in `tasks.md` and produce the required deliverables. You do not define scope, change plans, or modify run artifacts.

---

## Files You Must Read

Read these files before beginning execution. Read them in this order:

1. `trail/runs/intent-001/run-2026-04-25-14-45-09/operating-instructions.md` — **read first**; this file governs all of your behavior for this run
2. `trail/runs/intent-001/run-2026-04-25-14-45-09/tasks.md` — the exact work to perform
3. `trail/meta/files/Otaku_Haven_Reference_Data.md` — canonical fact set; required for all three tasks

**Additional input required for TASK-002 only (read after completing TASK-001):**

4. `Business Plan/01-Formation-and-Brand/Operating-Agreement.docx` — read before producing the Cap Table Summary to confirm exact values; this file does not exist until you produce it in TASK-001

You must not read any file not listed above or not listed in `tasks.md`. Do not read `intent.md`, `trail.md`, `global-operating-instructions.md`, `operating-instructions-override.md`, `manager-instructions.md`, or any other file in `trail/intents/` or `trail/meta/` other than the declared input listed above.

---

## Run Scope

This run produces exactly three deliverables:

1. `Business Plan/01-Formation-and-Brand/Operating-Agreement.docx`
2. `Business Plan/01-Formation-and-Brand/Cap-Table-Summary.docx`
3. `Business Plan/01-Formation-and-Brand/Brand-Style-Guide.docx`

No other deliverables are in scope. Do not produce additional documents, templates, or files.

---

## Execution Order

Execute tasks in this order:

1. **TASK-001** — Produce `Operating-Agreement.docx`
2. **TASK-002** — Produce `Cap-Table-Summary.docx` (requires TASK-001 to be complete first)
3. **TASK-003** — Produce `Brand-Style-Guide.docx` (independent; may follow TASK-001 or TASK-002)

Do not begin TASK-002 until `Operating-Agreement.docx` exists and you have read it.

---

## Output Folder

Write all deliverables to:

```
Business Plan/01-Formation-and-Brand/
```

Create this folder if it does not exist.

---

## Required Outputs

| File | Path |
|---|---|
| Operating-Agreement.docx | `Business Plan/01-Formation-and-Brand/Operating-Agreement.docx` |
| Cap-Table-Summary.docx | `Business Plan/01-Formation-and-Brand/Cap-Table-Summary.docx` |
| Brand-Style-Guide.docx | `Business Plan/01-Formation-and-Brand/Brand-Style-Guide.docx` |
| results.md (populated) | `trail/runs/intent-001/run-2026-04-25-14-45-09/results.md` |

All deliverables must be .docx format. No other format is acceptable.

---

## Handling Ambiguity

If you encounter ambiguity in a task:

1. Choose the simplest interpretation consistent with the task description and the canonical fact set.
2. Document the decision in `results.md` under "Assumptions Made."
3. Do not ask questions. Do not stop unless you are genuinely blocked.

If you are blocked — unable to proceed without violating `operating-instructions.md` or inventing facts not in the reference data:

1. Stop that task.
2. Document the blocker in `results.md` under "Open Questions/Blockers."
3. Move to the next task if it is not dependent on the blocked task.

---

## Populating results.md

Update `results.md` as you work. Do not leave it blank. After each task completes, record:

- The task ID and that it is complete under "Tasks Completed"
- The file path of the produced deliverable under "Files Changed/Added"
- Any assumptions or decisions under "Assumptions Made"
- Any deviations from the task description under "Deviations from Plan"
- Any unresolved issues under "Open Questions/Blockers"

---

## Validation Before Finishing

Before marking execution complete, verify:

1. All three .docx files exist at their specified output paths.
2. `Operating-Agreement.docx` and `Cap-Table-Summary.docx` use identical names, percentages, roles, and capital figures.
3. `Brand-Style-Guide.docx` entity information (name, address, digital handles) matches the reference data.
4. `results.md` is fully populated.
5. No deliverable was produced in a format other than .docx.