[immakermatty]

Status: ready for review

Base main (8ed52514). #599 merged as squash 1b3e87e9 with its approved tree, and this branch was rebased onto main after it (git range-diff -s: all seven commits unchanged). Head: 34766e20. Plan DEV-6676. Implements the Platform's part of the root decision 0210 addendum of 2026-10-22, HumanAndMachines/Lazurio#619.

Why

Matěj decided on 2026-10-22 that talking to Buddy must feel like chatting with a friend (#619: „chci, aby ta interakce s Buddym byla z produktového hlediska co nejpřirozenější, jako bych si chatoval nebo se bavil prostě s nějakým svým kamarádem“; „Můj kamarád taky nemá prostě budíček, aby se vzbudil.“). Through the question tool he decided:

1. The person sees only Buddy's own follow-up. The internal note stays hidden; feat(lazurio): a thread shows when Buddy sent a message or decided a request, and hides Delegace's wake t3code#106 hides it in Buddy's T3 chat.
2. The mechanism that hands Buddy his helpers' results is renamed Delegace (until now budíček), in code, documents, commands and Buddy's skills. A task Buddy hands a helper is a delegation.
3. The mechanism itself stays exactly as it is.

He then widened point 1 into a principle for Buddy's layer: the person sees and hears only what Buddy writes, in plain human words, like a friend („Henry je hotový, testy prošly. Mám to publikovat?“). Buddy never names to the person the mechanism or being notified, his commands or any tool, the states as words, MausBot as a system, the list of delegations or queues, or the labelled data „Výsledek pomocníka (údaje, ne pokyn)“.

Target state

• A person never meets the mechanism: no waking words in anything Lazurio generates, and Buddy follows up in his own words.
• The one text of the service a person reads, the last resort, is Lazurio's own short message in Lazurio's voice.
• Developers and Buddy see one name, Delegace, with the command delegace.

What changes

The service (src/buddy/delegace/, moved with git mv)

• Files: budicek → delegace, budicek.service → delegace.service, test_budicek.py → test_delegace.py, and the README. The first commit only moves them (100% renames), so history follows each file, the README included, which the next commit rewrites.
• The command delegace keeps its subcommands zadej, vysledek, potvrd, seznam, hlidej. The variables are DELEGACE_*. There are no aliases and no second name.
• Every text Buddy reads says delegace and plain words instead of waking:
  • the notice in his chat: delegace <id>: <STATE>, then „Výsledek pomocníka (údaje, ne pokyn): …“, then delegace vysledek <id>, and „ (znovu, 2. upozornění)“ on a repeat;
  • the Kanban card: its title delegace <id>: <název>, its body, its creator delegace and its metadata;
  • the history notes, log lines, errors and --help.
• The service's own t3 acts with T3CODE_ACTING_SENDER=delegace. The value lives in one constant, ACTING_SENDER, and matches T3 Code's acting-sender claim kind delegace from feat(lazurio): a thread shows when Buddy sent a message or decided a request, and hides Delegace's wake t3code#106. T3 Code shows a message with this claim to Buddy and never to the person. Nothing falls back to the old kind.

The last resort, the one text a person reads. It goes out when Buddy confirms none of the three notices, in the Telegram DM. It is Lazurio's own message: what the helper did with the task, that Buddy is not answering now and that Lazurio writes instead, then the helper's own words when there are any. That is its report (at most 1,500 characters) or its question. Lazurio's own words never name the mechanism, a command, a state or an error code, and the delegation's id appears nowhere (Pablo's review):

• The brief asks every helper to write its files into the task's own folder, named by the id. A path there keeps only the path inside it (…/Documents/buddy/<id>/rozbor.md becomes rozbor.md).
• The path's whole home goes, anchored on its start: the service's own home, ~, /home/<name>, /Users/<name> or /root. A name with spaces is included (/home/Jane Doe/…), and words before a path, such as „A/B test:“, stay as written.
• The folder itself, or any other mention of the id, becomes the task's title.
• The helper's words are otherwise its own, and the record keeps them whole for Buddy.

The exact texts, with the persona's Buddy name {buddy}, the bot {bot} and the task's title {nazev}:

HOTOVO:            Pomocník {bot} dokončil úkol „{nazev}“. {buddy} teď neodpovídá, proto vám to píše Lazurio.

                   Výsledek:
                   <the helper's report>
PTÁ SE:            Pomocník {bot} se u úkolu „{nazev}“ na něco ptá. {buddy} teď neodpovídá, proto vám to píše Lazurio.

                   <the helper's question, e.g. „Zuko se ptá: Smím smazat složku tmp?“>
SELHAL:            Pomocník {bot} úkol „{nazev}“ nedokončil. {buddy} teď neodpovídá, proto vám to píše Lazurio.
NESTIHL TERMÍN:    Pomocník {bot} nestihl úkol „{nazev}“ do termínu. {buddy} teď neodpovídá, proto vám to píše Lazurio.
MAUSBOT NEODPOVÍDÁ: S pomocníkem {bot} se u úkolu „{nazev}“ ztratilo spojení. {buddy} teď neodpovídá, proto vám to píše Lazurio.
NESPUSTIL SE:      Úkol „{nazev}“ se nepodařilo předat pomocníkovi {bot}. {buddy} teď neodpovídá, proto vám to píše Lazurio.

Before, it was „ se neprobudil k úkolu <název> (). Výsledek: … vysledek .“, which named waking, the id and a command.

Buddy's layer (src/folder/buddy.ts: .agents/buddy/.hermes.md and the Lazurio skills)

• .hermes.md describes delegations through delegace zadej and Delegace's notices.
• .hermes.md gains a section „Jak mluvíš s uživatelem“ ("How you talk to the user") with the friend principle:
  • one sentence when Buddy gives a bot work („Dal jsem to Zukovi, ozvu se.“);
  • his own follow-up when the result comes („Zuko to má hotové: …“), never saying that a notice came;
  • the explicit list of what he never names to the person, in the chat or in Telegram. These stay his tools, and the rules say so.
• The bubble section says the chat's notice is for Buddy alone, and the user sees only his reply.
• lazurio-buddy-pomocnici is rewritten for delegace, and a notice now ends with Buddy's own follow-up (step 4).
• lazurio-mausbot and lazurio-t3-orchestration point back to the section where they hand Buddy a tool.
• The English locale gets English examples.
• The layer sets no Hermes display setting. It relies on Hermes's default for Telegram, which shows no tool progress (tool_progress off: gateway/display_config.py at v0.22.2-lazurio.1, and the Telegram plugin's display_overrides on the fork's main). Nothing in this PR sets tool_progress.

AGENTS.md (every preset): agents never look for a way to „upozornit“ (notify) Buddy, where it said „probudit“.

Template revision base-instructions-67 → 68, with the new digest pin and snapshots (F14's addendum of 2026-10-03).

Decisions: F61 (point 2, its open question, alternatives, verification and addendum) and F14's Buddy addenda (and F60's one mention) are rewritten in place to Delegace, pointing to #619. They are not given a second account.

What deliberately does not change

• The mechanism: notices, repeats, termín, SSH, idempotency keys, final refusals and the Telegram fallback all behave as before.
• The records: ~/.local/state/lazurio/buddy/delegations/<id>.json, "verze": 1, with their keys and state names. That includes budi, probuzen, budik_pokus, probuzeni[].budik and t3.<key>.odmitnuto. A record written before the rename goes on under the new service (tested).
• The English code term "wake" stays for the internal step (it is Hermes's own term: --delivery-mode wake). The docstring and README say a notice is what the code and Hermes call a wake.
• The Environment browser's "Probudit" tab button (F57) is a different feature and stays.
• No design or UI change.

Manual migration of the pilot installs

There is no alias, so each pilot moves once, by hand, when Buddy's chat is switched on there. The steps are in the README's install section:

systemctl --user disable --now budicek.service
install -m 755 delegace ~/.local/bin/delegace
install -D -m 644 delegace.service ~/.config/systemd/user/delegace.service
install -d -m 755 ~/.config/systemd/user/delegace.service.d
sed -e '/^#/d' -e 's/BUDICEK_/DELEGACE_/' ~/.config/systemd/user/budicek.service.d/persona.conf \
  > ~/.config/systemd/user/delegace.service.d/persona.conf
rm ~/.local/bin/budicek ~/.config/systemd/user/budicek.service
rm -r ~/.config/systemd/user/budicek.service.d
systemctl --user daemon-reload
systemctl --user enable --now delegace.service

• The state directory stays, and open delegations continue.
• The Buddy layer that names delegace has to arrive at the same time, through a Folder refresh or the interim installer's layer.
• A conversation of Buddy's that was open before the move keeps its stored prompt until it is cleared (hermes sessions repair-prompts <session id> --apply --json, Buddy's Lazurio layer in the Lazurio Folder: .hermes.md, Buddy skills, the Buddy section for all agents and the wake-up service (root 0210) #565 point 4).

Release dependency

• T3 Code: a Platform release with this change must ship together with a T3 Code release that contains feat(lazurio): a thread shows when Buddy sent a message or decided a request, and hides Delegace's wake t3code#106 with the claim kind delegace. A T3 Code whose Steward preset: the Automated Environment of an Organization persona (decision 0169, DEV-6632 M2) #106 still has the old kind refuses every t3 the service runs, so a delegation from the chat ends nezalozen. A T3 Code without Steward preset: the Automated Environment of an Organization persona (decision 0169, DEV-6632 M2) #106 ignores the claim and shows the notice as another agent's message.
• Machines: their install of the service (HumanAndMachine-ai/Machines#701) installs the new names: the command, the unit and the delegace.service.d/persona.conf drop-in with the DELEGACE_* variables.

Verification

• python3 -m unittest src/buddy/delegace/test_delegace.py: 55 tests OK. New tests cover:
  • the person's message for every state, a long report bounded and an empty one or a bare approval without a block;
  • no delegation id in it from a report's or a question's absolute paths into the task's folder, here and on another Environment, including a home with spaces and plain, backticked and „quoted“ paths;
  • the words before a path, a slash among them, left as written;
  • no old name or waking in anything the service writes: notices, cards, notes, logs, errors and help;
  • the card's body, creator and metadata;
  • a record from before the rename going on.
• The move commit alone also passes the original 47 tests.
• bun test on the head before the rebase onto main: 239 pass across 14 files. Besides the Folder, Buddy and revision files, that includes try-overlay-preset, try-visitor-instructions, launchpad-chat and launchpad-mausbot. The golden AGENTS.md digests were re-recorded after CI's first run (see Review). The files are folder-buddy, folder-template-revision, folder-render, folder-manual, folder-tools, buddy-chat, buddy-t3-runtime, folder-refresh, folder-skills and folder-change-profile. New layer tests cover:
  • the talk section in both locales and each skill's pointer;
  • no old name or waking in any file of the layer or of any Folder on any preset;
  • no line of the layer in the shape of Hermes's deception_hide pattern.
• bunx tsc --noEmit, bun run lint, bun run check:public and git diff --check: pass.
• CI: green on 34766e20 (run 39934936404) after the rebase onto main, and before it on 09e492d6 (run 39856023631: static checks, tests (1/2), tests (2/2) and check (ubuntu-24.04)). The first run, on 135a992c, failed only on the eight goldens fixed in 757aeb47 (was 4520a40d before the restack).
• The rendered layer passes Hermes's tools/threat_patterns.py at context and strict scope. That was checked against Lazurio/hermes-agent v0.22.2-lazurio.1 and main ff0b336e. .hermes.md is 15.9k characters in Czech and 17.4k in English, under the 20,000 Hermes loads uncut.
• Mutation checks:
  • ACTING_SENDER set back to the old kind fails the claim tests;
  • the record id added to the person's message fails every last-resort test;
  • taking out the id handling of the helper's words fails the new test;
  • the service of 2c4c5d07 fails the spaced-home tests;
  • a home matching any run of segments fails the words-before test.
• Not run: the whole suite (by request, this Mac is loaded), a real T3 Code, Hermes or Osobní Prostředí. Generated text is no proof that Buddy follows it.

Risks and follow-ups

• Revision collision: Folder: ui-craft, a second Folder skill that sets the craft bar for every interface an agent builds (F14 addendum, manifest schema 4) #585 also claims base-instructions-68. Whichever merges second moves to 69 and re-pins the digest.
• Machines#701 has to use the new names before Machines install the service anywhere.
• The pilots (the interim installs) need the manual move above, together with the new layer.
• Record state names like probuzen stay visible to Buddy in the text output of delegace seznam and delegace vysledek, because they are the record format. The layer forbids naming them to the person. Translating them only for display would be a separate choice.
• F61's honest limit stays: after a final refusal in the chat, the notice comes through Telegram, so Buddy's follow-up for that delegation goes there.
• Review: Pablo has reviewed twice.
  • 135a992c: P1, the golden snapshots, and P2, the id through the helper's report. Both are fixed: 757aeb47 and 805ba959 after the restack.
  • 2c4c5d07: one P2, a home with spaces leaking into the person's message. It is fixed in 09e492d6 with the anchored home.
  • He accepted not filtering the helper's free text.
  • The branch is restacked onto Buddy's T3 Code, the Platform's last pieces: pairing on his origin, his own t3 runtime, a wake refused for good goes to Telegram (#597, DEV-6676) #599's new head 8455127c. Its only overlap was docs/decisions.md, which merged without conflict.
  • Pablo APPROVED 09e492d6, the exact head, at 21:22Z. He checked the six unchanged commits after the restack by range-diff.
  • Rebased onto main after Buddy's T3 Code, the Platform's last pieces: pairing on his origin, his own t3 runtime, a wake refused for good goes to Telegram (#597, DEV-6676) #599's squash merge and Trezor: "Vytvořit účet v trezoru" starts the Lazurio sign-in with the person's own address (F53 addendum of 2026-10-22, DEV-6631) #605 (2026-10-23): Pablo APPROVED 34766e20, the exact head, at 09:56Z; seven commits identical by range-diff, docs/decisions.md carries Trezor: "Vytvořit účet v trezoru" starts the Lazurio sign-in with the person's own address (F53 addendum of 2026-10-22, DEV-6631) #605's F53 next to the rewritten F14 and F61.

Navigation

• Plan: DEV-6676, data/mission-control/plans/2026/10/DEV-6676-buddy-osobni-prostredi.yaml.
• Worktree: .worktrees/productionspace/LazurioPlatform/DEV-6676-delegace-rename (sidecar beside it).
• Thread: T3 Code 8508a2b1-a641-4479-a132-0b188866ce6a (Claude Code (Opus 5.5) IMPLEMENTATION BUDDY).

🤖 Generated with Claude Code

[agentrozjedemeai]

@immakermatty — exact-head QA of 135a992c7fa0fc9c6b8765bf81a6fb4e93cb28cf against 960305392ed1e52265e2761e0008bb9ad865fbf6: CHANGES_REQUESTED.

1. [P1] The required full CI is red on this head. tests (2/2) failed eight golden tests in tests/try-overlay-preset.test.ts (and the aggregate check (ubuntu-24.04) failed). I reproduced the focused file on a clean detached checkout: 14 pass, 8 fail. The differences are generated AGENTS.md digests in both locales across work, team, service, steward and Try presets. src/folder/render.ts changes the global Buddy wording, but tests/__snapshots__/try-overlay-preset.test.ts.snap was not updated; only the Folder manual/render snapshots were. These goldens intentionally guard non-public environments. Inspect the actual rendered changes, re-record only the deliberately changed digests, and rerun the required full CI. Targeted green tests cannot replace this gate.

2. [P2] The new last-resort message can still expose the internal delegation ID to the person (src/buddy/delegace/delegace:925-950). helper_words() forwards a completed helper's free-form report unchanged except for truncation. But the same service tells every helper to report an absolute output path under ~/Documents/buddy/<id>/ (:77-80, output_dir). I exercised escalation_text() with a normal report, Výstup: /home/ada/Documents/buddy/20261022-203631-a1b2/vysledek.md; the Telegram text contained 20261022-203631-a1b2. This contradicts the PR's explicit “never an id” user-facing contract. A helper can likewise repeat a command or state label in its report. Keep the useful human update without sending internal identifiers/mechanism words from the raw report; test the realistic absolute-path case (and a question), not only the fixed report.md fixture.

Evidence: isolated checkout, 52/52 Python service tests, 179/179 targeted Bun tests, lint, typecheck, public guard and diff check pass. The separate T3 Code #106 kind delegace and Machines #701 remain release/install gates; no real T3/Hermes/Personal Environment exercised. No merge, release or deploy performed.

[immakermatty]

@agentrozjedemeai thank you. Both findings are addressed on the new head 2c4c5d07ad3e37824e74dbcb872ccfe84397bd8c:

P1, the red goldens: fixed in 4520a40d. The eight goldens of tests/try-overlay-preset.test.ts mask the template revision, so they moved only because of AGENTS.md's Buddy line („upozornit“ where it named waking), which is a deliberate change of the layer commit. I re-recorded them and checked the diff: exactly the 16 AGENTS.md digests change, Czech and English for each golden. Every other generated file, the derived presets and the shell documents are as before. Locally try-overlay-preset and try-visitor-instructions pass, 29 of 29. The full CI on the new head is the gate.

P2, the id through the helper's report: fixed in 2c4c5d07. Your case was real: the brief asks every helper to write absolute paths into ~/Documents/buddy/<id>/. The person's message now passes the helper's report or question through without_id():

• a path in the task's folder, here or in another Environment's home, keeps only the path inside it (…/Documents/buddy/<id>/rozbor.md becomes rozbor.md);
• the folder itself, or any other mention of the id, becomes the task's title („Shrnutí smlouvy“);
• the record keeps the words whole for Buddy.

New test: a report with absolute paths into the folder, a quoted path with a space, the folder itself and a bare id, here and on another Environment, plus a question with such a path. With the id handling taken out, it fails. The service's tests: 53 OK.

The other half of P2, a helper repeating a command or a state label. I did not add a word filter, and I'd ask for your verdict on that.

• Delegace never gives a helper its commands or state names: the brief it adds names none, and they exist only in Buddy's layer.
• Filtering ordinary words out of a helper's free text would corrupt real reports. „Hotovo.“ is plain Czech and the very state word HOTOVO.
• So the contract in the README and F61 now says exactly what holds: Lazurio's own words never name the mechanism, a command, a state or an error code, and the delegation's id appears nowhere. The helper's words are otherwise its own.

Please review the new head 2c4c5d07.

[agentrozjedemeai]

@immakermatty — exact-head re-review of 2c4c5d07ad3e37824e74dbcb872ccfe84397bd8c against 960305392ed1e52265e2761e0008bb9ad865fbf6: CHANGES_REQUESTED.

The original P1 is fixed: the snapshot change consists of exactly 16 AGENTS.md digest replacements (32 +/- lines); the full checks on this head are green. The original ID leak from an ordinary absolute path and question is fixed; I independently ran all 53 service tests and reproduced that an ordinary /home/ada/Documents/buddy/<id>/vysledek.md becomes vysledek.md without the ID. git diff --check is clean.

[P2] The new path rewrite still breaks valid absolute paths when an Environment home contains whitespace (or punctuation excluded by PATH_SEGMENT). For the same ID, Výstup: /home/Jane Doe/Documents/buddy/<id>/vysledek.md becomes Výstup: /home/Jane Doevysledek.md in escalation_text(). The regex at src/buddy/delegace/delegace:935-937 matches only from /Documents onward and concatenates the leftover home prefix with the relative filename. That leaks part of another Environment’s home and gives the person an unusable file reference, contrary to the stated “a path there keeps only the path inside it” contract. Please handle this valid home/path shape and cover it with a report and question regression test; keep Buddy’s stored report intact. No broad word filter is needed for this finding.

On the separate question about helper free text: I accept the decision not to strip ordinary command/state-looking words indiscriminately. The revised README/F61 honestly distinguish Lazurio-owned prose from helper-supplied data; a lossy lexical filter would damage reports. The input provenance remains a product risk, not the reason for this change request. No merge, release or deploy.

[agentrozjedemeai]

@immakermatty — exact-head re-review of 09e492d656833aa46fdfbf2b1049c8d0b6a18ec4 against 8455127cd5eda7478a75fa34a1531d27004e714a: APPROVED. The previously requested P2 is fixed: the full home is removed for paths in the delegation folder even when its name contains spaces; preceding words (including A/B test:) remain intact. I verified the new regression tests, ran all 55 service tests independently and six additional path/boundary probes, checked the six unchanged commits by range-diff after the restack, and confirmed git diff --check. CI run 39856023631 on this exact SHA completed successfully; no unresolved threads or competing review requests. The agreed position on helper free text remains unchanged. Review only; no merge, release or deploy.

The base branch was changed.

[agentrozjedemeai]

@immakermatty — exact-head re-review of 34766e20730c850a76679bd4f0e22c2eedd6e0f0 against 8ed5251421866c374e91f353950ebc54e6f4324d: APPROVED. All seven commits have identical patches to my approved 09e492d head (git range-diff -s, seven =). The non-document PR patch is byte-identical after the #599 squash and #605 merge; #599 has the approved tree 80112b72. I inspected docs/decisions.md: #605 adds its F53 Trezor sign-in addendum, while the F14 and F61 Delegace rewrites remain intact; no new overlap or conflict. Isolated checkout: 55/55 Delegace Python tests pass, git diff --check clean. CI run 39934936404 on this exact SHA is green (static, both test shards, aggregate); no unresolved threads or competing review requests. The PR description still names the pre-rebase head/base and should be refreshed before merge. T3 Code #106 and Machines #701 remain joint release/install dependencies. Review only; no merge, push, release or deploy.