Files

T

jschoubben ea4dfaa5a2 mesh-hand-acts answers bounded, newest first; mesh-healers seeds from a partial answer (issue 1966 S8)

hand-acts read the whole log (84k entries, 47 MB) on every call and could never answer inside the call bound or
the bus payload. It now reads from the newest entry backwards, page by page, and stops at the window's start, at
900 KiB of acts or at 20 s, saying complete: false, cut and why. warrants is bounded the same way. mesh-healers'
start-up seed takes a partial answer and logs it, instead of retrying forever.

Quick fix: this (mesh-catalog only, about 1.5 h). Thorough fix: also the tool runner never freezing on an oversized
bundle line and logging unanswered calls (mesh-tools, a separate fix by another developer, lead's ruling Q3), and an
SDK-side bound. Chosen here: quick for this module, the thorough part running beside it; the byte cap is the
module's own (lead's ruling Q1, a `limit` argument is a later note).

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5

2026-11-09 18:23:33 +01:00

cmd/mesh-hand-acts

mesh-hand-acts answers bounded, newest first; mesh-healers seeds from a partial answer (issue 1966 S8)

2026-11-09 18:23:33 +01:00

.gitignore

Design 47's last milestones: the keeper, self-check, healers, hand-acts, provisioner, vault, artifact sweep, disk readings, credential forms (issues 774, 1952, 1953, 1954, 1955)

2026-10-30 02:21:51 +01:00

go.mod

Complete go.mod and go.sum for the externals each module builds with

2026-11-06 00:51:22 +01:00

go.sum

Require every mesh package of the group at the floor version (ADR 0573 sections 2 and 4, issue 1966)

2026-11-05 16:56:39 +00:00

module.json

mesh-hand-acts and mesh-healers stop reading the controller's hand-act log (ADR 0571 §13)

2026-11-02 00:17:52 +01:00

README.md

Make the controller checks strict: nothing names the placed-nowhere controller

2026-11-02 12:29:56 +01:00

README.md

mesh-hand-acts

Holds the seat mesh-hand-acts (novox/hq ADR 0565 §10, §11): the hand-act log, moved out of the controller. Go, one binary (cmd/mesh-hand-acts), served by a runtime of its own on its own bus account (runs-as), so that its account alone writes the log.

What it keeps

the log acts (the stream LOG_mesh-hand-acts_acts, a module log of ADR 0297, as ADR 0565 §10 has it a stream): every act appended in its order under its key act-<ns>-<n> (warrant-<asker>-<ask> for a warrant), in the layout of the controller's log. The log keeps each act 400 days (max-age-days) and refuses a new act when full rather than drop one; hand-acts says how full it is against its cap. Each act is said as act-recorded.
mesh-hand-acts_warrants: one key <asker>.<ask> per warrant, made once by create before its act is appended, so of several instances one records it; a warrant whose act was lost is written again from the router's record.

Its verbs

mesh-hand-acts.hand-act: what, why, cause, the condition addressed, and the act's verb (a repair when not given; hand-act drill for a drill, whose cause is always drill). Who did it is the caller the runtime proves.
mesh-hand-acts.warranted: asker and ask. Read from the router's own record of that ask (messenger.asks), never from the caller, and recorded once per ask; an ask still open, ended without a choice or another asker's is refused.
mesh-hand-acts.hand-acts: this log (the controller's acts were copied into it once), newest first, with the causes repaired by hand twice within a fortnight; warrants=true lists the warrants.
hand_acts_copied and hand_acts_copy (research 072 row 26): the controller's hand acts are copied once into this seat's log, each with its own key, time and author. It runs at the module's start while the old bucket is readable and no marker (copied, key controller-hand-acts) says it was done, and by the tool; an act already in the log is never appended again, and hand-acts counts a copied act once. hand_acts_copied says whether, when and how many. The lease write has no hook to run it from, so the start is the trigger; hand_acts_copy with top_up=true, asked after the lease write, appends any act the controller wrote since the copy (a finished copy is otherwise a no-op).

No act is written to both logs: every recorder calls this seat from its delivery, and the controller keeps its own acts in its own bucket until it loses its lease.