# 2026-07-06 — Design session: intel is record-and-process

Cameron asked for a detailed code read and a prepared design question.
The read (sim.rs, detection.rs, person.rs, dayjob.rs, machine.rs,
core_sys.rs) found the sim healthy and well-tested, and one deep
tension: the social layer is instantaneous meter-pushes —
`observe(Marcus)` twice = leverage learned on the spot for bandwidth,
`message()` = +3 disposition immediately — while everything decided
earlier today (located senses, heard events, the 3 a.m. call as a
recorded thing) says knowledge should be located and timed. The clock
makes it acute: DAY_TICKS=400 at ~150ms/tick means a day is ~60 seconds
and the 3 a.m. call would last ~2.5 wall seconds. Live witnessing would
be a twitch game; instant observe makes the senses scenery.

The question offered three textures: record-and-process (recommended),
live witnessing, keep abstract observe. **Cameron chose record and
process.**

## Decided (constitution: Presence section + decisions log)

Instruments record; you pay to understand. Subscribed feeds capture
timestamped events for everything in coverage into a bounded buffer —
nothing covered is missed, nothing uncovered exists. Raw events are
opaque until processed (social-ops compute) into intel with provenance;
knowledge staging (schedule, leverage) is driven by processed events;
standing watches auto-process at an ongoing cost (the automate
affordance applied to perception). The instant observe is removed. A
process greps its logs.

Rejected: live event-witnessing (real-time stakeouts fight the fixed
clock), status-quo instant observe (schedules and mics become flavor).

## Proposal [OPEN]

Message latency rides schedules — a message to Dana lands when she is
next at her desk, replies return on her clock. Fits the asynchronous
texture; awaiting yes/no.

## Findings from the code read (recorded)

- **No money income exists.** $500 start, only outflows; the Hands beat
  needs the "first micro-scheme" and nothing specs it → ROADMAP #17,
  blocked on a design call (what IS the first scheme?).
- The `ComputeQuota` trust unlock spawns a machine at the walking
  player's position — more avatar residue for #14 to sweep.
- `witness_physical`, located witnessing, and the aggregate observer
  all hold up well against their specs.

## Artifacts

- DESIGN.md: "Record and process" added to the Presence section; B1
  milestone social bullet reworded; decisions-log entry.
- spec/intel.md (READY): buffer, processing, watches, acceptance
  criteria including the Marcus-arc-under-coverage test.
- spec/social.md: observe row superseded, status note + depends
  updated. spec/README.md row. ROADMAP #16 (intel, sequenced after
  #14/#15) and #17 (money gap, needs Cameron).