691 Commits

Include renames

Author	SHA1	Message	Date
jochen	f6199fafce	As-is 13: fix five review findings on the mesh MCP server (issue 1008, review round 1) ... node-tools still has a manifest (invokes *, waits, the mcp-endpoint provision) — describe it in prose instead of saying it has none. The TypeScript sources remain on main; only the built artifact is Go. The mesh-controller seat answers 63 verbs as its own runtime, not 60-93 per node (that is node-tools' own node-scoped seat verbs). Prefer reading mesh_overview live over a count that drifts. An as-is document amends nothing — reworded accordingly.	2026-10-17 13:39:14 +02:00
jochen	65f69d96a9	Describe the mesh MCP server as it runs and mark its design implemented (issue 1008) ... mesh-console is gone: the tool runner (node-tools) is a core component on every node, host-side and never a container (ADR 0175), announcing seven tools by address (ADR 0195, 0367), not the five-tool container the old as-is doc described. The to-be document's unsettled items get owners: the mesh's own verbs already shipped (ADR 0154); identity and per-assignment grants are design 58 milestone 6 (issue 883).	2026-10-17 13:35:12 +02:00
mesh-tools	0a010b8b79	Design 58: milestone 13 does not wait for milestone 7; until then nox's dangerous acts are refused (review round 1 of #396)	2026-10-17 10:17:00 +00:00
mesh-tools	cc0503ef66	Design 58 and 36: role names for the machines and no operator logins, as a public repository needs (fixes what #394 wrote)	2026-10-17 10:13:02 +00:00
mesh-tools	56d8d546c7	Design 58: milestones 11 to 14 from research 057 with their issues, and as-is 17 on today's accounts (playbook 04)	2026-10-17 10:10:42 +00:00
mesh-tools	0dc8cab178	Design 58 and 36: cite ADR 0266's ways to root, and make acceptance tests 7 and 9 and the nox glossary entry agree with ADR 0411, 0412 and 0414 (review round 1)	2026-10-17 09:40:48 +00:00
mesh-tools	98b731d5d1	Design 58 and 36: identities carry logins, run for an identity, a bus password per identity (ADR 0411 to 0414, research 057)	2026-10-17 09:35:37 +00:00
jschoubben	24701df23e	Merge branch 'main' into feat/agents-write-git-ssh	2026-10-16 22:27:02 +00:00
jschoubben	748641dd22	Review of #393: rollouts run one at a time today (issue 525); Approve on Telegram (issue 953 for the terminal); 976's place in the order; milestone 1 takes the rest of 525 and acceptance test 9	2026-10-17 00:06:59 +02:00
jschoubben	b6a191d0a6	Design 47's milestones and issues (playbook 04), and the as-is delivery rewritten from research 055's findings ... The operator confirmed six milestones on 2026-10-17; issues 973-981 and 971 carry their repository parts, linked depends-on in order. The as-is described the predecessor's pipeline; it now says what runs today, which design 47 replaces.	2026-10-17 00:04:00 +02:00
jschoubben	aa4bfe289e	Design 47 and the glossary: the reviewer's findings (three work queues, a feature in one repository, what-if, ADR 0406 clause numbers, backups by protection, no suite-time claim, the Go module's judge account)	2026-10-16 23:44:59 +02:00
jschoubben	6f0db74ee4	Design 47: the SDK commits the catalogue accepts (ADR 0402 §4)	2026-10-16 23:42:56 +02:00
jschoubben	e7854a31a6	Design 47: a member naming the SDK member's head is proven by its own merge check (ADR 0402's review)	2026-10-16 23:41:37 +02:00
jschoubben	8bfb11da2c	Design 47 and the glossary: the batch's record in the chain is the rollout (ADR 0408's review)	2026-10-16 23:40:11 +02:00
jschoubben	96f2ae72c1	Rewrite design 47 from research 055's decisions: hotfix, feature and epic from the trunk, delivery on the bus ... ADR 0401-0408 graduate research 055: no release branch, two more ordering rules, the composed check as each member's gate, a backup before the send, installed toolchains, events and work queues on the bus, the merge window as keys, and one chain kept on the bus alone. Design 47 is rewritten from them (one design per thing); the glossary takes hotfix, feature, toolchain, milestone and epic and retires release branch; design 18 loses the toolchain image; playbooks 07 and 08 drop the release-branch wait.	2026-10-16 23:39:12 +02:00
nox	fa5fd9fc69	Cite ADR 0399 and 0400 in design 29: the account's forge key lives in ~/.ssh (issue 955)	2026-10-16 22:37:15 +02:00
jschoubben	12e75cdfa2	Design 47: the transition paragraph, the recheck verb and the section's bullets say ADR 0395 whole (review)	2026-10-16 19:27:52 +02:00
jschoubben	377fa3f88a	Design 47: say ADR 0395 as accepted — a conflict is asked again at every move, an ended check's builds are not reused, a group's composed check reruns through its members, and the cost bound	2026-10-16 19:26:47 +02:00
jschoubben	11e32ce5be	Merge remote-tracking branch 'origin/main' into design/47-recheck-on-trunk-move	2026-10-16 19:26:35 +02:00
jschoubben	18428baf4b	Merge remote-tracking branch 'origin/main' into design/58-agent-work-as-the-meshs-own	2026-10-16 14:53:11 +02:00
jschoubben	91f82cd38e	Design 47: a group's own merge in order asks nothing again (ADR 0395 §1, review)	2026-10-16 13:32:39 +02:00
jschoubben	300be92814	Design 41 WP9: readlink and the account and group lookup are node-files verbs too (ADR 0394 §1; review)	2026-10-16 13:31:45 +02:00
jschoubben	a65e1076a2	Design 47: a pull request that no longer merges cleanly is told, not checked (ADR 0395 §2)	2026-10-16 11:42:03 +02:00
jschoubben	09ec150bd6	Design 47: a move of the trunk asks every active check again, one at a time per pull request (ADR 0395, issue 888)	2026-10-16 11:40:14 +02:00
jschoubben	26073f30b0	Design 41: node-reads goes in the delivery after node-files is held on every node (ADR 0394 §9)	2026-10-16 11:14:01 +02:00
jschoubben	1f5a12e07e	Design 41: WP8's node-reads is replaced by WP9's node-files (ADR 0394 supersedes ADR 0310)	2026-10-16 11:11:53 +02:00
jschoubben	7ac5194bcb	Design 41 WP9: mesh-files runs as the operator account with sudo where needed, and replaces node-reads (ADR 0394)	2026-10-16 11:06:32 +02:00
jschoubben	330d341618	Design 41 WP9: node-files is held by a module of its own, mesh-files, beside mesh-reads	2026-10-16 11:01:43 +02:00
jschoubben	cf56649845	Design 41: every file on a node is managed through node-files (WP9, ADR 0394, issue 900)	2026-10-16 11:00:46 +02:00
jschoubben	43c3f2c098	Design 58: the operator confirmed the milestones; issues 878 to 887, building after design 57's delivery (playbook 04)	2026-10-16 09:55:11 +02:00
jschoubben	45e2d7e972	Design 58: milestones for the operator to confirm, owners named, and the as-is of logins on the bus (playbook 04)	2026-10-16 03:03:21 +02:00
jschoubben	535fd8bb54	Glossary: the words of research 053's graduation, and harness and role as homonyms ... Playbook 02 adds a graduated effort's words; design 58 now says agent harness, never the bare word.	2026-10-16 02:47:48 +02:00
jschoubben	cb4c18cedc	Design 58: the identity store is read by grant, and sessions never call through the tool runner's login (review round 1)	2026-10-16 02:45:58 +02:00
jschoubben	8f8f1b4337	Design 58: agent work as the mesh's own, graduated from research 053 with ADR 0383 to ADR 0390 ... Threads on the bus, a headless thread handler in a sandbox per session, a workspace toolkit with no general command runner, one identity seat, effects on every tool, signed bus logins and the switch to them; names the build's acceptance tests for the milestones.	2026-10-16 02:44:15 +02:00
mesh-toolsandClaude	e4a55051cc	Cite ADR 0382 in the delivery design: a group's member is checked beside its siblings (issue 867) ... Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-15 23:27:14 +00:00
jschoubben	437523554e	Say rollout, not walk, for the sending of a batch across nodes (issue 646)	2026-10-15 19:57:20 +02:00
jschoubben	9f4757a8e4	Let the kernel module hold the kernel's run-time settings, huge pages first (ADR 0369, issue 746) ... Huge pages at always flooded the control-node's spinning disks with journal write-back and cost the controller its lease; the setting needs an owner, and the kernel module is the one to-be 42 already names for the kernel.	2026-10-14 23:48:35 +02:00
jschoubben	58edc4b4fb	Cite ADR 0368 in design 48: the resolver restarts itself, for that module alone ... Redoes the design-48 edit of the unmerged pull request 284, which cited the record under its file number 0280; the record now lives in the knowledge base as ADR 0368.	2026-10-14 23:18:38 +02:00
jschoubben	3c5edc3879	Cite decisions by number now that they live in the knowledge base, and date the design today	2026-10-14 23:12:18 +02:00
jochen	ab5025d508	Connectivity: walk the five contexts through the network layers, so a reader can see which layer each one acts at and read a failure from the bottom up	2026-10-14 23:11:53 +02:00
mesh-adminandClaude Opus 5.5	bafc7b7d05	A silent machine is caught up by the backlog walk, not fixed forward ... A machine that says nothing is often asleep; its builds wait for the backlog walk (ADR 0360 clause 10), so no new pull request is needed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 18:12:52 +00:00
mesh-adminandClaude Opus 5.5	5e493934a5	Say the rehearsal is the only live check, and that a fix goes into main ... The pull requests' checks still run before the walk, and by then the release's branches have reached main. Name the silent machine too, and list ADR 0360, which the passages rest on (review comment 12348). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 18:11:52 +00:00
mesh-adminandClaude Opus 5.5	c957fcc6d7	Fit design 57 to walks with no first-machine gate ... ADR 0360 sends a merge's builds to every machine at once, so release 57 has no first node to hold it and P6 can no longer wait at a gate. ADR 0362 moves the wait for the provisioner to the walk's end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 18:09:02 +00:00
jochen	bb8075b37b	Give ADR 0357 a home in design 45: the bus module says every user's slow consumer, and S9 raises it (issue 270)	2026-10-14 08:42:54 +02:00
mesh-adminandClaude Opus 5.5	e5b98e3b0a	Design 57: answer the second review of hq#350 ... The word setting waits for R2, P3 waits for F3, the group's order is declared with after: lines, and a stop's fix is a new merge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:53:59 +00:00
mesh-adminandClaude Opus 5.5	2f3e6e6641	Design 57: answer the review of hq#350 ... Role names instead of node names, the failure rule as ADR 0276 and 0299 have it, readiness and adoption of existing credentials said exactly, and the counts and refusals corrected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:47:32 +00:00
mesh-adminandClaude Opus 5.5	1405dd39e8	Design 57: ship the packages as one release, rehearsed in the lab ... The operator chose one delivery over one per package; the packages meet on one branch per repository and reach main as one delivery group. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:40:15 +00:00
mesh-adminandClaude Opus 5.5	11294372b7	Design 57: the work of ADR 0348 and ADR 0349 as packages, each an issue, in dependency order ... So config and provisioning are built in small, provable steps with at most five worked at once. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:12:23 +00:00
jschoubben	74e45e9b48	Merge remote-tracking branch 'origin/main' into design/335-a-busy-container ... # Conflicts: # 03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md	2026-10-14 00:12:11 +02:00
jschoubben	18ce19b85d	To-be 47: a change is built once, at its check (ADR 0350, issue 649) ... The design the decision lands in did not name it, so the knowledge base could not accept the record's insight with nothing citing it.	2026-10-13 23:18:20 +02:00