Pinky AAA: the queue-peek doctrine + the owner-waiting age + the kill breadcrumb + the dance model (v1.58.0) #87
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/pinky-aaa-peek"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Pinky AAA (steers #52/#53/#54/#56, target v1.58.0) — the queue-peek doctrine clause, the owner-waiting age, the kill-reason breadcrumb, and the dance model taught. Born from the 2026-10-08 incident where all three seams fired and nothing was lost.
1 — The peek doctrine (steer #52): the brain brief gains the clause — between steps of a LONG in-turn action chain, cheaply PEEK the user steer queue and yield or answer early when the owner queued something; a long turn is not an undisturbed turn (long legitimate work stays legitimate). The affordance is first-class:
GET /api/session/<sid>/infoextends withpendingSteers+oldestSteerAgeMs(read-only; README §"For agents" documents the peek).2 — The owner-waiting age: the turn-blocking wedge state composes N + age — "⚠ turn-blocking · N steers queue · owner waiting 4m12s" — on the row chip, the row detail's info strip and the slim line's alert ladder (live-updating). The age derives purely from the OLDEST queued USER steer's send time (the queue's own ordering key); bells and system items never qualify. Compact human form (45s / 4m12s / 1h02m) = one pure function,
age_compact.3 — The kill-reason breadcrumb (steer #53): after a creator-kill the interrupt path enqueues a one-line SYSTEM breadcrumb at the FIFO HEAD of the killed session's queue — "[system] turn #N was terminated by creator at owner request, HH:MM UTC — queued steers follow." — via the EXISTING queue machinery (a steer-shaped sweeper entry whose send-ms AND queued_at both sit one tick below the queue head, so BOTH delivery lanes sort it first without special-casing; the "system": true marker keeps it out of every owner-facing count, cap and age). Same authoritative-dismissal discipline as any steer, no dismiss chip, SYSTEM class in transcripts (message_kind prefix seam), and the audit journal links its queue id to the kill entry. A failed queueing never rolls back the kill.
4 — The dance model (steer #54/#56): the brain brief opens with THE DANCE — two tracks by design (FOREGROUND: the owner handoff; BACKGROUND: the pinky brotherhood pogoeing through the night) absorbing the old topology + bell-protocol points as tracks 1–2, the three SEAMS named, and the recursion rule verbatim (🪆 sub-brains). The README carries the full model as §"How brains and owners dance" with the incident as the proof story and the owner's flavor line verbatim.
Validation: suite 789 green (30 new: brief content incl. dance/peek/recursion, README gates, info peek fields, wedge age matrix + system exclusion + compact form, breadcrumb FIFO-head both lane keys + journal link + classing + fail-open); fixture E2E rig 19/19 (real observatory + real rig dispatcher process killed via the interrupt path: wedge forms with correct N + growing age, row chip + slim line render it via CDP, breadcrumb at the FIFO head, journal link, transcript SYSTEM class, system never counted as owner steer); Super-Linter station recipe green (BASH/BASH_EXEC/MARKDOWN/PYTHON_PYLINT/PYTHON_RUFF/YAML).