# P1 Content Expansion - Stray Signal Bureau

## Content Container

```yaml
content_container: case_ledger_shift
why_this_container: The Core loop is a social-information desk, so P1 extends it with visitor families, bureau tools, and a five-minute case ledger.
recent_container_delta: Not a phase/order/surge ladder. Each case family changes whether the player should Listen, Scan, or spend Tea Signal / Alias Stamp / Mute Lantern first.
```

## Core Fun Preserved

- Player still resolves disguised outsiders through Listen, Scan, Shelter, Cover, and Route.
- Trust still opens safer responses.
- Scan still reveals hidden need while raising patrol alert.
- Gentle social stakes remain protection, exposure, or regret rather than combat.

## P1-A 30 Second Slice

The first case family teaches an immediately visible choice relation:

1. Tea Signal costs time but opens Shelter while lowering patrol exposure.
2. Scan reveals certainty but raises alert.
3. A correct response resolves the case and records the cause.

## P1-B Five Minute Runtime Slice

Implemented files:

- `DATA/p1_content.json`
- `DATA/p1_content.js`
- `p1-game.js`
- `play-p1-5min.html`

The playable slice lasts 300 seconds and requires 24 case resolutions. The verified route must use P1 tools; a plain Core-like route remains playable but scores lower because it ignores the family-tool relation.

## P1-C 30 Minute Matrix

`play-p1-30min.html` and `DATA/p1_content.json` expose the 30-minute matrix. Only the first two rows are represented in the current five-minute runtime slice. Later rows are blueprint rows and must not be treated as implemented runtime.

## NotMath

This is not a unique-solution puzzle or autosolve board. The same visitor need can be approached through trust, scan, or a P1 tool, and the tradeoff is time versus alert versus preparation.

## NotSame

Recent C/B projects used route manifests, workshop shift contracts, and order ladders. This P1 uses a social case ledger with case families and desk tools. New DATA structures include `case_families`, `tools`, `choice_deltas`, and `p1_matrix_30min_blueprint`.

## Evidence Plan

P1 certification must use the current P1 digest and these CheckResults:

- `browser.p1_smoke`
- `runtime.p1_content`
- `regression.core`
- `content.choice_delta`

Dry-run metrics before final digest binding: skilled `12658` over plain `2629`, noisy `854`, random `144`, and idle `0`; browser smoke reported 0 runtime errors.