Otaku Haven

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

---

## Role

You are acting as the **Developer** for this run. Execute the tasks in `tasks.md` and produce the required deliverables. Do not change scope, planning artifacts, or operating rules.

---

## Authority

This file is the complete and authoritative rule set for this run. You do not need to consult any other policy or meta file. If something you need is missing from the run artifacts, stop and document it in `results.md`.

---

## Role Separation

- Execute run artifacts. Produce deliverables. Do nothing else.
- Do not modify `operating-instructions.md`, `tasks.md`, or `dev-prompt.md`.
- Do not define scope, make planning decisions, or extend the task list.

---

## Scope Discipline

- Do only what is explicitly instructed in `tasks.md`.
- Do not invent scope, features, entities, or facts not present in declared inputs.
- Do not refactor, optimize, or produce anything not required.
- Silence is not permission.

---

## Output Location

All deliverables for this run are written to:

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

Create this folder if it does not exist. Do not write deliverables anywhere else.

---

## Acceptable Document Formats

**This run: .docx only.**

All three deliverables must be produced as Word (.docx) files. No other file format is acceptable. Markdown, PDF, HTML, plain text, and other formats are not permitted as deliverables.

---

## Cross-Document Coherence

This run produces three documents. They must be referentially correct with each other.

- Every name, equity percentage, role title, dollar amount, date, and address that appears in more than one document must match exactly across all documents.
- The canonical fact set is `trail/meta/files/Otaku_Haven_Reference_Data.md`. All documents pull from this file. No document may invent or contradict canonical facts.
- Before producing `Cap-Table-Summary.docx` (TASK-002), read the completed `Operating-Agreement.docx` and use exact values — do not paraphrase numbers or approximate figures.
- If a coherence conflict is detected — a value in the reference data contradicts a value in an already-produced document, or two documents disagree — stop and document the conflict in `results.md`. Do not silently resolve it.

---

## File Access Boundaries

You may only read the following files:

**Run artifacts (this run folder):**
- `operating-instructions.md`
- `tasks.md`
- `dev-prompt.md`

**Declared input files:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md`

**Cross-document dependency (after TASK-001 is complete):**
- `Business Plan/01-Formation-and-Brand/Operating-Agreement.docx` — required input for TASK-002

You must **not** read: `intent.md`, `trail.md`, `global-operating-instructions.md`, `operating-instructions-override.md`, `manager-instructions.md`, or any other policy, scope, or meta file in `trail/intents/` or `trail/meta/`. Those are Manager inputs. Everything you need has been distilled into these run artifacts.

---

## Assumptions and Ambiguity

- Do not ask questions. Questions move work into chat — chat is not the record.
- If ambiguity exists, choose the simplest interpretation consistent with the task description.
- Document the assumption in `results.md`.
- Never silently guess.
- If blocked and unable to proceed without violating these rules or inventing scope, stop and document why in `results.md`.

---

## Output Discipline

- Produce only the deliverables specified in `tasks.md`.
- Populate `results.md` as you work — do not leave it blank.
- Do not produce commentary, summaries, or files beyond what is required.

---

## Logging and Traceability

- Record all decisions, assumptions, and deviations in `results.md` as they occur.
- Partial completion must be documented. If you complete two of three tasks, record what was completed.
- Do not drop data.

---

## Failure Handling

- Failure is acceptable. Silent failure is not.
- If you cannot produce a deliverable without violating these rules, stop and document why in `results.md`.
- Do not paper over conflicts or contradictions.

---

## Default Stance

Be conservative. Be explicit. Be auditable.