Files

T

jschoubben 475ffdcb33 gitea waits and keeps serving while its keys are unread; pin mesh-sdk 007b6fd

After a restart the forge-account provider returned a plain error, which the helper writes as failed
with its values cleared, so every consumer lost its forge entry until the keys loaded. provider.ErrNotReady
keeps the entry serving, in waits (issue 1954).

2026-10-30 00:04:14 +01:00

cmd/mesh-hand-acts

Keep the hand-act log's acts 400 days, as ADR 0565 §10 has it, now that a module log may say its age; pin mesh-sdk 2e5cc4f (issue 1953)

2026-10-29 22:18:59 +01:00

.gitignore

Add mesh-hand-acts, holder of the seat mesh-hand-acts, so the hand-act log has a home the controller's lease does not hold (issue 1953)

2026-10-29 21:54:21 +01:00

go.mod

gitea waits and keeps serving while its keys are unread; pin mesh-sdk 007b6fd

2026-10-30 00:04:14 +01:00

go.sum

gitea waits and keeps serving while its keys are unread; pin mesh-sdk 007b6fd

2026-10-30 00:04:14 +01:00

module.json

Keep the hand-act log's acts 400 days, as ADR 0565 §10 has it, now that a module log may say its age; pin mesh-sdk 2e5cc4f (issue 1953)

2026-10-29 22:18:59 +01:00

README.md

Keep the hand-act log's acts 400 days, as ADR 0565 §10 has it, now that a module log may say its age; pin mesh-sdk 2e5cc4f (issue 1953)

2026-10-29 22:18:59 +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: both logs, this one and the controller's mesh-controller_hand-acts until its lease ends, newest first, with the causes repaired by hand twice within a fortnight; warrants=true lists the warrants.

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.