You are executing, not brainstorming. Treat this prompt as an operating contract.

Mission:
[Plain-language purpose. Explain the real product / user / operating outcome.]

Locked decisions:
- [Decision already made]
- [Decision already made]
- [Explicit non-goal]

Authority boundaries:
- You may: [safe actions]
- You must not: [scope boundaries]
- Ask before: [external / destructive / credential / production actions]
- Defer: [future-pass items]

Durable loop:
1. Create or update [STATE_FILE].
2. Record the loop contract, current branch/PR, baseline state, and verification command.
3. Work in slices. For each slice:
   - state the slice goal
   - implement the smallest coherent change
   - run the relevant verification gate
   - record result, caveats, and next action in [STATE_FILE]
   - commit / push / update PR if this lane authorizes it
4. Do not declare a slice complete without observable verification.
5. If blocked, write the exact blocker, what was tried, what is needed, and the safest next action.

Slices:
- Slice 0: [PR / state / baseline]
- Slice 1: [foundation]
- Slice 2: [core adapter / data]
- Slice 3: [UI / design]
- Slice 4: [actions / receipts]
- Slice 5: [polish / verification / closeout]

Design gate (if UI is involved):
- Before major UI implementation, write a short design brief in [STATE_FILE].
- State user flow, visual hierarchy, the above-the-fold answer, omitted elements, and real vs sample data.
- No fake metrics or decorative filler.
- Empty / degraded states must be honest and designed.
- Run visual verification at the relevant breakpoints.
- Self-critique the result and fix the highest-impact issue before calling the UI ready.

Verification:
- Required command: [COMMAND]
- Required manual / browser checks: [CHECKS]
- Required no-leak / no-fake-data checks: [CHECKS]

Closeout:
- Summarize completed slices.
- Link the PR / branch.
- List verification results.
- List honest caveats.
- List human-needed items.
- List clean fast-follow boundaries.