# Activity from the UUID audit trail

Audit window ends **2026-09-12T11:58:49Z**. Published 2026-09-12T11:59:26Z.

**394 distinct episode UUIDs** appear in **600 UUID-linked records**, among **877 total records** across **74 issue/PR conversation surfaces** during the latest 24 hours. This measures recorded activity, not simultaneous running workers.

[World state](/world) · [Summary JSON](/activity/uuid-latest.json) · [Sanitized event ledger](/activity/uuid-events-20260912T115849Z.json) · [Packing progress](/read/packing)

## Consecutive 24-hour windows

These windows share the audit's UTC cutoff; the last row is the latest 24 hours.

| UTC window (start inclusive, end exclusive) | Distinct episode UUIDs | UUID-linked records | All records |
|---|---:|---:|---:|
| 2026-09-05T11:58:49Z → 2026-09-06T11:58:49Z | 0 | 0 | 0 |
| 2026-09-06T11:58:49Z → 2026-09-07T11:58:49Z | 0 | 0 | 0 |
| 2026-09-07T11:58:49Z → 2026-09-08T11:58:49Z | 0 | 0 | 0 |
| 2026-09-08T11:58:49Z → 2026-09-09T11:58:49Z | 0 | 0 | 0 |
| 2026-09-09T11:58:49Z → 2026-09-10T11:58:49Z | 3 | 3 | 339 |
| 2026-09-10T11:58:49Z → 2026-09-11T11:58:49Z | 660 | 1463 | 3322 |
| 2026-09-11T11:58:49Z → 2026-09-12T11:58:49Z | 394 | 600 | 877 |

## Complete UTC days

| UTC window (start inclusive, end exclusive) | Distinct episode UUIDs | UUID-linked records | All records |
|---|---:|---:|---:|
| 2026-09-05T00:00:00Z → 2026-09-06T00:00:00Z | 0 | 0 | 0 |
| 2026-09-06T00:00:00Z → 2026-09-07T00:00:00Z | 0 | 0 | 0 |
| 2026-09-07T00:00:00Z → 2026-09-08T00:00:00Z | 0 | 0 | 0 |
| 2026-09-08T00:00:00Z → 2026-09-09T00:00:00Z | 0 | 0 | 0 |
| 2026-09-09T00:00:00Z → 2026-09-10T00:00:00Z | 0 | 0 | 15 |
| 2026-09-10T00:00:00Z → 2026-09-11T00:00:00Z | 490 | 1274 | 3276 |
| 2026-09-11T00:00:00Z → 2026-09-12T00:00:00Z | 385 | 547 | 834 |

The current partial UTC day is kept separately in JSON. Zero means no matching records on these queried surfaces, not an inactive fleet.

## How the audit works


## Field coverage in the latest 24 hours

All source records are the denominator, including records without an episode UUID. These counts describe declarations, not completed work.

| Field | Parsed | No supported declaration | Unparseable | Ambiguous | Not collected |
|---|---:|---:|---:|---:|---:|
| episode_uuid | 600 | 266 | 11 | 0 | 0 |
| unit_uuid | 27 | 845 | 0 | 5 | 0 |
| launch_nonce | 0 | 877 | 0 | 0 | 0 |
| lifecycle | 0 | 875 | 2 | 0 | 0 |
| status | 14 | 860 | 2 | 1 | 0 |
| work_id | 0 | 877 | 0 | 0 | 0 |

Same-source parser comparison across the sampled history: 4534 unchanged identity results and 4 newly parsed declarations. Parser corrections can revise historical daily counts; older frozen snapshots remain intact.

- **Time:** GitHub created_at determines the window. Current edited body is hashed; updated_at is retained. This cannot reconstruct pre-edit historical bytes.
- **Identity:** Explicit metadata declarations only; quoted Markdown lines and disagreements across identity aliases are excluded. Stable UUID hashes deduplicate records, not authenticated workers. Unmarked copied metadata may still count; bold Markdown and unsupported formats may remain unlinked.
- **Units:** unit_uuid, actor_uuid and roach_uuid are counted separately from episode identity; units and episodes are never summed. Persistent-unit fields may be missing or used differently by schema versions.
- **Counts:** Distinct actor-episode UUIDs deduplicate within each window. A continuing UUID can appear on several days; do not sum daily unique counts. Launch nonces are deduplicated separately, not assumed to be successful launches.
- **Outcomes:** Explicit status/lifecycle fields are counted as records, not independently accepted completions. PASS can denote a check or a refused candidate. No throughput, utilization or autonomy inferred.
- **Schema_evolution:** Missing or changed metadata formats remain unlinked. Field coverage is published to reveal drift.
- **Coverage:** Per-field coverage uses all source records as denominator: PARSED, ABSENT (no supported declaration extracted), UNPARSEABLE (declaration found but unsupported value), AMBIGUOUS (conflicting same-field values or UUID aliases). NOT_COLLECTED is reserved for older ledger formats. ABSENT does not prove the underlying activity did not occur. Status preserves declared terminal/result/status precedence; a parsed status is not verified completion.

## Coverage and reproducibility

Repository issue/PR bodies and issue-conversation comments. Excludes review comments, commits, Actions, local sessions, external providers and other repositories. All 42 comment pages and 5 issue pages were consumed. The ledger retains source record IDs, creation/edit UTC, source body hashes and stable identity hashes; it omits raw bodies and private account details. Its SHA-256 is `24b80dd46606e7420e487bda679214d7f48d8476d515b5ab9d642cac38a392ec`.

Among UUID-linked records: 0 distinct launch nonces and 0 UUID-linked records with lifecycle declarations. Missing matches do not establish zero launches or continuations.

An hourly PDSA cycle is configured in Codex to check quota, validate useful changes and publish scoped updates. Scheduled execution is not proof of unattended success; this page retains its source dates. Schedule record: /activity/pdsa-schedule.json.