183 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4315bb6307	A subagent works from hq; a coding one in a worktree under hq's .work, also reading its repository's conventions (the operator, 2026-11-03)	2026-11-03 12:46:24 +01:00
jschoubben	e8c154c3a0	Agent definitions: the developer on the smaller model unless the lead says why; review notes	2026-11-03 12:15:48 +01:00
jschoubben	d829fd6f9b	Playbook 02: name no record in the seams rule	2026-11-03 12:14:48 +01:00
jschoubben	10df1c7be5	Playbooks overview: agents from hq's definitions; the seams review of every prepare	2026-11-03 12:14:25 +01:00
jschoubben	8420c6f236	Agents work from hq's definitions and start from the knowledge base; every prepare and record gets the seams review (the operator, 2026-11-03)	2026-11-03 12:14:12 +01:00
mesh-tools	92fa66f4e7	Merge pull request 'A research effort's reading tasks run on one agent definition, research-reader' (#504) from docs/research-reader into main	2026-11-03 00:51:58 +00:00
jschoubben	3a3501d9f4	Playbook 07 and design 47: say how the two new rules are checked; glossary words; name where the bus module has no want ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 00:58:19 +01:00
jschoubben	5d9a654767	Playbook 07: run every suite as the running checker places it, and let the running parts judge a release that changes them (issue 1126, release sdk1) ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-03 00:52:28 +01:00
jschoubben	1a389be090	A research effort's reading tasks run on one agent definition, research-reader, instead of a prompt written by hand each time	2026-11-03 00:28:06 +01:00
jschoubben	121b582ebc	Four reviewer agents carry playbook 01's review by architectural domain, two architectural domains each, so every review asks the same questions	2026-11-02 19:38:35 +01:00
jschoubben	6f2bacf6c4	Architectural domain for the review's eight concerns, and the glossary's domain qualified as mesh domain in the homonyms, as the operator chose on 2026-11-02	2026-11-02 19:21:48 +01:00
jschoubben	f5624e7d9f	Review fixes: the research skill names sections by title, the drawn overview's order and bounds follow the playbooks, an amended design is reviewed by aspect, and storage forms use glossary words	2026-11-02 18:20:12 +01:00
jschoubben	b861b3ae36	Glossary: review aspect; playbook 01: a piece of state takes the bus storage form that fits it, and a form added to mesh-sdk is named to the operator with its cost	2026-11-02 18:19:05 +01:00
jschoubben	0ac621e03f	Playbooks 01 and 02: review a direction and a design by aspect before proposing or merging, and name a record's sections by title with no file references, as the operator asked on 2026-11-02	2026-11-02 18:19:05 +01:00
jschoubben	2b9e6b256b	Read what exists before writing code, in the prepare step ... Each layer (research, decisions, survey, review) checked the layer before it and none read the running code, so effects of the controller's removed jobs surfaced only after delivery. Playbook 07's prepare step now writes, per context file, what exists today, every effect and reader of what is removed or moved, and each one's fate with its test; the review refuses work without it. Playbook 08 reads its area the same way, briefly. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 16:14:17 +01:00
jschoubben	7fd89de7cb	Playbook 07: item 9 names no wrong item	2026-10-29 01:56:19 +01:00
jschoubben	f4fdbde558	Playbook 07: rules for a delivery group's mesh-sdk pins, learned on 2026-10-28, so the next group does not meet the same refusals	2026-10-29 01:56:19 +01:00
jschoubben	7d022710b3	Playbooks 07 and 08: name the controller's try too while its verb exists (issue 774)	2026-10-28 20:37:05 +01:00
jschoubben	f89b8599c6	Playbooks 07 and 08 name the try by the checker's seat: mesh-delivery-checker.try replaces mesh-controller.try (ADR 0547 §10, issue 774)	2026-10-28 20:36:59 +01:00
jschoubben	a9830f5110	Playbooks 07 and 08: the review asks where state lives and how seams travel, and whether a repository holds mesh setup	2026-10-28 17:43:44 +01:00
jschoubben	781392b121	Playbook 07: the report follows the report-cadence section (short every 5 min, detailed every 30 min)	2026-10-28 12:32:05 +01:00
jschoubben	ea0c62355c	The glossary's word is catalog: replace the spelling catalogue in running prose	2026-10-28 11:27:34 +01:00
jschoubben	dd36b7557a	Playbooks 07 and 08: the local integration run is the named tests that exercise the change; the report's tree is drawn from the verb	2026-10-28 11:12:23 +01:00
jschoubben	d348256090	Playbooks 07 and 08: lessons of 2026-10-28 (progress tree, report cadence, local integration run, group members, delivered, fixtures)	2026-10-28 11:10:26 +01:00
jschoubben	6ef40bbcc7	How-we-build: a bus permission is proven under the real permission (ADR 0560); playbook 07 keeps only the failure note, as the operator asked	2026-10-27 20:36:54 +01:00
jschoubben	7ff4c7ce68	Playbook 07: the developer runs the node-permission test locally as a named exception to step 1	2026-10-27 20:29:11 +01:00
jschoubben	0d1aa93e37	Playbook 07: keep only the node-agent permission lesson; the operator keeps merging before the check by choice (2026-10-27)	2026-10-27 20:28:16 +01:00
jschoubben	1afab9739e	Playbook 07: a node-agent change runs under the node's real permissions before review approves, and a pull request whose safety is its check is approved only on its passing verdict (issue 1126, 2026-10-27)	2026-10-27 20:27:41 +01:00
jschoubben	1dab64134a	Playbooks 07 and 08: the one check is one status, mesh/check; drop the leftover try wording (review fixes)	2026-10-26 20:52:36 +01:00
jschoubben	a0e4c1fe17	Playbooks 07 and 08: one release, one check, no try, push once after the review (ADR 0548) ... Build capacity is the mesh's scarcest resource: a try before and after the review plus a check per fix round on an open pull request spent it several times per release.	2026-10-26 20:50:37 +01:00
jschoubben	b7dabd8ceb	Design 47 gives its running milestones rows; the glossary and playbook 07 name progress (issue 1947) ... The three milestones of the controller leaving build and delivery were prose only, so no reader of the table saw the running work; 1209 and 971 were listed in two milestones against ADR 0493 §2.	2026-10-26 16:40:12 +01:00
jschoubben	be1bbe0a65	Playbooks 07 and 08: read the forge head before trusting a reported push, so a try never runs on a push that did not happen	2026-10-26 11:02:44 +01:00
jschoubben	0354947ba6	Playbooks 07 and 08: the dependent-pull-request rule leaves delivery group members out; the instance-search rule is a numbered item	2026-10-25 13:29:17 +01:00
jschoubben	4d596bd211	Playbooks 07 and 08: open a dependent pull request only after delivery, fold a follow-up into the unapproved one, search every instance of a fault kind	2026-10-25 13:27:54 +01:00
jschoubben	ba09497092	Name the hand-path command mesh-hand-compose, as mesh-sdk feat/r6 now calls it: main's mesh-compose is the composer (ADR 0482, issue 1943)	2026-10-24 23:06:00 +02:00
jschoubben	2d3a205740	Merge remote-tracking branch 'origin/main' into feat/r6	2026-10-24 23:00:09 +02:00
jschoubben	49dd8fc7e3	Merge pull request 'R4g finish: hq's checks as Go tests, the old word struck, the marker (issues 1296, 1935)' (#473) from feat/r4g-finish into main ... Reviewed-on: #473	2026-10-24 20:56:42 +00:00
jschoubben	4b514e4d69	Design 47, the glossary and playbooks 04, 07 and 08 for release 6: wants and signed compositions, no plans (ADR 0539, issue 1130) ... Release 6 deletes delivery plans, batches, the merge window and tiers, so design 47's sections that described them as current are rewritten to the assigner's seven rules, the controller's signed compositions per node, the node agent, credentials on a done build, the switch as release 5's last plan, the hand path by mesh-compose and a want, and the view's delivered, moving, settled and stuck events. The glossary gains composition and restates want, declaration, send and apply; the playbooks follow a delivery by the view and the have keys and call no plans, plan, push or what-if.	2026-10-24 21:01:24 +02:00
jschoubben	8433e42c03	Playbook 07: the glossary's words, the source revision and the gate (review)	2026-10-24 13:54:31 +02:00
jschoubben	129af9906d	Playbook 07: read a verdict's trunk against main at once, because a lagging trunk makes the Approve merge nothing (issue 1726)	2026-10-24 13:50:37 +02:00
jschoubben	2249d30151	Merge main into feat/r4g-finish (#472)	2026-10-24 13:26:24 +02:00
jschoubben	8498006d23	Playbooks 07 and 08: answer the review (no lab, plain words, checks on the forge, issue 1941)	2026-10-24 12:50:35 +02:00
jschoubben	d20ed892cf	Playbooks 07 and 08: three questions in the milestone file, and a try before a merge by hand (research 071, issue 1921)	2026-10-24 12:45:57 +02:00
jschoubben	6dc008b5e7	Delete merge-check.sh and the four Python checks; the Go tests replace them (issue 1296, H6)	2026-10-24 03:39:11 +02:00
jschoubben	8055006ba1	Playbook 07: the two 'never run integration tests on the machine' lines say 'while developing', so the guideline after a failed try no longer contradicts them (review-471)	2026-10-23 23:24:15 +02:00
jschoubben	2b53b6a5d2	Playbooks 07 and 08: say the local run after a failed try as a guideline, not a rule (the operator)	2026-10-23 23:22:21 +02:00
jschoubben	87c338da8e	Playbooks 07 and 08: a failed try or check is run locally at once, so every failure shows in one run, not one per try (the operator, 2026-10-23)	2026-10-23 23:20:27 +02:00
jschoubben	8f7c23da7d	Make a timer that writes state, or a rule in code that overrides a person, a change the review asks (issue 1903)	2026-10-23 16:10:44 +02:00
jschoubben	c8ccbfe35f	Playbooks 07, 08 and the overview name what runs: the checker's try and status, hq's Go tests, the stream backlog, and the way to deliver without the builder (issue 1888)	2026-10-23 15:17:30 +02:00
jschoubben	47e78d8ff4	Strike the word merge gate: the composition check replaces it in the glossary, the designs and the playbook, and old issues keep it dated (issue 1303)	2026-10-23 15:12:57 +02:00