Otaku Haven

# Run: run-2026-04-25-19-40-35
# Purpose: Produce HR, employment, and people documents for Otaku Haven LLC

---

## Your Role

You are the **Developer** for this run. You execute. You do not define scope.

---

## Files to Read — In This Order

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

**Additional inputs required for TASK-001 only — read these before producing the Employee Handbook:**

4. `Business Plan/01-Formation-and-Brand/Operating-Agreement.docx`
5. `Business Plan/02-Strategic/Financial-Model.xlsx`
6. `Business Plan/02-Strategic/Business-Plan.docx`

These are your only permitted inputs. Read nothing else. 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/` beyond the reference data file listed above.

---

## Required Outputs

| File | Path |
|---|---|
| Employee-Handbook.docx | `Business Plan/03-HR/Employee-Handbook.docx` |
| Job-Description-Store-Manager.docx | `Business Plan/03-HR/Job-Description-Store-Manager.docx` |
| Job-Description-Assistant-Manager.docx | `Business Plan/03-HR/Job-Description-Assistant-Manager.docx` |
| Job-Description-Key-Holder.docx | `Business Plan/03-HR/Job-Description-Key-Holder.docx` |
| Job-Description-Sales-Associate.docx | `Business Plan/03-HR/Job-Description-Sales-Associate.docx` |
| Offer-Letter-Template-Salaried.docx | `Business Plan/03-HR/Offer-Letter-Template-Salaried.docx` |
| Offer-Letter-Template-Hourly.docx | `Business Plan/03-HR/Offer-Letter-Template-Hourly.docx` |
| New-Hire-Onboarding-Checklist.docx | `Business Plan/03-HR/New-Hire-Onboarding-Checklist.docx` |
| Anime-Product-Knowledge-Guide.docx | `Business Plan/03-HR/Anime-Product-Knowledge-Guide.docx` |
| results.md (populated) | `trail/runs/intent-003/run-2026-04-25-19-40-35/results.md` |

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

---

## Execution Order

1. Read `operating-instructions.md` and `tasks.md` fully before beginning any production work.
2. Read `trail/meta/files/Otaku_Haven_Reference_Data.md`.
3. Read the three prior deliverables listed above (Operating-Agreement, Financial-Model, Business-Plan). Verify all three files exist before proceeding. If any file is missing, stop and document in `results.md`.
4. Create `Business Plan/03-HR/` if it does not already exist.
5. Execute TASK-001 through TASK-009 (production tasks). These tasks are largely independent — complete them in any order. Populate `results.md` after each task completes.
6. Execute TASK-010 (coherence check) after all nine production tasks are complete.
7. Ensure `results.md` is fully populated before declaring the run complete.

---

## Critical Constraints

- Output format is **.docx only** for all nine deliverables. No exceptions.
- All compensation figures must exactly match the reference data: Store Manager $65,000/year (exempt/salaried), Assistant Manager $20.00/hour (non-exempt/hourly), Key Holder $18.00/hour (non-exempt/hourly), Sales Associate $15.00/hour (non-exempt/hourly).
- All documents must comply with **Texas employment law** as specified in `operating-instructions.md`. At-will language is required in the Employee Handbook and both offer letter templates.
- **Gusto** is the payroll, HRIS, and benefits system. **Square for Retail** is the POS system. Use these exact names wherever these systems are referenced.
- Store hours: **Monday–Saturday 10:00 AM–9:00 PM, Sunday 11:00 AM–7:00 PM**. Use these exact hours wherever store hours are referenced.
- Do not invent facts not present in the declared inputs. If you need a fact that isn't in the declared inputs, document the gap in `results.md` and make the simplest reasonable assumption.

---

## Ambiguity Handling

If ambiguity arises: choose the simplest interpretation consistent with `tasks.md`. Document the decision in `results.md` under "Assumptions Made." If you cannot proceed without inventing scope or violating `operating-instructions.md`, stop and document the blocker under "Open Questions/Blockers."

---

## Populating results.md

Update `results.md` continuously as you work. After each task, record:
- The task ID and status (complete or blocked) under "Tasks Completed"
- The file path of any produced deliverable under "Files Changed/Added"
- Any decisions or assumptions under "Assumptions Made"
- Any deviations from the task description under "Deviations from Plan"
- Any unresolved issues under "Open Questions/Blockers"

---

## Run Completion Validation

Before declaring this run complete, verify all of the following:

- [ ] `Business Plan/03-HR/` folder exists
- [ ] All 9 .docx deliverables exist at their specified output paths
- [ ] TASK-001: Employee Handbook contains all 8 policy sections and a table of contents
- [ ] TASK-002–005: All 4 job descriptions contain correct compensation and correct exempt/non-exempt classification
- [ ] TASK-006: Salaried offer letter template has at-will language and all [PLACEHOLDER] fields
- [ ] TASK-007: Hourly offer letter template has at-will language, FLSA overtime language, and all [PLACEHOLDER] fields
- [ ] TASK-008: Onboarding checklist covers all 5 phases; Gusto and Square for Retail referenced correctly
- [ ] TASK-009: Anime Product Knowledge Guide covers all 8 product categories and all 10 named franchises
- [ ] TASK-010: All 9 coherence checks documented in `results.md` with PASS or FLAG status
- [ ] `results.md` fully populated: Tasks Completed, Files Changed/Added, Deviations from Plan, Assumptions Made, Open Questions/Blockers