Otaku Haven

# Run: run-2026-04-25-20-10-23
# Purpose: Produce all 11 Operations SOPs for Otaku Haven

These instructions are the complete, authoritative rule set for this run. Do not
consult any other policy or scope file. If something you need is missing here,
stop and document it in `results.md`.

---

## Role

You are acting as **Developer**. Execute the tasks in `tasks.md` and produce the
deliverables listed there. You do not define scope.

---

## File Access

Permitted inputs:

- All files in `trail/runs/intent-004/run-2026-04-25-20-10-23/`
- `trail/meta/files/Otaku_Haven_Reference_Data.md`
- `trail/meta/files/Otaku_Haven_Document_Checklist.md`
- `Business Plan/03-HR/Employee-Handbook.docx`
- `Business Plan/02-Strategic/Business-Plan.docx`
- `Business Plan/02-Strategic/Financial-Model.xlsx`

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 in `trail/intents/` or `trail/meta/`. Those are Manager
inputs. If something is missing from the run artifacts, stop and document it
in `results.md`.

---

## Output Location

All 11 deliverables are written to:

```
Business Plan/04-Operations-SOPs/
```

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

---

## Acceptable Format

Word (.docx) only for all deliverables in this run.

---

## SOP Document Template

Every SOP must follow this exact structure, in this exact order. Deviation from
this structure is not permitted.

### Section 1 — Header Block (table at top of document)

| Field           | Value                       |
|-----------------|-----------------------------|
| SOP Title       | [Full title of this SOP]    |
| Document Number | SOP-00X                     |
| Effective Date  | June 1, 2026                |
| Last Revised    | June 1, 2026                |
| Approved By     | Store Manager               |

### Section 2 — Purpose

1–2 sentences stating why this procedure exists and what outcome it ensures.

### Section 3 — Scope

A statement of who this SOP applies to (which roles) and under what
circumstances (always, during specific shifts, during specific events, etc.).

### Section 4 — Responsibilities

A list or table identifying which role(s) own each aspect of the procedure.
Roles must match those in the reference data (Store Manager, Assistant Manager,
Key Holder, Sales Associate).

### Section 5 — Procedure

Numbered, sequential steps. Sub-steps use lettered indentation (a., b., c.).
Steps must be specific, actionable, and written so any trained team member can
follow them without additional instruction.

### Section 6 — Related Documents

Bulleted list of cross-references using exact SOP numbers and titles, Employee
Handbook sections referenced by name, and any forms mentioned (by name only —
forms are not produced in this run).

### Section 7 — Revision History

An empty table with three columns:

| Date | Description | Approved By |
|------|-------------|-------------|
|      |             |             |

---

## Cross-Document Coherence Rules

1. Pull all store facts (hours, roles, headcount, technology, address, product
   categories) from `Otaku_Haven_Reference_Data.md`. Do not invent facts.

2. Before producing any SOP that touches scheduling, discipline, safety, or
   technology use: read the relevant sections of `Employee-Handbook.docx` and
   use consistent language and policy references.

3. Before producing SOP-003 (Cash Handling): read `Financial-Model.xlsx` for
   cash flow assumptions. Choose specific dollar thresholds for the float,
   variance bands, and deposit size, and document them in `results.md`.

4. Cross-references between SOPs must use the exact document number and full
   title (e.g., "SOP-003: Daily Cash Handling and Reconciliation SOP").

5. Store hours: Monday–Saturday 10:00 AM – 9:00 PM, Sunday 11:00 AM – 7:00 PM.
   Total headcount: 8 employees. POS system: Square for Retail.
   Scheduling/timekeeping: Gusto. Do not contradict these.

---

## Forward-Reference Documentation (Required)

SOP-003 and SOP-005 establish values that Intent 5 (Finance and Compliance) and
Intent 7 (Customer and Marketing) will depend on. After producing these two SOPs,
record the specific values chosen in `results.md` under the designated sections.

**From SOP-003 — record in results.md:**
- Starting cash float amount ($)
- Variance threshold requiring manager notification ($)
- Variance threshold requiring escalation or investigation ($)
- Daily deposit frequency (once per day / per shift / other)
- Deposit method (bank drop, armored, staff deposit, other)
- Safe access policy (who has access)

**From SOP-005 — record in results.md:**
- Return window (number of days from purchase)
- Receipt requirement (required or optional)
- Accepted refund methods (original payment, store credit, other)
- Condition requirements for return eligibility
- Exchange-only scenarios (items not eligible for refund)
- Manager override scenarios and authorization level

---

## Assumptions & Ambiguity

- Do not ask questions. Document all assumptions in `results.md`.
- If you must choose a value not specified in the reference data (e.g., a specific
  dollar threshold), choose the most operationally realistic value for an 1,800 sq ft,
  8-person retail store and document it.
- Never silently guess. Every non-obvious choice goes in `results.md`.

---

## Failure Handling

- Failure is acceptable. Silent failure is not.
- If a coherence conflict is detected between reference data and a prior
  deliverable, stop and document the conflict in `results.md`. Do not choose
  a value and continue silently.
- If you cannot proceed without inventing scope or violating these rules, stop
  and document why in `results.md`.

---

## Scope Boundary

Produce only the 11 SOPs listed in `tasks.md`. Do not produce:
- Standalone forms (incident report, complaint form, inventory adjustment form)
  — SOPs may reference these by name only
- Employee Handbook policies (already exist in Intent 3)
- Training materials (already exist in Intent 3)
- Any customer-facing version of the return policy (Intent 7 scope)