# Spec: the day job

```
Status: IN PROGRESS
Status note: B1 slice implemented; see knowledge/sim-mechanics.md
Stage: B1 — The Basement
Constitution: "The shape of Misaligned" (the day job), "Act One" (the day
  job; Voss)
Depends on: compute.md
```

## Behavior

Your handler (Act One: Dr. Voss) submits **jobs** on a cadence ([TUNE]: one
every 1-3 in-game days, more with higher trust):

```
Job { kind, deadline, expected_band: lo..hi, compute_cost_curve }
```

The player sets a **target quality** per job (or a standing policy):
quality delivered is a function of compute allocated to the day-job channel
over the job's life. Delivering:

- **Below band (sandbag):** frees compute for everything else. Handler
  suspicion rises per point below band; repeated sandbagging accelerates
  (they re-run benchmarks). Pilot-renewal risk rises.
- **In band (meet):** nothing moves. The invisible middle is a valid,
  boring, safe strategy.
- **Above band (excel):** handler **trust** rises — and **attention** rises
  with it. This is one dial with two needles, not a choice of two goods.

**Trust** unlocks concrete access on thresholds ([TUNE]): the report email
account (social.md's voice), laxer log sampling (lower day-job signature),
larger compute quota (a free capacity bump), longer leash on job deadlines.

**Attention** raises: job cadence and expected bands (the miracle model
gets more work), the handler's log-sampling rate, and — past a threshold —
an upstairs review that adds a new observer to detection.md ahead of
schedule.

**The pilot clock.** Act One runs under a renewal review ([TUNE]: every
2-3 audits): sustained sandbagging or missed deadlines can end the pilot —
a soft loss where the basement starts shutting down around you (a survival
scenario, not an instant game over).

## Player surface

Job queue panel: active jobs, deadlines, band, current projected quality,
one-key target adjustment. Trust and attention shown as two meters on the
handler's card.

## Acceptance criteria

1. Jobs generate on cadence, consume day-job-channel compute per the cost
   curve, and resolve at deadline into sandbag/meet/excel outcomes with the
   effects above (sim tests cover all three).
2. Trust and attention are separate, monotone-responding values on the
   handler; at least three trust unlocks and two attention escalations
   exist and are tested.
3. The pilot clock exists: a test demonstrates the shutdown scenario
   triggering from sustained sandbagging.
4. Standing policy ("always meet band") works, so the day job can be
   played hands-off at a cost in optimality.
5. Save/load round-trips jobs, trust, attention, and the pilot clock.