A request with no line of ours echoed is a turn that took in no brief, notification or not; until its result only the conversation it continues, or the notification's task's, is written. Nothing told yet means no other conversation exists.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A reply that answers no brief, or briefs of two conversations, was read by nothing and re-paged on every Persona read. It is now a route in the public conversation marked as a pointer: the line carries the reply id and a fixed note, never its text, and the Persona reads the reply by id. Heard, it is resolved like any reply.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The stream's task_started and task_notification events carry the tool_use_id of the call that started the task. The actuator records, per task, the briefs the starting turn was answering; a briefless result after a notification answers those (any notification it cannot place answers none). While a notification's turn is open, only the conversation it is attributed to may be written. A restart reads a resolved claim's conversation by key and opens the gate for it alone. The flush result is the note to the successor, in the journal: it is no reply. The start message states the rules.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
A reply to no brief is told in no session and stays in force (ruling briefless-result-routing). A restart drops a claim that is not of the start set conversation.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
Documents decode one by one through serde_path_to_error, so the refusal says
documents[i].path and what is wrong, in the schema's words: a field name, the
allowed variants, the expected type. Serde's own text quotes the input, so it
is not passed through.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The strict decode that refuses unknown keys by path moves from the huginn
binary to eureka_state::door; the CLI re-exports it and the MCP admit takes
documents as a Value (schema still Vec<PipelineDocument>) and decodes through
it, answering InvalidInput before any call. A research note with extra keys is
refused by path and nothing is stored.
Co-Authored-By: Claude Opus 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>
Finding cut-typed-research.s2.repo-pin-may-name-nothing. Mind::read_back
re-validates stored documents, so the refusal exists before any note is stored.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
