A chat channel answering every message no longer starts Strata with
--parallel 2: on the 16 GB card that read prompts about three times
slower (2026-11-16, answers took 10-20 s). Chat and voice answers now
take turns at Strata. response.policy defaults to latest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Playback tells the worker how much of each request was played (tts_played); the worker keeps a
spoken answer's recording only that far (an answer stopped mid-way no longer keeps its unheard
rest, and is marked stopped); nothing played or never reported: no file.
- Old recording day folders are also removed with the first recording of each new day.
- response.interrupt off, latest: a request whose final comes after a newer one's is replaced
instead of replacing it.
- botBrowser presses play on a page's paused main player also after open, not only after a click.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Alone with Jarvis, whatever the speaker says is answered without asking the judge. With others
present the judge is told how many people are in the channel and how many may call Jarvis: with
one other person most of what the speaker says counts as said to Jarvis (unclear is yes); with
more, or not known, the question is the group one it was before. Live 2026-11-16: alone in the
channel, questions without the wake word got no answer because the judge assumed a group.
Eval (qwen3:8b, pair cases): 3/7 before, 6/7 after; group cases unchanged.
Also: the protocol test fixture's brain takes the trace argument (the test failed since traces).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 로그 screen: "보이는 글 txt로 저장" (logs_save_text), a 대화 view that saves the days'
conversation with every trace in full (history_export), and a 목소리 view with the
voice.record switch and the days' recordings as a zip with an index (voice_export).
- Voice worker: with JARVIS_RECORDINGS_DIR (voice.record, off by default) each final and each
spoken answer is kept as a WAV with an index line; day folders older than 7 days removed.
- response.interrupt (default on): off, latest/important finish the running answer first.
- Bot browser: Chrome lets pages start video and sound; botBrowser reports each page's media
state, waits for a player to start after open/click, and presses play on a video page a click
led to when its player stayed paused (live: a clicked YouTube video stayed paused).
- webSearch reads `query` when `search_query` is missing (live: both searches of an answer failed).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A partial transcript that call detection already reads as a request is sent
to the worker as prepare, so the intent judge runs while the speaker talks.
The live round trip now times the earcon and the answer's own sound apart.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A short two-tone chime, made in code, plays right before each voice answer
starts and at once for a wake word said alone while Jarvis is free; the
question that joins it gets no second one. call.earcon turns it off.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A wake word said alone waited without a time limit once the speaker's
next utterance started. If the worker connection ended meanwhile, that
final never came and the restarted worker's utterances (numbered from 1
again) were joined to it, so a later sentence without a wake word was
answered. The core now reports WorkerLost; the conversation drops
waiting wake words and forgets utterances in progress then and on leave.
An utterance in progress is tracked until its own final arrives instead
of by comparing utterance numbers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pause after the name ("자비스, ... 지금 몇 시야?") is longer than the
worker's 300 ms end silence, so the wake word ended its own utterance:
Jarvis answered the bare name and ignored the question that followed (no
wake word). Found on real Discord. A voice utterance that is only a wake
word is now joined to the same speaker's next final when that utterance
is running or starts within call.followUpMs (default 1500); otherwise the
wake word alone is the request after that time. Stops drop it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A person's reply stopped counting as "unanswered" as soon as the worker sent
reply_text, so a delete question that could not be spoken (no TTS, a failed
or stopped speech) or that the app could not post still let the next
"응, 지워" confirm the delete.
- Worker: an answer reaches the person on a tts_done neither failed nor
cancelled (spoken answers), on the app's reply_delivered ok (chat
answers), or at reply_text (unspoken voice answers). tts_unavailable, a
failed or cancelled tts_done, reply_delivered ok=false, no report within
30 s and the session ending all mean it never did: a turn number is
skipped, so the delete asked in it lapses. A reply sent before the
previous answer reached them is still not their next turn.
- App: a chat answer reports reply_delivered with whether Discord took the
post; a late, failed or empty answer reports it was not posted.
- Tests: no TTS, a failed speech, a chat post the app reports failed, and
no report at all do not delete; a spoken and a posted question do.
Conversation and worker client tests for the report.
- Specs: voice_worker.spec.md (reply_delivered, when an answer reaches the
person), discord_core.spec.md, conversation.spec.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The voice and chat lanes let a person's voice reply start while their chat
reply was still running. The chat delete consent counts "the very next
message" by turn number, so a message that started before the delete was
asked could pass as the confirmation, and the person's dialogue memory
was updated out of order.
- A reply takes its asker's lock, then its lane's: one person's replies
stay one at a time in the order asked, different people's voice and
chat answers still overlap, and a reply waiting for its asker holds no
lane. Test: a person's voice question starts only after their chat
answer.
- Specs and roadmap: the lanes are per person; the roadmap no longer says
voice answers wait behind chat answers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The voice worker writes voice and chat replies in separate lanes (one
of each at a time), so a chat answer being written never holds up a
voice answer. Tests: a voice reply finishes while a chat reply is still
running; replies of one kind stay one at a time.
- A chat answer arriving 5 minutes or more after it was asked is not
posted, checked when it arrives.
- Specs: the lanes, and that Strata needs --parallel 2 for both lanes'
LLM calls to run at once until the app starts Strata itself (M5).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- chatChannels[].answer: wakeWord (default) or everything. Chat uses
call.chatWakeWords (else the voice wake words) with the shared
designated-people switches.
- The brain's answer (reply via chat, not spoken) is posted as a Discord
reply to the message, pinging nobody; failed or empty answers post
nothing. Bots, channels with sending off and stops are not answered.
- Chat runs beside the voice conversation and never takes its turn.
- Core: send_chat_reply, chat_answer and the ReplyText event; the worker
client's reply takes via.
- Specs (conversation, discord core) and the roadmap updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A voice stop also voids pending "addressed" questions, so a yes that
arrives afterwards starts nothing.
- The core sends Stopped before the SpeakEnds of what stop() or the end
of a session cancelled; the conversation drops its queue on it, so the
slash command's stop no longer starts the next waiting request.
- An addressed answer after its 5 s timeout counts as no even when it is
handled before the timer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- conversation.rs: the loop between the core's events and the rest.
Finals go through call detection and the response policy; answers are
asked of the brain and spoken from the app's queue, an interruption
cancels only that answer, a voice stop silences everything, and missed
requests are kept without text (last 100). Tested with a fake voice side.
- Core: answer(user, text) adopts a playback request the worker speaks
under the same id, cancel(id) stops one request, ask_addressed and
ask_rank pass the conversation's questions; new SpeakingStopped,
Addressed and Ranked events.
- Worker client: reply, addressed and rank messages and their results; a
reply with no answer, refused or not sent ends its speech as failed.
- Voice worker: addressed and rank messages on their own threads, beside
a running reply; a spoken reply cancelled while the brain is answering
is not spoken. judges.py holds the two short LLM judgements with the
heard text fenced as data; eval evals/test_voice_judges.py.
- Specs (conversation, discord core, voice worker), docs/llm_contexts.md
and the roadmap updated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Action::Rank and ranked() carry a ranking id; answers to a replaced or
dropped ranking are ignored.
- A candidate tying the ranked ones while a ranking is pending replaces
it with a new ranking over all of them (plus the running answer when
the ranking is about interrupting it), keeping the first deadline, so
only compared candidates are missed as lower_score. A better one makes
the ranking moot.
- next_deadline returns the collect timer while collecting, and the
settle deadline only while an ending utterance holds the choice up.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A new request that ties the running answer on priority and wake word
is ranked against it by the brain; a win interrupts, a loss or a
timeout lets the answer go on. The ranking is dropped when the answer
ends first.
- A ranking that arrives after its deadline counts as a timeout.
- Candidates collected while an answer runs keep end-time order, so the
timeout fallback picks the earliest-ended one.
- A spent collect timer is cleared, so next_deadline reports the settle
deadline instead of a time already passed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- calls.rs: wake words anywhere in the utterance with near matches by
edit distance on NFKD-normalised letters (Hangul splits into its
letters), call modes (wakeWord, addressed, everything), designated
people with both switches, and a voice stop (wake word + stop word).
- policy.rs: first, inOrder, latest and important as an event-driven
state machine with the time passed in: ordering by end time, waiting
for an earlier-ended utterance still being transcribed, queue limit,
interruption, importance ranking only on a tie with a timeout, stop
dropping the queue, and a reason for every missed request.
- settings: new call and response sections, validated with the key.
- conversation.spec.md documents the contract; registry and roadmap
updated. Wiring into the Discord core and the brain comes next.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>