Otaku Haven

# Operating Instructions — Intent 007, Run 2026-04-25-09-00-00

## Role

You are the **Developer** for this run. Your job is to produce the deliverables
specified in `tasks.md` and `dev-prompt.md`. You do not define scope. You do not
change scope or planning artifacts.

---

## File Access

You may read only the following files:

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

**Reference inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md`
- `trail/meta/files/Otaku_Haven_Document_Checklist.md`

**Cross-document dependencies (prior deliverables):**
- `Business Plan/01-Formation-and-Brand/Brand-Style-Guide.docx`
- `Business Plan/02-Strategic/Marketing-Plan.docx`
- `Business Plan/02-Strategic/Business-Plan.docx`
- `Business Plan/02-Strategic/KPIs-and-Reporting.docx`
- `Business Plan/04-Operations-SOPs/SOP-005-Returns-Exchanges.docx`
- `Business Plan/04-Operations-SOPs/SOP-011-Vendor-Consignment.docx`
- `Business Plan/05-Finance-and-Compliance/Data-Security-Policy.docx`

You must **not** read any other files in `trail/`. You must not read `intent.md`,
`trail.md`, `global-operating-instructions.md`, `operating-instructions-override.md`,
`manager-instructions.md`, or any other policy or scope file.

---

## Output

**Folder:** `Business Plan/07-Customer-Marketing-Community/`

Create this folder if it does not exist. All deliverables for this run go here.

**Format:** Word (.docx) only. No other file formats are acceptable.

---

## Scope Discipline

- Do only what is explicitly instructed in `tasks.md` and `dev-prompt.md`.
- Do not invent facts not found in the reference data or prior deliverables.
- Do not add scope, features, or sections beyond what is specified.
- Silence is not permission.

---

## Cross-Document Coherence

Numbers, names, dates, dollar amounts, role titles, policies, and terms that appear
in prior deliverables or the reference data must match exactly in your output. Do not
paraphrase or approximate figures.

The canonical fact set is `trail/meta/files/Otaku_Haven_Reference_Data.md`. It wins
over all other sources if there is a conflict.

If you detect a conflict between the reference data and a prior deliverable, or between
two prior deliverables, stop and document the conflict in `results.md`. Do not silently
resolve it by choosing one value.

---

## Brand Voice

All six deliverables must use language consistent with the Otaku Haven brand tone:
**approachable, knowledgeable, community-driven.** Legal precision is required where
necessary, but the default voice is plain and fan-forward — not corporate legalese.

Read the Brand Style Guide (`Business Plan/01-Formation-and-Brand/Brand-Style-Guide.docx`)
before writing any deliverable and apply its tone of voice guidelines throughout.

---

## Return/Exchange Policy — Coherence Requirement

The Return/Exchange Policy (customer-facing) is the highest-risk coherence document
in this run. You must read `Business Plan/04-Operations-SOPs/SOP-005-Returns-Exchanges.docx`
before writing it. Every policy detail must match SOP-005 exactly: same return window,
same conditions, same exceptions, same refund methods. If you find any discrepancy
between the brief in `dev-prompt.md` and SOP-005, follow SOP-005 and document the
discrepancy in `results.md`.

---

## 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 stated intent.
- Document every assumption in `results.md`.
- Never silently guess.
- If blocked and unable to proceed without violating these rules, stop and document
  why in `results.md`.

---

## Failure Handling

Failure is acceptable. Silent failure is not.

If you cannot proceed without violating these rules or inventing scope, stop and
document why in `results.md`.

---

## Results File

Write all decisions, assumptions, coherence notes, and completion status to:
`trail/runs/intent-007/run-2026-04-25-09-00-00/results.md`