2000 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
mesh-toolsandClaude Opus 5.5	ddf23a7861	Put the ready note and the brief a fixing agent follows into playbook 07 ... They lived in a file on one machine that only one session's agents read. They are how every feature's agents work, so they belong with the method; a feature keeps only its local facts (paths, branch, locks). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 12:33:00 +00:00
mesh-tools	f3bbfd4bf6	Merge pull request 'Playbook 07: up to five Sonnet agents at once, at most two on the larger model' (#360) from pb07-five-agents into main	2026-10-15 12:02:56 +00:00
mesh-toolsandClaude Opus 5.5	893d90fb41	Allow up to five Sonnet agents at once and keep the larger model to two, in playbook 07 ... The operator, 2026-10-15: the smaller model is as good as free against the weekly allowance, so the limit that matters is how many agents the lead can settle and follow (three to five); subagents on the larger model stay at two at most and as rare as possible. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 12:00:09 +00:00
mesh-tools	1e577168bf	Merge pull request 'Playbook 07: three to five review rounds, the reviewer told its round, and the allowance in every report' (#359) from pb07-review-rounds into main	2026-10-15 11:22:56 +00:00
mesh-toolsandClaude Opus 5.5	f349c940f0	Cap review rounds at three to five and report the allowance used, in playbook 07 ... A reviewer that does not know its round keeps finding the next smaller thing: one decision record went through nine rounds on 2026-10-15, each spending the operator's shared weekly allowance. The operator asked for three to five rounds, the round told to the reviewer, and the allowance in every report. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 11:21:37 +00:00
mesh-tools	1699375476	Merge pull request 'Playbook 07: the lead settles an issue's questions before a smaller-model agent builds it, two at a time' (#358) from pb07-builders into main	2026-10-14 23:26:01 +00:00
mesh-toolsandClaude Opus 5.5	912fd428fb	Have the lead settle an issue's questions before a smaller-model agent builds it, two at a time ... Five agents at once, each stopping on an undecided design question and restarting, spent a week's allowance in a night. Also write down the lessons of feature 57: never land on a red check, a new manifest word lands with the controller that reads it, and review the tree that is pushed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 23:24:14 +00:00
mesh-admin	a75faad882	Merge pull request 'To-be 42: the kernel module holds the kernel's run-time settings, huge pages first (ADR 0369, issue 746)' (#357) from design/42-kernel-module-holds-runtime-settings into main	2026-10-14 21:52:48 +00: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
mesh-admin	93f8bbfc8e	Merge pull request 'To-be 48: cite ADR 0368, the resolver restarts itself for that module alone' (#356) from design/48-cites-adr-0368 into main	2026-10-14 21:29:04 +00: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
mesh-admin	010a34cc33	Merge pull request 'To-be 08: the five connectivity contexts walked through the network layers' (#275) from design/connectivity-through-the-layers into main	2026-10-14 21:14:49 +00:00
mesh-admin	35d5b2814f	Merge pull request 'Playbook 07: review the local commits before anything is pushed' (#355) from playbook-07-review-before-push into main	2026-10-14 21:12:20 +00: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	6c8532ce70	Review the local commits before anything is pushed ... A push starts the forge's checks, which build the modules and run every test for up to a quarter of an hour, so a review finding fixed after the push costs another full run (the operator, 2026-10-14). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 20:03:11 +00:00
mesh-admin	c032cae100	Merge pull request 'Playbook 07: how several agents work one feature on one branch' (#354) from playbook-07-parallel-issues into main	2026-10-14 19:55:30 +00:00
mesh-adminandClaude Opus 5.5	071fc1c29d	Name the lead, and have it take over a finished issue ... A finished issue's agent is gone, so left in fixing it goes stale; the lead takes it over until the feature is delivered. One repository is one delivery, not a group; readiness comes from depends-on links (review comment 12466). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:53:20 +00:00
mesh-adminandClaude Opus 5.5	c2d5323dea	Say how several agents work one feature on one branch ... Feature 57 was first worked as a pull request per issue into protected branches and lost most of a day waiting on merge checks. Record the issue as the unit, a review and checks once at the end, landing by fast-forward under a lock, and the lessons met on the way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 19:50:14 +00:00
mesh-admin	21b79a04a2	Merge pull request 'Fit design 57 to walks with no first-machine gate (ADR 0360, ADR 0362)' (#353) from design/57-adr-0360 into main	2026-10-14 18:15:22 +00: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
mesh-admin	dcb5d5ce38	Merge pull request 'To-be 45: the bus module says every user's slow consumer, and S9 raises it (issue 270, ADR 0357)' (#352) from design/270-the-bus-module-says-every-users-slow-consumer into main	2026-10-14 07:00:14 +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-admin	40a39c8602	Merge pull request 'To-be 57: building config and provisioning, as 37 packages each an issue (ADR 0348, ADR 0349)' (#350) from design/57-building-config-and-provisioning into main	2026-10-13 23:57:18 +00: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
mesh-admin	fd416cef91	Merge pull request 'To-be 47: a busy container on the first node holds only its walk, and the wait counts (ADR 0335, issue 594)' (#349) from design/335-a-busy-container into main	2026-10-13 22:21:01 +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
mesh-admin	c2a7016b62	Merge pull request 'To-be 47: a change is built once, at its check (ADR 0350, issue 649)' (#348) from design/350-one-build-per-change into main	2026-10-13 21:30:32 +00: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
mesh-admin	3a0b33501d	Merge pull request 'Design 27: a served own name with a default, or nested, is refused too (ADR 0346, review 224)' (#347) from design/624-a-served-name-takes-no-default into main	2026-10-13 19:22:05 +00:00
mesh-admin	ed63ca8f68	Merge pull request 'To-be 46: an ask reads at a glance, and its values are whole where the sender is proven (ADR 0345, issues 383 and 639)' (#344) from design/639-an-ask-reads-at-a-glance into main	2026-10-13 19:02:17 +00:00
jochen	de3b61217a	To-be 46: say ADR 0347 as it is decided (the review of #344): no overclaim, and the note is cut last, not never	2026-10-13 20:35:37 +02:00
jochen	327f7bc55c	To-be 46: every value an approval sets is in the ask's note (ADR 0347, issue 383)	2026-10-13 20:35:37 +02:00
jochen	6bf56ea5c9	To-be 46: an ask reads at a glance, and its values are whole where the sender is proven (ADR 0345, issues 383 and 639) ... The operator would not read the Telegram asks: the ADR 0343 ask was thirty plain lines, a settings proposal a wall of masked values. The design takes ADR 0345: the asker's summary and points are the body, everything else a note the channel shows apart, and an ask's values whole on a proving channel.	2026-10-13 20:35:37 +02:00
mesh-admin	f7b4133e59	Merge pull request 'To-be 27: a provider may serve its own composed names (issue 624, ADR 0346)' (#345) from design/624-a-provider-serves-its-own-names into main	2026-10-13 18:33:45 +00:00
jochen	2a27c38beb	Design 27: a served own name with a default, or nested, is refused too (ADR 0346, review 224)	2026-10-13 20:33:28 +02:00
mesh-admin	0f5aab10b4	Merge pull request 'To-be 46: an approved settings change is sent at once (issue 641, ADR 0344)' (#346) from design/641-an-approved-setting-is-sent into main	2026-10-13 15:27:03 +00:00
jochen	732e8bd4d9	Design 46: a settings walk sends the layer and no build, and stops before a data move (ADR 0344 v4)	2026-10-13 16:50:09 +02:00
jochen	417a50d06c	Give ADR 0344 a home in design 46: an approved settings change is sent at once (issue 641)	2026-10-13 16:40:29 +02:00
jochen	a54b1eaab9	Give ADR 0346 a home in design 27: a provider may serve its own composed names (issue 624)	2026-10-13 16:40:09 +02:00
mesh-admin	471f99344b	Merge pull request 'Design 36 §12: the names a memory value may carry (issue 367, ADR 0343)' (#343) from design/367-memory-names into main	2026-10-13 14:26:55 +00:00
jschoubben	d70c189ed2	Design 36 §12: say which project and path names a memory value may carry (issue 367, ADR 0343)	2026-10-13 16:20:14 +02:00
mesh-admin	e7ebafad1a	Merge pull request 'To-be 36: a session's memory follows the operator (issue 367, ADR 0343)' (#342) from design/367-memory-follows-the-operator into main	2026-10-13 14:14:11 +00:00
jochen	319c210624	Design 36 §12: a node that was away takes the newest memory, and two large versions are kept in two files (ADR 0343 as reviewed)	2026-10-13 16:03:37 +02:00
jschoubben	213987b2cc	Give ADR 0343 a home in design 36: a session's memory follows the operator (issue 367)	2026-10-13 15:57:55 +02:00