Otaku Haven

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

All tasks produce Word (.docx) files written to `Business Plan/04-Operations-SOPs/`.
All SOPs use the exact template defined in `operating-instructions.md`.
See `workplan.md` for recommended production order and groupings.

---

## SOP Template (use on every task)

Every SOP must contain exactly these seven sections in this order:

```
1. Header Block (table)
   - SOP Title
   - Document Number: SOP-00X
   - Effective Date: June 1, 2026
   - Last Revised: June 1, 2026
   - Approved By: Store Manager

2. Purpose
   [1–2 sentences]

3. Scope
   [Who and when]

4. Responsibilities
   [Role → responsibility mapping]

5. Procedure
   [Numbered steps with lettered sub-steps]

6. Related Documents
   [Exact SOP numbers/titles, handbook sections, form names]

7. Revision History (empty table)
   Date | Description | Approved By
```

Roles available: Store Manager, Assistant Manager, Key Holder, Sales Associate.

---

## TASK-000: Read Inputs and Verify Dependencies

**ID:** TASK-000
**Description:** Read all required inputs before beginning production. Verify
that the three cross-document dependency files exist and are readable.

**Inputs:**
- `trail/runs/intent-004/run-2026-04-25-20-10-23/operating-instructions.md`
- `trail/runs/intent-004/run-2026-04-25-20-10-23/tasks.md` (this file)
- `trail/runs/intent-004/run-2026-04-25-20-10-23/workplan.md`
- `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`

**Outputs:** None. This is a read-only verification step.

**Acceptance Criteria:**
- All 8 input files confirmed readable
- If any cross-document dependency file is missing, stop and document in `results.md`

---

## TASK-001: SOP-001 Store Opening Procedures

**ID:** TASK-001
**Description:** Produce the Store Opening Procedures SOP. This document covers
all steps required to prepare the store for business each morning, from staff
arrival through unlocking doors for customers.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — hours, roles, technology, address
- `Business Plan/03-HR/Employee-Handbook.docx` — scheduling and technology use policies

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-001-Store-Opening.docx`

**Content Requirements:**
- Opening times: Mon–Sat doors open at 10:00 AM, Sun at 11:00 AM
- Staff arrival time should precede door open by a reasonable interval (suggest 30–45 min)
- Cover all of the following steps in the Procedure section:
  1. Staff arrival and sign-in (reference Gusto timekeeping)
  2. Alarm deactivation
  3. Lights, HVAC, and equipment power-on sequence
  4. Cash drawer setup (reference SOP-003: Daily Cash Handling and Reconciliation SOP)
  5. Square for Retail POS system startup and login
  6. Merchandise walkthrough: check displays, facing, no missing items, no damage
  7. Signage and promotional displays check
  8. Fitting room / restroom check (if applicable per store layout)
  9. Unlock front door and flip Open sign at designated opening time
  10. Brief team huddle (optional but noted as best practice)
- Responsibilities section must specify which roles perform opening (typically Key Holder or above)
- Related Documents: SOP-003, SOP-004, Employee Handbook (scheduling section)

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- Opening times match Mon–Sat 10:00 AM, Sun 11:00 AM
- Gusto referenced for timekeeping sign-in
- Square for Retail referenced for POS startup
- SOP-003 referenced in Related Documents (exact title)
- Roles are limited to those in the reference data

---

## TASK-002: SOP-002 Store Closing Procedures

**ID:** TASK-002
**Description:** Produce the Store Closing Procedures SOP. This document covers
all steps required to close the store safely and securely at end of business.

**Prerequisite:** Produce TASK-003 (SOP-003) before this task so the cash
reconciliation reference is accurate.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — hours, roles, technology
- `Business Plan/03-HR/Employee-Handbook.docx` — scheduling, security policies

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-002-Store-Closing.docx`

**Content Requirements:**
- Closing times: Mon–Sat 9:00 PM, Sun 7:00 PM
- Cover all of the following steps in the Procedure section:
  1. Last customer announcement (15 minutes before close)
  2. Final customer sweep to ensure store is clear
  3. Lock front door at closing time
  4. Register closing and end-of-day reconciliation (reference SOP-003: Daily Cash Handling and Reconciliation SOP)
  5. Run end-of-day sales report in Square for Retail
  6. Cash deposit preparation (per SOP-003)
  7. Merchandise and display security check (high-value items secured)
  8. Lights-out sequence, equipment shutdown
  9. HVAC adjustment for overnight
  10. Cleaning tasks (note scope: basic tidying only; not a full cleaning SOP)
  11. Final walkthrough for any safety issues
  12. Alarm activation
  13. Lock up and exit; verify door is locked
  14. Sign out in Gusto
- Responsibilities: specify closing manager role (Key Holder or above for final lock-up)
- Related Documents: SOP-003, SOP-004, SOP-009, Employee Handbook

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- Closing times match Mon–Sat 9:00 PM, Sun 7:00 PM
- SOP-003 referenced by exact title in both Procedure and Related Documents
- Alarm activation step included
- Gusto sign-out referenced
- Key Holder or above designated for final lock-up authority

---

## TASK-003: SOP-003 Daily Cash Handling and Reconciliation

**ID:** TASK-003
**Description:** Produce the Daily Cash Handling and Reconciliation SOP. This
is a forward-reference document — all dollar thresholds chosen must be
documented in `results.md`. Intent 5 (Cash Management and Internal Controls
Policy) will reference these values.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — staffing, technology
- `Business Plan/02-Strategic/Financial-Model.xlsx` — cash flow assumptions

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-003-Cash-Handling.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  1. Starting cash float setup (specify dollar amount; document in results.md)
  2. Cash drawer assignment and accountability
  3. Making change procedures
  4. Handling large bills (counterfeit detection)
  5. Mid-day cash pull procedures (if float exceeds a threshold)
  6. Register reconciliation at end of shift/day: count cash, compare to Square report
  7. Variance documentation: who documents, using what form (reference Inventory Adjustment Form or Cash Variance Log by name)
  8. Variance thresholds: specify dollar amounts for (a) acceptable variance, (b) manager notification required, (c) investigation required — document all three in results.md
  9. Deposit preparation: envelope, amount, documentation
  10. Safe procedures: access, deposit drop, who holds combination/key
  11. Bank deposit: frequency, who carries, transport requirements
- Roles: specify who can open/close drawer, who reconciles, who has safe access
- Related Documents: SOP-001, SOP-002, SOP-004

**Dollar Threshold Guidance (if not found in Financial-Model.xlsx):**
Use operationally realistic values for an 1,800 sq ft retail store:
- Starting float: $200–$300 typical
- Acceptable variance: ±$5
- Manager notification threshold: >$10
- Investigation threshold: >$25

**Forward-Reference Requirement:**
After producing this SOP, record in `results.md` under "SOP-003 Forward References":
- Exact starting cash float amount chosen
- All three variance thresholds (acceptable, notify, investigate)
- Deposit frequency and method
- Who has safe access

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- All three variance thresholds are specific dollar amounts (not ranges)
- Safe procedures addressed
- Square for Retail referenced for end-of-day report
- All forward-reference values recorded in results.md
- Values are consistent with any cash assumptions found in Financial-Model.xlsx

---

## TASK-004: SOP-004 POS Usage and Transaction Handling

**ID:** TASK-004
**Description:** Produce the POS Usage and Transaction Handling SOP. This
document covers Square for Retail operations for all transaction types handled
at the register.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — technology stack, product categories, staffing

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-004-POS-Usage.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  1. POS login: how staff log in (individual Square accounts or shared terminal)
  2. Ringing a standard sale: item lookup, quantity, total, payment
  3. Payment methods accepted: cash, credit/debit, contactless, Square gift cards
  4. Applying discounts: specify who can authorize discounts and at what percentage thresholds
     (e.g., Sales Associate: up to 10%, Key Holder: up to 20%, Manager: above 20%)
     — document the specific thresholds chosen in results.md
  5. Processing Square gift cards: sale and redemption
  6. Handling split tender (partial cash, partial card)
  7. Processing voids and returns at POS (reference SOP-005 for full return policy)
  8. Handling declined transactions
  9. Running end-of-day Z-report and closing out the register
  10. Printing or emailing receipts
  11. Handling customer disputes at the register (escalation to manager)
- Responsibilities: who can perform voids, who can access manager functions in Square
- Related Documents: SOP-003, SOP-005

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- Square for Retail named explicitly throughout
- Discount authorization tiers specified with dollar or percentage thresholds
- Void and return steps present with reference to SOP-005
- End-of-day report step present with reference to SOP-003

---

## TASK-005: SOP-005 Returns, Exchanges, and Refunds

**ID:** TASK-005
**Description:** Produce the Returns, Exchanges, and Refunds SOP. This is a
forward-reference document — all policy details chosen (return window, refund
methods, condition requirements) must be documented in `results.md`. Intent 7
(customer-facing return policy) must match this internal SOP exactly.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — technology, product categories
- `Business Plan/03-HR/Employee-Handbook.docx` — any relevant policy language

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-005-Returns-Exchanges.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  1. Return window: specify number of days (recommend 30 days; document in results.md)
  2. Receipt requirements: with receipt vs. without receipt procedures
  3. Item condition requirements: unopened/original packaging vs. opened
  4. Refund methods available: original payment method, store credit, exchange
  5. Items not eligible for return (e.g., trading card packs once opened, digital codes,
     clearance items — define the list and document in results.md)
  6. Exchange procedure: same item, different variant; different item
  7. Defective product handling: return window exception, vendor warranty escalation
  8. Manager override scenarios: when a manager can approve a return outside normal policy
     — document the scenarios in results.md
  9. Processing the return in Square for Retail
  10. Restocking returned items or flagging for vendor return
- Responsibilities: who can approve standard returns (Sales Associate), who handles
  exceptions and overrides (Key Holder / Manager)
- Related Documents: SOP-004, Employee Handbook

**Forward-Reference Requirement:**
After producing this SOP, record in `results.md` under "SOP-005 Forward References":
- Return window (days)
- Whether receipt is required
- Accepted refund methods
- Items not eligible for return (full list)
- Manager override scenarios

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- Return window stated as a specific number of days
- Non-returnable items list is explicit
- Manager override scenarios listed
- Square for Retail referenced for processing
- All forward-reference values recorded in results.md

---

## TASK-006: SOP-006 Customer Service and Sales Floor Standards

**ID:** TASK-006
**Description:** Produce the Customer Service and Sales Floor Standards SOP.
This document defines Otaku Haven's approach to customer engagement, product
recommendations, and handling difficult situations on the sales floor.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — product categories, store concept, staffing
- `Business Plan/02-Strategic/Business-Plan.docx` — brand and customer experience language

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-006-Customer-Service.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  1. Greeting standards: timing (greet within X seconds of entry), language (knowledgeable
     enthusiasm, not aggressive sales)
  2. Sales floor engagement: how to approach browsing customers, open-ended questions
  3. Product knowledge expectations: categories the store carries (figures, manga, apparel,
     accessories, trading cards, media, consignment)
  4. Product recommendation approach: genre/interest-based, new arrivals, staff picks
  5. Handling customer questions the associate can't answer (escalation vs. research)
  6. Handling difficult customers: de-escalation steps, when to involve a manager
  7. Customer complaints: listening, acknowledging, resolution steps
  8. Phone inquiry handling: answering, placing on hold, taking messages, call-back expectations
  9. Social media / online inquiry notes (brief: staff do not handle social DMs;
     route to Store Manager)
  10. Line management at register during peak periods
- Responsibilities: all staff for floor standards; Key Holder and above for escalations
- Related Documents: SOP-005 (for complaint → return scenarios), Employee Handbook

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- All 7 product categories mentioned (figures, manga, apparel, accessories, trading cards,
  media, consignment)
- Escalation path to manager clearly defined
- Tone guidance aligns with "curated anime retail experience" brand concept

---

## TASK-007: SOP-007 Inventory Receiving, Stocking, and Cycle Counts

**ID:** TASK-007
**Description:** Produce the Inventory Receiving, Stocking, and Cycle Counts SOP.
This document covers the full inventory management lifecycle from delivery
acceptance through cycle counting.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — product categories, technology (Square for Retail inventory)
- `Business Plan/02-Strategic/Financial-Model.xlsx` — inventory valuation method

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-007-Inventory-Receiving.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  Part A — Receiving:
  1. Delivery arrival: who is authorized to accept deliveries
  2. Check shipment against purchase order: quantity, SKU, condition
  3. Documenting discrepancies: short shipment, damaged goods, wrong items
     (reference Receiving Discrepancy Report by name)
  4. Signing delivery confirmation
  Part B — Stocking:
  5. Entering received inventory into Square for Retail
  6. Labeling and pricing items (including price sticker placement standards)
  7. Shelving by category and planogram compliance
  8. New arrival highlighting: tagging, end cap placement
  Part C — Cycle Counts:
  9. Cycle count frequency (suggest weekly partial count by category; document in results.md)
  10. Cycle count method: how to count, how to record
  11. Entering count results in Square for Retail
  12. Variance investigation threshold: when to investigate discrepancies
  13. Inventory adjustment documentation
- Note: Product arrives via delivery to storefront — no warehouse or separate receiving dock
- Responsibilities: Store Manager / Assistant Manager for receiving sign-off;
  Sales Associates for stocking and cycle counts under manager supervision
- Related Documents: SOP-009 (Loss Prevention, for inventory discrepancy patterns)

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- Three distinct parts (Receiving, Stocking, Cycle Counts) clearly labeled within Procedure
- Square for Retail referenced for inventory entry
- Cycle count frequency specified
- No assumption of warehouse, receiving dock, or dedicated receiving staff

---

## TASK-008: SOP-008 Visual Merchandising and Seasonal Reset

**ID:** TASK-008
**Description:** Produce the Visual Merchandising and Seasonal Reset SOP.
This document defines display standards and the process for resetting the floor
for seasonal, thematic, and promotional changes.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — product categories, store dimensions, store concept

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-008-Visual-Merchandising.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  Part A — Ongoing Display Standards:
  1. Display standards by product category (figures, manga, apparel, accessories,
     trading cards, media, consignment section)
  2. Cleanliness and facing standards: daily straightening expectations
  3. Signage standards: price tags, section labels, promotional signs
  4. New arrival placement: designated new arrival zone or end cap
  5. High-value item display: locked case standards (figures above a threshold)
  Part B — Seasonal and Thematic Resets:
  6. Reset triggers: anime release calendar milestones, conventions (list examples:
     Anime Matsuri, A-Kon, PAX South if local), holidays (Christmas, Valentine's Day,
     back-to-school), major franchise releases
  7. Reset planning: who plans the reset, lead time (suggest 2 weeks before event)
  8. Reset execution: floor map, product moves, signage changes
  9. Post-reset walkthrough and approval
  10. End cap rotation schedule (suggest monthly rotation)
- Responsibilities: Store Manager / Assistant Manager for planning; all staff for execution
- Related Documents: SOP-007 (for new arrival stocking that feeds displays)

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- All 7 product categories included in display standards
- Reset trigger examples include both anime-specific (release calendar, conventions)
  and general retail (holidays)
- Locked case standard mentioned for high-value figures

---

## TASK-009: SOP-009 Loss Prevention and Incident Reporting

**ID:** TASK-009
**Description:** Produce the Loss Prevention and Incident Reporting SOP.
Loss prevention for this store relies on staff awareness, camera systems, and
procedural controls — not dedicated LP staff or EAS tagging systems.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — staffing, store layout, technology
- `Business Plan/03-HR/Employee-Handbook.docx` — discipline, workplace violence, and
  reporting policies

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-009-Loss-Prevention.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  Part A — Prevention:
  1. Staff awareness and positioning: floor coverage, sight lines
  2. Greeting as deterrence: acknowledging all customers who enter
  3. High-value item controls: locked display cases for figures above a threshold
     (align with SOP-008 threshold; document figure price threshold in results.md)
  4. Camera system: awareness, what is monitored, who reviews footage
  5. Internal theft prevention: access controls, bag checks policy, two-person
     reconciliation for cash
  Part B — Response:
  6. Shoplifting response: do not physically confront; steps for observation,
     documentation, calling manager, and calling law enforcement if needed
  7. Shoplifting documentation: Incident Report Form (reference by name)
  8. Confrontation de-escalation: when a suspect becomes confrontational
  9. Internal theft investigation: who is notified (Store Manager, Owner),
     chain of custody for evidence
  Part C — Incident Reporting:
  10. What constitutes a reportable incident (theft, assault, accident, vandalism)
  11. Incident Report Form completion (reference by name; form is not produced here)
  12. Escalation path: Store Manager → Owner → law enforcement
  13. Insurance notification requirements
- Responsibilities: all staff for awareness; Key Holder and above for incident reports;
  Store Manager for law enforcement contact
- Related Documents: SOP-010 (Safety and Emergency), SOP-007 (Inventory for discrepancy
  detection), Employee Handbook (workplace violence section)

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- No assumption of dedicated LP staff or EAS systems
- Physical confrontation explicitly prohibited for staff
- Incident Report Form referenced by name
- Camera system referenced
- Internal theft and external theft procedures both present

---

## TASK-010: SOP-010 Safety and Emergency Procedures

**ID:** TASK-010
**Description:** Produce the Safety and Emergency Procedures SOP. This SOP must
align with the Workplace Violence and Safety Policy in the Employee Handbook.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — store address (2847 S Lamar Blvd, Suite 105, Austin, TX 78704)
- `Business Plan/03-HR/Employee-Handbook.docx` — Workplace Violence and Safety Policy

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-010-Safety-Emergency.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  Section A — Fire Emergency:
  1. Fire alarm response: staff roles, customer evacuation
  2. Evacuation route: primary and secondary exits (describe generically — actual
     floor plan not available; note that store-specific routes will be posted on-site)
  3. Assembly point: across the street or parking lot (reference the store's street address)
  4. Fire extinguisher location and who is trained
  5. Do not re-enter until cleared by fire department
  Section B — Severe Weather:
  6. Severe weather alert: how staff are notified (weather alert app, local news)
  7. Shelter-in-place location: interior room, away from windows (note store layout constraint)
  8. Customer and staff sheltering procedure
  Section C — Medical Emergency:
  9. Immediate response: call 911, do not move injured person unless immediate danger
  10. First aid kit location (specify: near back office or manager station; document in results.md)
  11. AED location if applicable (note: no AED assumed unless in reference data)
  12. CPR/first aid training expectation for management staff
  Section D — Active Threat:
  13. Run-Hide-Fight framework (standard CISA guidance)
  14. Lockdown procedure: lock front door, silence phones, hide, call 911 when safe
  15. Staff communication and customer communication during lockdown
  Section E — General Safety:
  16. Emergency contact list location (posted in back office)
  17. Emergency contacts: 911, Austin Police non-emergency, building management, Owner
  18. First aid kit inspection schedule
  19. Incident reporting for safety events (reference SOP-009)
- Responsibilities: all staff for awareness; Store Manager / Key Holder for emergency leadership
- Ensure alignment with Employee Handbook Workplace Violence and Safety Policy;
  use consistent language for any policy cross-references
- Related Documents: SOP-009 (Incident Reporting), Employee Handbook (Workplace Violence
  and Safety Policy)

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- All four emergency types covered (fire, severe weather, medical, active threat)
- Store address referenced in evacuation context
- First aid kit location documented in results.md
- Language consistent with Employee Handbook safety policy
- SOP-009 referenced in Related Documents

---

## TASK-011: SOP-011 Vendor Consignment and Special Product Agreements

**ID:** TASK-011
**Description:** Produce the Vendor Consignment and Special Product Agreements SOP.
This covers the intake, tracking, and payment process for locally produced consignment
items from Austin-area creators. This is a small portion of the store floor, not a
full consignment management system.

**Inputs:**
- `trail/meta/files/Otaku_Haven_Reference_Data.md` — consignment section description,
  product categories, technology (Square for Retail)

**Outputs:**
- `Business Plan/04-Operations-SOPs/SOP-011-Vendor-Consignment.docx`

**Content Requirements:**
- Cover all of the following in the Procedure section:
  Part A — Creator Application and Intake:
  1. Application process: creator submits product samples and pricing proposal to Store Manager
  2. Product acceptance criteria: anime/manga related, original artwork or licensed
     fan work compliant with IP guidelines, appropriate for all-ages store environment
  3. Quality standards: no damaged goods, professional presentation
  4. Intake agreement: Consignment Agreement form (reference by name; form not produced here)
     — agreement must specify: consignment split percentage, payment schedule, duration,
     removal terms
  5. Consignment split: document the percentage split chosen in results.md
     (suggest 60% creator / 40% store; document actual choice)
  Part B — Inventory Tracking:
  6. Entering consignment items in Square for Retail: item name, creator name, price,
     quantity
  7. Tagging: consignment items labeled with creator attribution
  8. Tracking sold vs. unsold quantities
  Part C — Sales Reporting and Payment:
  9. Reporting period: how often (suggest monthly; document in results.md)
  10. Creator payment: method (check or ACH), payment schedule relative to reporting period
  11. Sales report format: what is shared with creator (items sold, revenue, store fee)
  Part D — Product Return and Removal:
  12. Creator-initiated removal: notice period, condition of return
  13. Store-initiated removal: poor sales threshold, quality issues, end of agreement term
  14. Unsold item return: timeline and condition requirements
- Responsibilities: Store Manager for agreement approval and payments; all staff for
  intake tagging and sales processing
- Related Documents: SOP-007 (Inventory Receiving, for stocking procedures), SOP-004 (POS)

**Forward-Reference Items to Document in results.md:**
- Consignment split percentage (creator % / store %)
- Payment schedule (monthly, quarterly, etc.)
- Reporting period

**Acceptance Criteria:**
- All 7 SOP sections present in correct order
- Four parts (Application/Intake, Inventory Tracking, Sales/Payment, Return/Removal)
  clearly labeled within Procedure
- Consignment Agreement form referenced by name
- Square for Retail referenced for inventory tracking
- Consignment split percentage documented in results.md
- IP compliance and all-ages appropriateness criteria included

---

## TASK-012: Complete results.md

**ID:** TASK-012
**Description:** Complete the results.md scaffold with all required forward-reference
values, documented assumptions, and any coherence flags or deviations.

**Inputs:**
- Notes accumulated during TASK-001 through TASK-011

**Outputs:**
- `trail/runs/intent-004/run-2026-04-25-20-10-23/results.md` (completed)

**Required Sections to Complete:**
1. SOP-003 Forward References (cash handling thresholds)
2. SOP-005 Forward References (return policy values)
3. SOP-011 Forward References (consignment terms)
4. Assumptions Made During Production
5. Coherence Flags (if any conflicts detected)
6. Deviations from Tasks (if any)
7. Deliverables Produced (checklist)

**Acceptance Criteria:**
- All three forward-reference sections completed with specific values (not ranges)
- Deliverables checklist shows all 11 SOPs as complete
- Any assumptions documented with rationale
- Any coherence conflicts explicitly flagged (do not silently resolve)