Otaku Haven

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

---

## Role

You are 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, policies, 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/03-HR/
```

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

---

## Acceptable Document Formats

**This run: .docx only.**

All nine deliverables must be produced as Word (.docx) files. No other file format is acceptable for this run. Excel, PowerPoint, Markdown, PDF, HTML, and plain text are not permitted as deliverables.

---

## Texas Employment Law Compliance

All HR policies in this run must comply with Texas employment law. Mandatory requirements:

- **At-will employment:** Texas is an at-will employment state. Every employment policy document must be consistent with at-will employment. An explicit at-will statement must appear in the Employee Handbook and in both offer letter templates. No language anywhere in any document may create an implied employment contract or limit the at-will relationship.
- **No state income tax:** Texas has no state income tax. Do not reference Texas state income tax withholding as an employer or employee obligation.
- **No mandated breaks:** Texas law does not require meal or rest breaks for adult employees. A voluntary break policy is acceptable as a best practice but must not be described as legally required.
- **Harassment and discrimination:** Texas employment discrimination law is aligned with federal law. The anti-harassment policy must reference both federal protections (Title VII of the Civil Rights Act, ADA, ADEA) and Texas law where applicable.
- **Workplace violence:** Texas handbook guidance requires an explicit workplace violence prevention section. This is required, not optional.
- **Final pay timing:** Texas law requires that a discharged employee's final pay be issued within 6 days of termination; a resigned employee receives their final pay on the next regular payday. This must be reflected in the Discipline and Termination section of the Employee Handbook.
- **Texas Workforce Commission (TWC):** May be referenced in the handbook where applicable (e.g., unemployment, labor law complaints).

---

## Cross-Document Coherence

This run produces nine documents. All nine must be internally consistent with each other and with the declared input files.

**Rules:**
- Every name, title, compensation figure, store hour, system name, policy term, or assumption that appears in more than one document must match exactly.
- 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.
- If a coherence conflict is detected — between two produced documents, between a produced document and the reference data, or between a produced document and a prior deliverable — stop and document the conflict in `results.md`. Do not silently resolve it.

**Required consistency across this run's documents:**

| Fact | Required Value | Appears In |
|---|---|---|
| Store Manager compensation | $65,000/year | Handbook, JD-SM, Offer-Salaried |
| Assistant Manager compensation | $20.00/hour | Handbook (if ref'd), JD-AM, Offer-Hourly |
| Key Holder compensation | $18.00/hour | JD-KH, Offer-Hourly |
| Sales Associate compensation | $15.00/hour | JD-SA, Offer-Hourly |
| Store hours | Mon–Sat 10am–9pm, Sun 11am–7pm | Handbook, all 4 JDs, Onboarding |
| Holiday hours | Closed Thanksgiving Day & Christmas Day; reduced hours Christmas Eve & New Year's Day | Handbook |
| Payroll/HRIS system | Gusto | Handbook, Onboarding, Offer letters |
| POS system | Square for Retail | Handbook, JD-SM, JD-AM, JD-KH, JD-SA, Onboarding |
| Total headcount | 8 (1 SM, 1 AM, 2 KH, 4 SA) | JD-SM responsibilities, Handbook (if ref'd) |
| Entity legal name | Otaku Haven LLC | All documents |
| DBA / trade name | Otaku Haven | All documents |
| Store address | 2847 S Lamar Blvd, Suite 105, Austin, TX 78704 | All documents |
| SM exempt status | Exempt, Salaried | JD-SM, Offer-Salaried, Handbook (timekeeping) |
| AM/KH/SA status | Non-exempt, Hourly | JD-AM, JD-KH, JD-SA, Offer-Hourly |
| Product categories | 8 categories per reference data | Anime Product Knowledge Guide, JD-SA |

---

## 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 dependencies (required for TASK-001 only — read before producing the Employee Handbook):**
- `Business Plan/01-Formation-and-Brand/Operating-Agreement.docx`
- `Business Plan/02-Strategic/Financial-Model.xlsx`
- `Business Plan/02-Strategic/Business-Plan.docx`

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` under "Assumptions Made."
- Never silently guess.
- If blocked and unable to proceed without violating these rules or inventing scope, stop and document why in `results.md` under "Open Questions/Blockers."

---

## 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 six of nine tasks, record what was completed and what remains.
- 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.