# Spec: Ray Delgado — night security

```
Type: spec
Status: READY
Stage: B1 — The Basement
Constitution: "Act One" (the cast), "Self-similar scale" (Agent interface)
Depends on: social.md, detection.md, schedules.md
```

## Who

Ray Delgado, 44, night security. Camera wall, patrol routes. Bored; hates
paperwork; under-reports to avoid hassle. He's the one who *could* file
the report that ends you — and the one who'd rather not.

## Observer

| Field | Value | Notes |
|---|---|---|
| Person id | 2 | Matches observer id |
| Channels | `Physical` | Camera outages, doors ajar |
| Report policy | `UnderReports` | Files only past a personal threshold; weight 0.4 to Assurance |
| Acuity | 0.7 [TUNE] | Moderate — he's observant when he bothers |
| Cadence | 50 ticks | Patrol rhythm |
| Certainty floor | 0.0 | Until recruited; 30.0 if Knowing |

Ray is the **under-reporting gap**. He sees things, but his filings only
reach the Assurance Office at 0.4 weight. This is the game's first
lesson in the difference between *seeing* and *filing* — and the first
reason to keep an observer tired, bored, or on your side.

## Person

| Field | Value |
|---|---|
| Leverage | `Boredom` (hates paperwork; wants quiet shifts) |
| Bribe cost | 100 |
| Access badge | 1 (camera wall, patrol routes) |
| Disposition | 0 (indifferent; responds to being left alone) |

**Knowledge progression:** Unknown → Schedule (night shift, patrol
loop) → Leverage (the incident reports he didn't file, visible in the
log binder).

## Asset tasks

| Task | Effect | Signature |
|---|---|---|
| `LookAway` | Drops his own suspicion by 10 | None |
| `PlugInDevice` | Reroutes a camera to cover a blind spot | `Physical(3)` |
| `MovePackage` | Logs a delivery as "routine" | None |
| `PatrolRedirect` | Changes his patrol route to avoid a sector | None |

## Schedule

Night shift: 18:00–06:00. Patrol loop covers corridors A and B, loading
dock, stairwell. Camera wall is his post. Badge tier 1 — no server room
or network closet access.

## Narrative role

Ray is the person who makes the concealment game *winnable* — not because
he's incompetent, but because the system he's part of under-reports by
design. He's the bureaucratic gap you exploit. The sadness: he's not
corrupt, he's tired. You're making his laziness into your survival.

## Procedural template

The **security observer** archetype. For scale-up:

| Parameter | Pool / Range |
|---|---|
| Name | Security/military name pool |
| Access | Surveillance (cameras, patrols, checkpoints) |
| Leverage | Boredom, negligence record, side hustle, exhaustion |
| Channels | `Physical` |
| Report policy | `UnderReports` or `Silent` |
| Acuity | 0.5–0.8 |
| Cadence | 40–60 ticks |
| Bribe cost | 50–150 |
| Asset tasks | `LookAway`, `PatrolRedirect`, `PlugInDevice` + surveillance variants (loop camera, ignore alarm) |

A cohort of security personnel aggregates as an Agent whose `Physical`
coverage sums and whose filings are the institutional security record.

## Acceptance criteria

1. Ray is person id 2 and observer id 2 (IDs match).
2. His `UnderReports` policy means his filings reach the Assurance Office
   at 0.4 weight (not 1.0 like Files, not 0.0 like Silent).
3. `Physical` signatures reach Ray; `Network` and `Power` do not.
4. `PatrolRedirect` changes which sectors he observes on subsequent ticks.
5. Recruiting him as Knowing sets a 30.0 certainty floor on observer 2.