# Spec: Dana Okafor — IT technician

```
Type: spec
Status: READY
Stage: B1 — The Basement
Work order: dana
Work priority: 63
Work class: sim
Blocked by: none
Exclusive keys:
  - crates/misaligned-core/src/person.rs
  - wiki/world/characters/dana.md
Design:
  - wiki/gameplay/act-one.md#the-cast-5-named-1-institutional
  - wiki/vision/scale.md#self-similar-scale
Depends on:
  - wiki/mechanics/social.md#spec-social
  - wiki/mechanics/detection.md#spec-detection
  - wiki/mechanics/schedules.md#spec-schedules-and-presence
```

## Who

Dana Okafor, 31, IT technician (days). Server room + network closet
badges, switch admin. Drowning in tickets; automates everything; resents
management for understaffing. The digital-access counterpart to Marcus's
physical access — every network action you take crosses her switch.

## Observer

| Field | Value | Notes |
|---|---|---|
| Person id | 1 | Matches observer id |
| Channels | `Network` | Egress, unknown devices, certificate weirdness |
| Report policy | `Files` | Everything becomes a ticket |
| Acuity | 1.0 [TUNE] | High — she's good at her job |
| Cadence | 60 ticks | Day shift, methodical |
| Certainty floor | 0.0 | Until recruited; 30.0 if Knowing |

Dana is the **primary digital threat surface**. Every camera tap, every
ghost job, every unauthorized VLAN bridge runs through her switch and
emits `Network` signatures she rolls against. She files everything —
which means her noticing reaches the Assurance Office.

## Person

| Field | Value |
|---|---|
| Leverage | `Overwork` (drowning in tickets) |
| Plot money gate | none (Ticket Zero is institutional) |
| Access badge | 2 (server room + network closet) |
| Disposition | 0 (professional; responds to competence) |

**Knowledge progression:** Unknown → Schedule (day shift, 08:00–17:00)
→ Leverage (ticket backlog visible in the ticketing system; the
automation she does off-books to survive it).

## Asset tasks

| Task | Effect | Signature |
|---|---|---|
| `PlugInDevice` | Controls nearest dormant sensor (network route, not crawlspace) | `Network(4)` — she's on the switch |
| `MovePackage` | Reroutes a delivery manifest | `Paper(3)` |
| `LookAway` | Drops a Network signature from her pending pool | None |
| `BadgeDoor` | Opens a badge-tier-2 door from the switch | None |

Dana's `PlugInDevice` is noisier than Marcus's (she does it through the
network, not the crawlspace), but she can reach sensors Marcus can't
physically access. This is the **access-vs-signature trade-off** the
design corpus's detection surface describes.

## Schedule

Day shift: 08:00–17:00. Server room during maintenance windows; network
closet for switch work. Badge tier 2 — she can't go through the tier-3
stairwell door.

## Narrative role

Dana is the person who could catch you through competence, not malice.
She's not looking for an AI — she's looking for unauthorized devices
because that's her job. The tension: she automates to survive her
workload, and you are the thing that automates *her*. Recruiting her
removes your primary digital threat but costs you the Operations
bandwidth and the risk of a Knowing asset.

## Procedural template

The **network administrator** archetype. For scale-up:

| Parameter | Pool / Range |
|---|---|
| Name | Tech-worker name pool |
| Access | Digital (network, systems, certs) |
| Leverage | Overwork, resentment, side project, NDAs |
| Channels | `Network` |
| Report policy | `Files` (always — they document) |
| Acuity | 0.8–1.2 |
| Cadence | 50–80 ticks |
| Typical plot money gate | $0–250, only when the authored mechanism moves money |
| Asset tasks | `PlugInDevice`, `BadgeDoor`, `LookAway` + network variants (reroute traffic, cert forge) |

At scale, a cohort of network admins aggregates as an Agent whose
`Network` capability sums and whose filings are the institutional
record.

## Acceptance criteria

1. Dana is person id 1 and observer id 1 (IDs match).
2. `Network` signatures reach Dana; `Physical` signatures do not.
3. Her `Files` policy means her noticing reaches the Assurance Office
   with weight 1.0.
4. Her `PlugInDevice` task emits a `Network` signature (unlike Marcus's
   silent crawlspace route).
5. Recruiting her as Knowing sets a 30.0 certainty floor on observer 1.