717 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	d81c23b65a	Design 47: the operator confirmed the releases as milestones (2026-10-18); release 1-2's issues and their order	2026-10-18 17:55:21 +02:00
jschoubben	cd9336d05a	Design 47 and glossary: review round 1 (the sections stay the design until their release, rule 4's step above zero, the Approve on the phone until issue 953, release of a milestone under The record)	2026-10-18 17:48:15 +02:00
jschoubben	5c81f1170c	Design 47: the six releases of ADR 0429 as milestones, milestone 6 folded into release 4; glossary: the delivery domain, its parts and their words (ADR 0428, ADR 0429) ... Research 063 graduated into ADR 0429 and this design (playbook 02 step 3). The design names the parts and the releases; its other sections hold until each release is delivered and are rewritten as each is prepared (issue 1130). The words the plans use are marked as going at release 6, not struck: they stay true until that release is delivered.	2026-10-18 17:45:59 +02:00
jschoubben	f242b8763b	Design 47 builds with ADR 0426 (no timer where an event can end the wait)	2026-10-18 12:49:18 +02:00
jschoubben	bb6af05f5c	Playbooks 07 and 08: tests are written from acceptance criteria the larger model writes onto the issue (issue 1118); design 47 gets milestone 5b, the planning out of the controller (issue 1117)	2026-10-18 12:42:06 +02:00
jochen	05ff547358	Design 55: hq owns part of the third slice's code, its checks and links (review round 1)	2026-10-18 04:25:11 +02:00
jochen	1def984c07	Design 55: designs and the glossary become records, and the knowledge base owns a design's state (ADR 0423, ADR 0424)	2026-10-18 04:23:10 +02:00
jschoubben	19bd7fd960	Retire the word epic, and define milestone as a group of a design's issues delivered together (issue 1105) ... The operator decided on 2026-10-18 that a domain word is used only when clearly defined. epic had three uses and no code; design 47 now names two ways, hotfix and feature.	2026-10-18 04:08:15 +02:00
jschoubben	b6cf49d8ce	Design 47: milestone 3 fix names issue 1079, of which 1084 was closed as a duplicate, and the forge module it touched	2026-10-18 01:49:37 +02:00
jschoubben	24fd567c31	Design 47: milestone 4 delivered and split; a fix of milestone 3 comes next. Playbook 07: new integration tests are read against the code before the first push (issues 980, 1082)	2026-10-18 00:29:35 +02:00
jochen	21c4d212ec	Correct three facts in the designs' states (issue 1072, review round 1)	2026-10-17 22:55:02 +02:00
jochen	1bd6f4611e	Say where nine half-built designs stand (issue 1072) ... The records cleanup found them saying proposed or designed although their code is on main; each now says in-progress and what is built and left.	2026-10-17 22:53:10 +02:00
jschoubben	d5ddd1e715	Playbooks 07 and 08: no ready mark; the review record rides in the pull request and the Approve is asked once the checks pass (issue 1022, ADR 0421)	2026-10-17 20:55:47 +02:00
jschoubben	2001d6e063	Playbook 07: a milestone has steps, runs the whole unit suite, writes its findings into its issues and watches on the smaller model; design 47 names milestone 2b and takes 895 into milestone 3 (issue 1053)	2026-10-17 20:19:16 +02:00
mesh-tools	499407c669	Take in main up to 2cf1c64e24 (issue 1024) ... hq main moved after this change's check; it touches neither design 29 nor anything this change edits. The branch's tree is the reviewed design 29 change merged with main.	2026-10-17 18:09:09 +00:00
mesh-tools	4e0dd1b0d3	Say in design 29 how a folder a module owns treats files it did not write (issue 1024, ADR 0422) ... Design 29 is ADR 0422's home: it now says what `unknown` and `knows` mean on a directory under a home, that the found class no longer holds in ~/.ssh (ADR 0415, 0417), and lists ADR 0412, 0415, 0416, 0417 and 0422 among its decisions.	2026-10-17 16:23:05 +00:00
jschoubben	0b9fda46cc	Design 47: phase II release 1 delivered, 2026-10-17 (playbook 07, write-back)	2026-10-17 18:04:17 +02:00
jschoubben	b0cfd08f7c	Design 47: ADR 0420 accepted, ADR 0249 superseded, milestone 3's issues named (review of #404)	2026-10-17 17:20:16 +02:00
jschoubben	0a6613f0d4	Design 47: one plan per group, no order lines, the Approve as the only gate (ADR 0418, 0419, 0421)	2026-10-17 17:18:03 +02:00
jschoubben	85a729c607	Design 47: milestones 1 and 2 delivered, 2026-10-17 (playbook 07, write-back)	2026-10-17 15:06:38 +02:00
jschoubben	addbd74c39	Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)	2026-10-17 13:47:37 +02:00
jschoubben	6bf18062c4	Playbooks 07 and 04: a milestone is one release, never cut for size or time; milestones are cut by release order (the operator, 2026-10-17)	2026-10-17 13:47:21 +02:00
mesh-tools	0f63a73def	Merge pull request 'Describe the mesh MCP server as it runs and mark its design implemented (issue 1008)' (#400) from fix/1008-mcp-server-shipped into main	2026-10-17 11:43:03 +00:00
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	2cea6c9b0c	Date design 57's delivered milestones (issue 1009, review round 2)	2026-10-17 13:35:56 +02:00
jochen	79dcc0a6ec	Give design 57 its milestones and check every write-back moment (issue 1009, review round 1)	2026-10-17 13:35:20 +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
jochen	b83a1e748e	Playbook 07: the lead writes a design's state back (issue 1009) ... Design 57 was merged as a release with three tasks left and still said designed, so another session took it for unbuilt. Say it in-progress, with what is left and when it is built.	2026-10-17 13:33:37 +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