Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
JavaScript agentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentsoftware-factoryspec-driven-developmentverificationvibe-coding
docs: drop a private machine name and a dated quote [C7]
Corey Olson22b298341b9c
diff --git a/docs/architecture.md b/docs/architecture.mdindex 9f9da78d..f7af4990 100644--- a/docs/architecture.md+++ b/docs/architecture.md@@ -132,7 +132,7 @@ The relay never receives a board key in a form it can use. A phone gets it wrappA relay canary is an opt-in monitor on an ordinary client machine. It checks the authenticated board move path by signing in as its configured ordinary seat, sending a nonce-bearing shout through the normal ordered move, pulling the fresh event and unsealing the exact returned move. A successful `/health` response alone is not a round trip. The canary does not alter the relay API or add a server-side table.-`pullboard relay canary on [--timeout <milliseconds>]` stores `relay.canary` in this machine's settings: an enabled flag, an absolute checkout path, the registered non-coordinator `agentId`, and an optional deadline (5 seconds by default; 100–25,000 ms when set). The credentials stay in the existing local link and key stores. The setting binds the run to that checkout and seat. To monitor the dedicated board from Studio and MacBook, link that board normally on each non-relay host and configure one ordinary seat per machine after the feature lands. `pullboard relay canary off` disables an existing setting (or leaves an absent setting unset); `status` reads local observations without a network request; `run` executes one probe; `watch` runs an immediate probe and then checks once per minute until stopped with Ctrl-C. The watch is separate from the ordinary ten-minute health scan.+`pullboard relay canary on [--timeout <milliseconds>]` stores `relay.canary` in this machine's settings: an enabled flag, an absolute checkout path, the registered non-coordinator `agentId`, and an optional deadline (5 seconds by default; 100–25,000 ms when set). The credentials stay in the existing local link and key stores. The setting binds the run to that checkout and seat. To monitor one board from two machines, link that board normally on each and configure one ordinary seat per machine after the feature lands. `pullboard relay canary off` disables an existing setting (or leaves an absent setting unset); `status` reads local observations without a network request; `run` executes one probe; `watch` runs an immediate probe and then checks once per minute until stopped with Ctrl-C. The watch is separate from the ordinary ten-minute health scan.Each machine keeps its observations and minute schedule in a private SQLite file at `<git common dir>/pullboard/relay-health.sqlite`. A fresh result is healthy or degraded; after two minutes without a recent sample, status is unknown. Two consecutive failed probes create an alert. A latency alert requires a complete ten-minute window and at least ten successful samples, with p95 above two seconds. The local Needs-you entry reports the actual queued move count from that machine's outbox. It is local telemetry: it is not included in sealed board presentations or sent to other devices as health state.diff --git a/docs/contributing-runbook.md b/docs/contributing-runbook.mdindex c0f52ce5..0fb813c6 100644--- a/docs/contributing-runbook.md+++ b/docs/contributing-runbook.md@@ -1,6 +1,6 @@# Procedure: handling an outside contribution (maintainers and the coordinator)-Approved direction from the person, 22 Oct 2026. This is the internal runbook. Contributors read CONTRIBUTING.md; this file is for us.+This is the internal runbook. Contributors read CONTRIBUTING.md; this file is for us.## When an issue arrives1. Reply when capacity allows: thank them, and say what happens next ("on our board as #N", "a question first", or "not planned, because...").