Every other test in the package builds its own JSON, so a key renamed on one
side and not the other went unnoticed until the daemon refused to start. This
reads deploy/mavend.json through the same Load, and asserts the settings whose
absence would be a silent behaviour change rather than an error: n_gpu_layers
being 0 means CPU-only inference, and nothing defaults it.
MemoryEvalConfig and EmailConfig, with their two constants and their normalise
arms. Neither loop can speak, which is why they read together.
The shared defaults const block now holds only the core daemon's own; every
other block keeps its defaults beside its struct.
Both shape what reaches him unasked, so they read together.
The digest defaults were three literals inline in applyDefaults; they are now
named next to the struct like every other block's, at the same values (30m, 5,
sev 2). normaliseDigest is the one normalise that materialises an absent block
instead of folding it to nil, because the dispatcher reads Digest.Enabled with
no nil check — noted in the comment so the next block does not copy it.
RoutineConfig, MorningRoutineConfig, MorningRoutineItemConfig, QuietHoursConfig,
the two mappers, and the severity-floor and cron-parse arms as normaliseRoutines
and validateRoutines. config.go drops the morning and cron imports.
Its validate arm goes with it as validatePhraser.
The doc drifted on every numeric field. It claimed NGpuLayers defaults to -1,
NCtx to 2048 and Timeout to 30s. Nothing in this package defaults any of them:
phraser.DefaultConfig sets -1 and has no callers, and cmd/mavend builds a
phraser.Config literally. So an omitted n_gpu_layers reaches llama-server as
-ngl 0, CPU-only, masked here only because deploy/mavend.json sets 99. Fixed
the comment and left the code, and the discrepancy is filed.
WorkerConfig, TtsConfig, EmbedderConfig, WeatherConfig and ToolConfig. None of
them is reachable except through a voice block, so they read better beside it.
The VoiceConfig struct only. Its defaults, normalise/validate arms and
UseLLMRouter follow in the next commit, because the pre-commit cap counts a
pure move at twice the block size.
The RouterThreshold doc drifted: it said the default was 0.35 and that 0.0
meant permissive. DefaultRouterThreshold is 0.55 and applyDefaults replaces
anything <= 0, so permissive was never reachable. Fixed the comment, not the
code.
Pure move, plus a note on SpeakerConfig.LibPath: it is the one field in the
tree with no reader, no default and no validation, because
cmd/mavend's newSpeakerEmbedder discards the whole block — there is no
speaker model on this box. It stays declared so a block written from the
plan document matches, and the comment now says so rather than leaving the
next reader to grep for it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move. The media block and the vision block, their two accessors and
their two validate arms. The validate arms become validateMedia and
validateVision so the check sits next to the field it rejects.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move. Feeds and Crawl are the same seam — a webfetch on a timer that
writes notes and may not speak — so the constraint is stated once at the top
of the file instead of twice inside the blocks. The crawler's own comment
still put it behind "the model, his memory and Kiwix" and did not know about
the live search; corrected.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move. Search and Kiwix are one seam — the query chain tries the live
search, then the ZIMs — so they share a file, in the order they answer, with
the "only the query leaves the box" rule stated once at the top instead of
twice. KiwixConfig's own doc said it was searched "before anything touches
the network", which stopped being true on 2026-08-02 when search went in
front; corrected here.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move. Praxis, Nexus and Hexis go to ecosystem.go with a note on why
they stay three identical two-field types instead of one shared
EndpointConfig: the block a reader greps for is the service they are
debugging. The workstation block, its two defaults and its normalise arm go
to workstation.go.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move, with one comment corrected on the way. NetScanConfig.Rate said
"0 ⇒ 50"; netscan.DefaultRate is 100 and has been since the package was
written, and deploy/mavend.json sets 100 explicitly. The three sibling
defaults now name the constant they come from rather than restating a
number that can drift again.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move. SmartHomeConfig, its two refresh constants, the smarthome.Config
mapper, and the normalise and validate arms now sit together. The provider
check moves inside validateSmartHome, where the block it rejects is visible.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Second half of the move. MCPConfig, DefaultMCPHostInterval and the
normalise arm now sit next to the server struct they govern; applyDefaults
calls normaliseMCP instead of inlining it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Pure move. Nothing changes but the file a reader opens. validateMCP is the
one new name: config.go's validate arm becomes a method next to the block
it checks, which is the shape the rest of this sweep follows.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
askClarify parked "Что сделать?" whatever was on the other end. With an empty
allowlist that question has no answer: she asks, fails, asks again and gives up,
three turns spent on a request she could have declined in the first one.
Empty allowlist now names the gap and parks nothing. A non-empty one still asks,
and names what she can run, capped at six, so the question is answerable.
Three durable stores said no client machine existed. That was written
when the workstation was only a model host. It is where he sits most of
the day and it has the microphone.
The verdict is unchanged and so is the seam. What changes is the size of
the remaining work: deploying two daemons and asking mavend to listen on
TCP, not acquiring hardware. Note that deploying them does not by itself
prove a wake word — mavwaked gates on energy and has no keyword model
(V-487).
Measured on the box: "глаголы в прошедшем времени с окончанием -ла",
copied from the query prompt where it fixes her gender, was read by the
resident model as an instruction to use the past tense throughout. She
answered "я вела заметки" and "если ты разрешил, я управляла домом",
which makes a live capability sound finished.
The gender rule stays, without the example.
Two defects found probing the new source on the box.
"кто ты" was answered from one of his notes. The self source sat below
memory and notes, which match by proximity and have no idea the subject
is her. It belongs above all three: a question about her has no answer
in his data either.
And PhraseQuery opens every answer with "вот что я нашла: ", which is
deliberate — it marks the answer as a lookup. Her own description is the
one subject she did not look up, so this is PhraseSelf instead, same
read-only discipline and its own opener. The Stub reads the description
out as it stands, which needs no fallback: it is already her voice.
"что ты умеешь" reached the personal boundary, which claimed it as his
and said "не знаю — не нашла у тебя такой записи" about her own
description. Letting it past would be no better: SearXNG answers about
somebody else's assistant.
A self query source above the boundary, reading one frozen description.
It is NOT a note — notes are his, and a note about her would come back
for "что я записал", would be fed to the digestion worker as something
he said, and would be recalled by proximity for questions that are not
about her.
The description names only what this box does. Everything that depends
on config — the house, the LAN, the feeds, the list, weather, telegram —
is named as depending on what he allowed, and a test pins that split:
inventing a capability here is the same defect as inventing a fact.
topicSelf is scored like every other topic, with a narrow keyword floor
for the no-embedder case. "что ты умеешь" moved off topicOther, where it
had been sitting so an attention question had something to lose to — a
phrasing on two sides never clears the margin. TestONNXTopics 38/38 ->
43/43 on held-out utterances.
Found verifying the three fixes on the box: "кто изобрёл телефон" ran a
LAN scan and answered "нашла 3 устройства". The network seed set opens
with "кто в сети сейчас" and names devices throughout, so a "кто ..."
question about any device noun landed there.
Three topicOther seeds, same shape as the V-553 fix. TestONNXTopics
34/34 -> 38/38 on held-out utterances, and a real scan is still a scan.
Prior turns were joined with newlines and nothing else, so the model got
four unlabelled lines and no way to tell which one was the question. It
answered an earlier one: asked "как дела" after a question about the
telephone, she carried on about the telephone. Four turns live for
fifteen minutes, so the line she answered was often minutes old.
One user message still, because the template constraint that forced the
flattening is real. The turns are labelled as his own earlier words and
the current utterance is named as the one to answer. With no history
the message is the utterance alone, unchanged.
"расскажи про Байкал" was refused as his by 0.0052. Every world seed
opened with an interrogative, so a world question phrased as an order
landed nearer "я тебе рассказывал об этом?" — the same verb about his
own words. Four narrative seeds on the world side.
TestONNXPersonalBoundary 25/25 -> 29/29 on held-out utterances, and the
control "я рассказывал тебе про байкал?" is still his. TestONNXTopics
unchanged at 34/34.
A parked question consumed whatever came next. One act she could not
fulfil ate three turns: "выключи свет в спальне" asked "Что сделать?",
and "кто изобрёл телефон" was scored as an answer to it, then "как
дела" after that. Nothing tested whether the words could be an answer.
The test is two offline token checks that already existed for other
callers: a question shape, or a capture verb. It fires only where the
answer filled nothing, so an answer that closes the gap still lands
whatever shape it has, and the retry budget is untouched — the count
was never the problem.
The topic seeds let "какой сегодня праздник" and "что интересного
произошло сегодня в мире" past the weather source, and the personal
boundary refused them one source further down: "не знаю — не нашла у
тебя такой записи" about a public holiday.
Same defect, same mechanism, one layer lower. "что у меня сегодня" is a
personal seed and worldSeeds had nothing in that frame. Two seeds fix it.
TestONNXPersonalBoundary 22/22 -> 25/25, nothing regressed.
Two recognisers claimed world questions naming a day, both by the same
mechanism and neither by its keyword floor.
topics: weather was the only topic whose seeds carry a day word, four of
eight. So every "какой сегодня X" landed nearest it. "какой сегодня
курс доллара" cleared the margin by 0.0220 and "какой сегодня
праздник" by 0.0398, against 0.0883 for a real weather question, and the
gate asked "для какого города?" about the dollar.
The margin was not the knob: 0.0398 is not a coin flip, and raising the
bar far enough would take real weather with it. topicOther was missing
the negative class. Six seeds, four naming a day and two carrying the
"какой сегодня X" frame itself — a frame both topics use has to sit on
both sides, or the side that owns it wins every noun it has never seen.
personal boundary: the same shape one layer down. "что у меня сегодня"
and "когда моя встреча" put "when does a thing happen" on the
personal side and no world seed answered it, so "во сколько закат
сегодня" was refused as his. Three world seeds, each carrying сегодня,
which is the half of the frame that does the pulling — without it they
caught nothing.
Measured, both opt-in against the ONNX embedder homesrv runs:
TestONNXTopics 27/27 -> 34/34 (7 new cases, none regressed)
TestONNXPersonalBoundary 19/19 -> 22/22 (3 new cases, none regressed)
The control matters as much as the fix: "во сколько у меня встреча" is
the same frame about something that IS his, and it holds at +0.0842,
unchanged from before the seeds moved.
Replaces a test whose name promised more than its body checked: it
looped the grammars asserting Pattern != nil, which regexp.MustCompile
already guarantees at init. Asserting the grammars pass IsAgendaQuestion
would be true by construction, since the first arm is that same loop.
A hand-written example per grammar name catches what neither does: a
grammar edited until it no longer matches the case its comment gives,
and a new grammar nobody wrote an example for.
queryCalendar matched on a day word and stepped aside only on weather
wording. Every world question naming a day was claimed by it and answered
with an empty schedule: "какой сегодня курс доллара" replied "на
05.08.2026 ничего нет", which reads as an answer about a subject she
never looked at. All four probe utterances have an answer in search, and
search sits below the calendar.
V-474 fixed one instance of the class. Sunset, holidays, exchange rates
and world news are the same class and weather wording does not cover them.
router.IsAgendaQuestion is the narrowing. Its first arm reuses
AgendaQueryGrammars, so the rule that routes a question to the query
chain and the rule that lets the calendar answer it cannot drift. The
second reads a scheduled-thing noun, wider than the grammars because
"какие встречи завтра" carries no possessive. The third claims a
question that names no subject of its own.
A continuation is exempt: "а завтра?" cannot name an agenda, and this
is the only date-aware source there is.
Item 2 was blocked because the resident llama-server binds --port 0 inside the
container, so no host process can reach it. Cleared by taking the first of the
three ways out the task listed: a second llama-server on the same gguf, on a
fixed host port.
Cascade + resident model scores 75.8% full and 80.2% intent-only at p50 1.19s
and p95 1.65s, on the fixture as it now stands at 91 cases. That is a new
baseline rather than a movement: 14 cases were added since the 77-case number
in CLAUDE.md.
The model alone scores 37.4% full against 61.5% intent-only. The gap is slots,
not routing. Every reminder case leaves the time to the daemon, which is what
the contract asks of it, and the cascade fills them.
Item 3: the ~6s figure recorded in the task was one sample through the whole
of POST /api/chat, not the router, and is not comparable.
Item 4 is still not run. Killing the resident llama-server needs a permission
this session does not have, and it now has a second half anyway, since with the
workstation up only killing both proves the classifier answers.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoL7EBdYC5Mhz3DJd49GJy
At 21:12 "напомни мне завтра в семь позвонить маме" confirmed a reminder for
21:12 tomorrow. The hour was dropped and the wall clock carried onto the named
day. She did not ask; she named a time nobody gave her, on a path that fires.
A bare "напомни в семь" declines correctly, so adding "завтра" turned a decline
into an invented answer.
dateparser only reads a bare hour when it carries a qualifier or a colon.
"завтра в 7" keeps the current clock and "завтра в 7 часов" is read as seven
hours from now, which moves the day as well. English "at 7" fails identically,
so this is not a Russian defect and both prepositions are rewritten.
The script now gives it the colon: "в 7", "в 7 часов" and "at 7" become
"в 07:00" beside the existing утра/вечера rewrites. A duration is untouched,
because "через 2 часа" has no preposition to match, and so are "в 7:30",
"в 30 минут" and "в 2026 году".
The stub parser has always read the token after the day word, so the floor was
right and the production parser was not. No test on the stub could have caught
this. The four new cases are in TestPythonDateParser, which runs where
dateparser is installed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoL7EBdYC5Mhz3DJd49GJy
V-405 measured reach with the classifier only, and the LLM router is the
deployed default, so 16/30 was the floor rather than the shipped behaviour.
TestReachWithLLMRouter scores the same 30 cases with the model, gated on
MAVEN_LLM_URL like TestLLMRouterBaseline.
The open question was whether the model writes a literal Praxis capability
into the fn slot and reaches a service the classifier structurally cannot. It
does not. Praxis is 0/12 with the model alone, exactly what the classifier
alone scores, and all twelve fail the same way: local, empty fn. Nothing in the
router prompt names a Praxis capability, so there is no string for it to write.
So V-516's stage-0 grammars are the only path to Praxis, not a determinism
argument. Through the cascade the model scores 28/30 with praxis 11/12, one
point above the classifier baseline. Hexis is 10/10 either way.
Overreach is 1 in both configurations, under the 4 the harness asserts.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoL7EBdYC5Mhz3DJd49GJy
"что ты записала сегодня?" was recognised as a history question and then
answered with "ты говорил: …". The rows are right — a tapped fact is one act
seen from two sides — but the sentence hands the question back instead of
answering it.
historyAsks returns which side was asked and queryHistory phrases from it,
including the nothing-found reply. His side is tested first, because "отмечать"
is on both verb lists and "что я отметил" is not a question about her.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SoL7EBdYC5Mhz3DJd49GJy
claude