2045 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jschoubben	1ddc2f5cbf	Merge pull request 'Design 41: every file on a node is managed through node-files (WP9, ADR 0394)' (#380) from design/41-node-files into main ... Reviewed-on: #380	2026-10-16 12:24:18 +00:00
jschoubben	06998cc8d9	Merge pull request 'Playbooks 07 and 08: the five rules from the delivery-time audit' (#375) from playbooks/07-08-time-sinks into main ... Reviewed-on: #375	2026-10-16 12:24:07 +00: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	1efa37957d	Playbooks 07 and 08: is the coast clear? Hold a push while a release branch in flight shares its files; the glossary's release branch ... The operator, 2026-10-16: the file module waited for feature 57's release branch, which changes four of the same controller files.	2026-10-16 11:28:32 +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
mesh-tools	b9af4e373d	Merge pull request 'Feature 57 (config and provisioning): release hq's record' (#378) from release/57-config-and-provisioning into main	2026-10-16 08:41:58 +00:00
mesh-tools	e7417cf124	Feature 57 (config and provisioning): release hq's record (glossary words, release notes) on top of main	2026-10-16 08:24:14 +00:00
jschoubben	47f7321c05	Playbooks 07 and 08: integration tests only in the merge check, no try before it, no lab and no end-to-end tests yet (the operator, 2026-10-16)	2026-10-16 10:15:31 +02:00
jschoubben	f95043e379	Playbooks 07 and 08: a module's acceptance is an integration test the forge runs, and try runs on the builder (ADR 0391)	2026-10-16 10:14:42 +02:00
jschoubben	cb98a08384	Playbooks 07 and 08: prove a module whole on a throwaway bus and store, not in the lab while its runs are too slow (the operator, 2026-10-16)	2026-10-16 10:14:25 +02:00
jschoubben	4e822c56a0	Playbooks 07 and 08: checks for every new rule, the ready mark's bound in both, the lead marks an unreviewed edit (review round 1)	2026-10-16 10:14:25 +02:00
jschoubben	c5fa1de264	Playbooks 07 and 08: review asks only what makes a change wrong, try before opening, mark ready on approval, prove a module whole first, hand back stopped issues ... From the delivery-time audit of 2026-10-16: seven review rounds on issue 704, a feature branch's first check failing on 29 problems, mesh-catalog #300 waiting 12 h unmarked, the mail modules failing live, 98 issues held in fixing.	2026-10-16 10:14:25 +02:00
jschoubben	ea359ea4e6	Try a small fix's branch before its pull request, since local runs miss the check's toolchain (playbook 08)	2026-10-16 10:14:25 +02:00
mesh-tools	c22b58143b	Merge pull request 'Test levels and time budgets in how-we-build and playbooks 07 and 08 (issue 891, ADR 0391)' (#374) from fix/891-test-levels-and-budgets into main	2026-10-16 08:13:26 +00:00
mesh-tools	d9dd8a63d8	Say ADR 0391's test levels and time budgets in how-we-build and playbooks 07 and 08 (issue 891)	2026-10-16 08:09:33 +00:00
mesh-tools	08d6476e52	Merge pull request 'Playbooks 01, 02 and 04: settle decisions before versions, test at the cheapest level, acceptance tests through to milestones' (#371) from playbooks/01-settle-before-versions into main	2026-10-16 00:15:00 +00:00
jschoubben	80b647a2ed	Name the acceptance tests in the milestone table and say what the review returns (review round 2)	2026-10-16 02:12:17 +02:00
jschoubben	a4c5ef69bb	Give the build's acceptance tests a home in the design and milestones, and answer review round 1 ... The research playbook named acceptance tests the milestones carry, which playbooks 02 and 04 did not know; its pre-check also disagreed with the knowledge base's deferral rule.	2026-10-16 02:11:27 +02:00
jschoubben	ada703e790	Write a graduation's records side by side, from the confirmed direction (playbook 02) ... Proposing records one after another serialises their reviews and the operator's asks; retyping the effort's findings into each record makes them long and gives the review more to send back.	2026-10-16 02:09:57 +02:00
jschoubben	2a61c57258	Settle research decisions before proposing versions, and test on the cheapest bed (playbook 01) ... Research 053's identity part took six versions and about two hours: options that broke the mesh's own rules were offered and argued back, a version was proposed after every answer, and reviews returned findings a pre-check would have caught. A lab run was planned where an in-process test answered.	2026-10-16 02:09:22 +02:00
mesh-tools	f8c0676b3a	Merge pull request 'Cite ADR 0382 in the delivery design (issue 867)' (#370) from fix/867-group-siblings into main	2026-10-15 23:52:50 +00: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
mesh-tools	9bfd57174f	Merge pull request 'Playbook 08: a small fix may cover two or three related issues in one repository' (#368) from playbooks/08-related-issues into main	2026-10-15 20:38:39 +00:00
jschoubben	a227f98bdd	Let a small fix cover two or three related issues in one repository (playbook 08)	2026-10-15 22:37:12 +02:00
mesh-tools	409fa9bbc9	Merge pull request 'Playbook 08: a small fix gets three review rounds, as a feature does' (#367) from playbooks/08-three-rounds into main	2026-10-15 19:29:07 +00:00
jschoubben	747fc546c1	Allow a small fix three review rounds, as a feature has (playbook 08)	2026-10-15 21:28:29 +02:00
mesh-tools	046bbd3b30	Merge pull request 'Playbooks 01, 02 and 04: one cycle from idea to delivered milestones' (#366) from playbooks/01-02-04-the-cycle into main	2026-10-15 19:23:08 +00:00
jschoubben	99243ec47e	Confirm milestones before opening their issues, name issue 845 for the check, keep 01's withdrawal and history lines	2026-10-15 21:19:01 +02:00
jschoubben	0d66edb24c	Make playbooks 01, 02 and 04 one cycle from idea to delivered milestones ... The operator found 04 odd on 2026-10-15: it went from a settled design straight to building, with no work breakdown, and contradicted playbook 07 on pull requests. 01 now starts from the operator's idea with setup questions, findings and a direction the operator confirms; 02 graduates that direction into one record per reversible choice and hands the design on; 04 breaks it into milestones usable on their own, one issue per repository part, each milestone one feature step of 07. 01 notes the knowledge base's insight-only rule for an active effort until issue 844 is delivered.	2026-10-15 21:18:15 +02:00
mesh-tools	5ff97ec3aa	Merge pull request 'Say rollout, not walk (issue 646)' (#365) from fix/646-rollout-not-walk into main	2026-10-15 17:59:22 +00:00
jschoubben	75ac87c72b	Merge remote-tracking branch 'origin/main' into fix/646-rollout-not-walk	2026-10-15 19:57:54 +02: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
mesh-tools	058d76ee8a	Merge pull request 'Playbook 07 as five bounded phases with reused context; playbook 08 for small fixes' (#364) from playbooks/07-08-fast-flow into main	2026-10-15 17:54:22 +00:00
jschoubben	db6430ccbf	Show the report's issues as a tree, and keep the agent's brief, the red-check rule and the forge-commit check, in playbook 07	2026-10-15 19:52:48 +02:00
jschoubben	458f248c05	Give the lead's ten-minute report a full and a short layout, in playbook 07	2026-10-15 19:52:31 +02:00
jschoubben	464833d0ef	Rewrite playbook 07 as five bounded phases with reused context, and add playbook 08 for small fixes ... A feature waited a day for its last issue, each small issue paid for its context again, and waits nobody saw cost the most time. The operator set the flow on 2026-10-15: prepared context per repository, one to two hours of local development on unit tests, one review of at most three rounds back to the same agents, one push for the integration checks, then the delivery plan; steps for a larger feature; a separate playbook for small fixes; models per step; a wait list with bounds; a prepared clear at each phase end.	2026-10-15 19:26:02 +02:00
mesh-tools	99a9da0950	Merge pull request 'Add three lessons from feature mail-hardening to playbook 07' (#363) from playbook-07-lessons into main	2026-10-15 15:14:16 +00:00
jochen	de8a7176ab	Add three lessons from feature mail-hardening to playbook 07 ... A temporary-directory quota failure, a delivery group's manifest-check ordering, and an agent that stops or finishes without committing each cost time during that feature because the playbook did not yet say what to do. Writing them down so the next feature avoids the same detours.	2026-10-15 17:08:43 +02:00
mesh-tools	a7d4c39535	Merge pull request 'Playbook 07: an issue is one repository and five to ten minutes; a long run says where it stands' (#362) from pb07-issue-size into main	2026-10-15 12:40:48 +00:00
mesh-toolsandClaude Opus 5.5	048f14540a	Size an issue for one repository and five to ten minutes, and have a long run say where it stands, in playbook 07 ... On 2026-10-15 issues spanning one repository finished in two to four minutes, while those spanning two or three ran for thirty to sixty, mostly merging the feature head and checking again as other agents landed. The operator asked for agents that finish in five to ten minutes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-15 12:37:33 +00:00
mesh-tools	c2ee44255e	Merge pull request 'Playbook 07: the ready note and the brief a fixing agent follows' (#361) from pb07-agent-brief into main	2026-10-15 12:33:46 +00:00
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