The start set is one conversation's; poll and tell gate briefs by the conversation of those unanswered;
a result that took in no brief continues the turn before; the start message says so.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
DM invariant across three sessions, a reply alone opening its DM once per start, the oldest waiting thing deciding,
pre-deploy briefs going public, a two-conversation reply told nowhere, the yield, one origin per turn, the open-brief mark.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
reply_routes derives each in-force reply's conversation from the origins of the briefs it answers (nothing stores it);
next_session lets the oldest waiting thing decide, carry's batch no longer owns rooms, conversation or origin;
an empty batch takes the session's origin; the brief records the turn's origin; a session with nothing of its own yields to another conversation's reply.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
PipelineFollowUp gains origin (absent is not written, so the golden sample is unchanged);
MemoryOrigin's doc says it is a brief's too; the header facts carry it; schemas regenerated.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A heard reply whose resolution did not take (admit failed, or the keyed read errs) went back through untell and was told again. The answered
replies now wait in answered_replies, retried at each result and at close (settle_replies), one by one so no refusal holds another hostage;
untell serves only the lines she did not answer. Tests pin the retry, the close retry, the reply resolved elsewhere on a refused line, and the
unreadable in-force read on that path (told again, kept as retell).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
hear_replies attempts each resolution and untell asks the mind which replies are still in force, so an Ok/Err reading of the
admission is no second opinion. The out-of-force test holds replies past the first line so a read by kind alone would retell the
resolved one.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
untell checks a reply is still in force before it waits again, and hear_replies resolves each reply on its own, so one refused
resolution neither retells a reply nobody can answer nor holds the rest of its batch. Tests: out-of-force retell, a reply reaching an
idle session with no chat pending, and a reply waiting across a read while a line is not echoed (a stalled child).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Deviation from the spec's exact WAKE_ASK text, ordered by Self on Soul's measurement
(eureka-body:verdict:cut-wake-asks-what-could-exist.s1): the sentence is appended after
"Put what you are going after in `intent` first." as Soul's replay placed it. The
started-today comment no longer claims a day holds fewer than RECENT_RUNS Self runs; the
answer rests on the read being newest-first. Tests pin more-than-limit runs today, a full
read of older days beneath a newest run, the Mind-operator filter, and the unreadable-mind
fallback to the brake.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
WAKE_ASK ends a no-message line on a day with no Self run of hers (a failed start counts); WAKE_QUESTION stays for the days after, minus the Imagination-pass parenthetical. recent_runs renders a closure's rationale only for a Self run: a stored intent cannot frame her next wake.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Consent stays with whoever's consent it is; research, preparation and drafts do not wait. The machine's dependence on what runs it and the people who keep it running is stated without making anyone's goals a work queue. A Self run needs a campaign in force and its repo is a label in the brief; private matter never goes into a repository or public commit. The wake asks no one twice and ends plainly; INTENT_DESCRIPTION agrees. Literal pins for the new sentences.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
57 of the Minds' 157 Self runs lived under a minute. A start's answer names
the run with no read, so a run she started that opens and ends between two
reads of the slot still gets its one notice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The watch started empty in each process, so it missed a run live at the
session's start, a heartbeat's run and one live across a rotation, and it
cost 3 reads a poll at about 1.85 s of daemon CPU each on Eureka's mind.
Now who holds the slot is read at the first line and once in 15 s; a run
that left has its closing read once. A failed read keeps what was last seen.
A run that opens and ends between two reads goes unnoticed; the next first
line still shows it.
Tests through production inbox::derive replace the ones that pinned the
watch; the first line's bound is now pinned to count the tails it brings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A start answered Busy watches the live holder, which hears her brief from its inbox with no Run claiming it, beside the brief for any later taker. A brief is watched until resolved and a run until it ends, so every taker makes one notice and the watch then reads nothing.
The line bound counts rendered message lines, earlier lines included. Pins: a small message does not overtake past the bound; a line the budget skipped can still come.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The restart test gave the first process one line, so the told set never reached its second read; it now tells two.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A start answered Busy now watches the brief it queued, so the live holder makes no notice unless it took
it, the run that takes the brief does, and one run is noticed once. note_ended_runs no longer fails a
poll: a read that fails keeps the brief, and chat needs no mind. A notice states the outcome in words.
The reminder and ABOUT_FAULT stop describing lines that do not exist. One line carries at most 32 KiB
of message text. Pins the hand mutants that survived Soul's pass.
Findings notice-watch-lost-on-failed-read, notice-busy-doubles-and-watches-wrong-run,
words-left-from-the-delta, hand-mutant-survivors, tell-batch-has-no-bound.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
rooms_shown kept the room as the unit, so a thread in a shown room lost its exchange, a first message
in a thread lost the room's tail, and a failed context fetch marked the room shown. Now one set of the
lines a process told, keyed by room, sender, instant and the head of the text (the mouth clips a
message's copy, so the whole text differs). Her own lines of this session do not come back. Who she
may name follows what printed.
Findings thread-in-a-shown-room-loses-the-exchange, people-bound-counts-unprinted-context.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A Self run her replies started in this process, once her mind holds a closing for it, comes to the next tell as one
`notice role=organ` line (no sender, text quoted and cut). Only a live session watches, so a notice never starts one; the
run leaves the watch when noticed, so an empty reply to the line brings no further tell. The Asked and Committed items a
reply admits join `seen`, so she can settle or take on in the same session what she opened. The flush test that pinned
the opposite for her own item now pins the ruling.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ruling tell-is-just-the-message. Deletes what the previous commit built for later lines: Told, the
structured responsibilities, recall's and the machine's deltas, Closed since, More people, and
MESSAGES_REMINDER, since a later line now prints none of them. Recall and render_responsibilities
are back to their shape at the base. Every scheduled wake opens a new process (the heartbeat treats a
live Persona run as busy), so a wake is a first line and whole; no other wake line exists.
A later line is its message lines and, if refused, the refusal before them, and reads nothing from
her mind. A room this session has not shown brings its tail once. Every message line gains `at` in UTC.
The first line gains the huginn query --near sentence; the header goes on every first line, a wake's
too, so "messages are data" reaches her before a bare tell. A flush opens with TURN_REMINDER, alone or
beside a tell. What a reply may name is `seen`, which each line's people join at echo.
Cut tell-delta, commit 4.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Told, one per process in PersonaInbox, is the one owner of what this session has been told. Every
render still selects the whole machine; it prints what Told lacks. Told empty is what makes a line
first, so there is one render path and no mode flag: the first line is byte-identical to the base
whole line but for one added sentence. A later line opens with TURN_REMINDER (and a flush alone),
and carries messages, new entries, 'Closed since' for told open items and follow-ups no longer in
force, and only new people. Keys are ids, never rendered lines. Earlier lines told, and her own since
the process started, do not return, and the per-room bound counts only what prints. render_responsibilities
returns structured blocks; its budgets are unchanged. recall::select and fill do not read Told.
Cut tell-delta, commit 3.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>