Files

T

jschoubben 06ebd7e8cf G findings: the writers name the ask's subject from the contract; the readers take the writer whole

WriterConfig.Asked is the generated mesh-conditions contract's SubjectFindingsAsked (A-17), a reader's Findings is the
module's writer itself (A-22, A-26), and mesh-build-go's single manifest ask writes and clears its first-view-unanswered
finding through the writer with the contract's Finding (A-28). mesh-config and mesh-vault's own followers (A-28) are not
yet moved onto a views.Reader: they do not compile at mesh-sdk 24f876a.

Builds: design 47 G §687, §689, A-17, A-22, A-26, A-28

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

2026-11-11 22:03:09 +01:00

cmd/mesh-watcher

G findings: the writers name the ask's subject from the contract; the readers take the writer whole

2026-11-11 22:03:09 +01:00

files

Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main

2026-10-16 09:42:45 +00:00

go.mod

G findings: the view-only modules write their reader's findings through mesh-sdk's stdio writer

2026-11-11 21:46:49 +01:00

go.sum

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

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

module.json

OBS4: artifact-store-tools, mesh-watcher, minio and nfs-server ask findings and finding-events in requires

2026-11-11 15:48:35 +01:00

README.md

Every module follows the assigner's new places: the contracts' go/ path, mesh-wants in the delivery contracts, the state and tool assignments (issue 1966)

2026-11-05 22:29:07 +01:00

README.md

mesh-watcher

The watcher's watcher (novox/hq to-be 45 §5, signal S10, ADR 0227 rule 6): what tells the operator when the parts that would tell them are what failed.

Assigned to one machine that is not the control node. It reads where the bus runs (the seat mesh-broker's holders, from the assignments seat's state of who holds which seat) every ten minutes; on the same machine its status says MISPLACED.
Watches two signals.
- The self-check: the seat mesh-self-check's checked event. Bound: twice the interval the heartbeat says doctor runs at (five minutes when it says none). Heard by the time the heartbeat says it was made, so a backlog delivered after a restart is not a sign of life. The heartbeat is read in one place, cmd/mesh-watcher/heartbeat.go, which states every assumption it makes about its shape.
- The bus: a round trip through the bus server — its own watcher_ping on its own machine — every minute. Bound: three minutes.
Silent past its bound: it sends to Telegram directly over HTTPS, not through the bus, once; once more an hour later if still silent; and again when the signal returns. Before a signal is first heard it counts from the watcher's start: a heartbeat that never comes is what this is for.
Its own health is visible: watcher_status leads with whether it can tell the operator anything at all (BLIND without a token or chat id, or while Telegram fails), whether it is misplaced, and whether heartbeats reach it. A message it could not send is owed and tried every minute.

What the operator gives

The bot token, as this module's own secret: secret accept <machine> mesh-watcher telegram-token, then push that machine. The same bot as the operator-channel's is fine; it is one more machine holding it (ADR 0227, accepted for this one case).
The chat id, as a setting: settings for mesh-watcher with {"telegram-chat-id": "<id>"}.

Tools

tool	does
`watcher_status`	its own health, then each signal: last heard, bound, silent, owed
`watcher_last_heard`	when each signal was last heard, and what it sent lately
`watcher_test`	a test message to Telegram now, directly
`watcher_ping`	the bus round trip's other end

Files it does not know

Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).

${dir:state}: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).