Otaku Haven

# Operating Instructions — Intent 006, Run 2026-04-25-10-00-00

**Your role:** Developer
**Intent:** Vendor, Product, and Supply Chain
**Run folder:** `trail/runs/intent-006/run-2026-04-25-10-00-00/`

---

## What You Are Doing

You are producing 5 vendor and supply chain documents for Otaku Haven LLC — a fictional anime retail store in Austin, Texas. These documents establish how inventory is sourced, ordered, received, and managed from a vendor relationship perspective.

---

## Your Permitted File Inputs

You may read ONLY the following:

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

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

**Cross-document dependencies (prior deliverables — read before producing dependent documents):**
- `Business Plan/04-Operations-SOPs/SOP-007-Inventory-Receiving.docx`
- `Business Plan/04-Operations-SOPs/SOP-011-Vendor-Consignment.docx`
- `Business Plan/05-Finance-and-Compliance/Inventory-Valuation-Policy.docx`
- `Business Plan/05-Finance-and-Compliance/Chart-of-Accounts.xlsx`
- `Business Plan/05-Finance-and-Compliance/Cash-Management-Policy.docx`

You must **not** read any other file in `trail/` — including intent files, meta policy files, or manager instructions. If something you need is missing from these run artifacts, stop and document it in `results.md`.

---

## Output Location and Formats

All deliverables must be written to: `Business Plan/06-Vendor-Supply-Chain/`

Create that subfolder if it does not exist.

Acceptable formats:
- **Word (.docx)** — narrative documents, policies, agreements
- **Excel (.xlsx)** — templates, lists, workbooks

No other formats are permitted. No Markdown, PDF, HTML, or plain text deliverables.

---

## Cross-Document Coherence Rules

- Every fact, number, role title, dollar amount, and term that appears in a prior deliverable must match exactly in any document that references it. Do not paraphrase or approximate.
- The canonical fact set is `trail/meta/files/Otaku_Haven_Reference_Data.md`. All shared facts (store address, product categories, technology stack, role names) come from there.
- Before producing a document that has a cross-document dependency listed above, read that dependency and use its exact values.
- If you detect a conflict between the reference data and a prior deliverable, stop and document it in `results.md`. Do not silently resolve it.

---

## Scope Discipline

- Do only what is explicitly described in `tasks.md` and `dev-prompt.md`.
- Do not add deliverables, sections, or features not listed.
- Do not modify any file outside `Business Plan/06-Vendor-Supply-Chain/` or `results.md`.

---

## Assumptions and Blocking

- If you must make an assumption to proceed, make the simplest interpretation consistent with the task, then document it in `results.md`.
- If you are blocked and cannot proceed without inventing scope or violating these rules, stop and document why in `results.md`.
- Do not ask questions in chat. All decisions go in `results.md`.

---

## On Completion

- Update `results.md` with: each deliverable produced, any assumptions made, any conflicts detected, and the consignment revenue split chosen (this value will be referenced by a future intent).
- Partial completion must still be documented.