188 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3c49b389d1	Playbook 09: a deletion is approved as an ask on the operator's warrant once design 58 milestone 7 is built; until then the operator runs the approved list	2026-10-16 20:51:00 +02:00
jschoubben	222fbe95f4	Playbook 09 and the hq-cleanup skill: a cleanup reads first, deletes only what the operator approves, and reports what it kept (the operator, 2026-10-16)	2026-10-16 20:01:13 +02:00
jschoubben	101d7f30f7	Playbook 02: one design per thing; a graduation rewrites the design that covers it instead of writing a second (the operator, 2026-10-16)	2026-10-16 19:40:48 +02:00
mesh-tools	152cc0c0e7	Playbook 08: a second fault the delivery shows joins the issue only in the same files ... Taken from issue 937, where mesh-catalog #335 was taken into the issue and issue 943 was opened for a fault in other code.	2026-10-16 17:06:25 +00:00
jschoubben	0eadc27fc7	Playbook 08: needing a decision keeps a fix small; a feature is several modules with research or a design before it (the operator, 2026-10-16)	2026-10-16 17:46:23 +02:00
mesh-tools	4e437eb148	Merge pull request 'Design 58: agent work as the mesh's own (graduation of research 053)' (#372) from design/58-agent-work-as-the-meshs-own into main	2026-10-16 14:09:25 +00: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	7b5f3582be	Playbooks 07 and 08: mark ready with mesh-delivery.mark-ready, label then comment in the order the forge counts (issue 913)	2026-10-16 14:31:49 +02:00
jschoubben	6dcfa2226e	Merge pull request 'Playbooks 01 and 02: place research in the domains; its words reach the glossary at graduation' (#382) from playbooks/01-place-it-in-the-domains into main ... Reviewed-on: #382	2026-10-16 12:24:26 +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	353bfdcef3	Merge remote-tracking branch 'origin/main' into design/58-agent-work-as-the-meshs-own-tmp	2026-10-16 14:00:12 +02:00
jschoubben	427fe4c9c5	Playbooks 01 and 02: place research in the domains before its direction, and carry its words into the glossary at graduation (ADR 0244) ... The operator, 2026-10-16: research defines the modules a feature lands in and the domain extensions and reductions that come with it.	2026-10-16 12:38:59 +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
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	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
jschoubben	9844020589	Glossary: Uses lines, the thread's two records, the grant from ADR 0386 §4, the provisioner's harness, issue 872 for the seat-sense role (review round 1)	2026-10-16 02:49:22 +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	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
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
jschoubben	747fc546c1	Allow a small fix three review rounds, as a feature has (playbook 08)	2026-10-15 21:28:29 +02: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
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
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
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-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-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-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-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-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-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-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
jochen	c11cb99470	Give ADR 0341 a home in design 52: the home network's SMB and NFS shares become modules' (issue 613)	2026-10-13 10:40:27 +02:00
mesh-admin	87f24d6b69	Merge pull request 'Glossary: fix time and fix budget (issue 403, ADR 0313)' (#331) from fix/403-fix-time into main	2026-10-12 19:41:36 +00:00
jschoubben	e373474db7	Give ADR 0323 its place in to-be 47, to-be 45 §9 and the glossary (issue 341) ... A merge check now judges the head merged into a named trunk commit and its verdict goes out of date when the trunk moves; the designs and the glossary say so, with the tests that hold it.	2026-10-12 17:29:59 +02:00
jochen	506d00cf74	Name fix time and fix budget in the glossary (issue 403, ADR 0313) ... ADR 0313 makes the span from the move to fixing to delivered the operator's target; the delivery budget stays a measure inside it, and its leaf figure is three minutes since ADR 0304.	2026-10-12 15:50:13 +02:00
jschoubben	56b7a9084a	Add Media as the eleventh domain, with its words (ADR 0302) ... ADR 0302 made Media a domain: content, kind, media release, library, media file, media-importer, download client, engine and grab now have one meaning each. Release already meant two things, so the Media sense is qualified in the homonyms.	2026-10-11 21:32:15 +02:00