100 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jschoubben	cc605e3b13	Answer design 47's review for release 4's check: the judge's account ends at release 4, the assigner's reads and version skew and field refusal stated, where acceptance tests 22 and 23 are measured, and what release 4 retires	2026-10-19 22:44:18 +02:00
jschoubben	9ffa60924e	Graduate research 058 into design 47's release 4: a check runs only what changed, its tests by the language's build module, its composition by the assigner, in one status ... The check took 3 to 4.5 minutes on every change and paid the whole suite again on every re-ask; the operator's target leaves it about a minute. ADRs 0444 to 0447 decide how; the glossary gains composition check and kept verdict, and merge gate is struck once release 4 is delivered (issue 1303).	2026-10-19 22:03:44 +02:00
jschoubben	3174d5aa6e	Name R3c's issues and the forge module it takes in, and the orders its prepare step found (design 47)	2026-10-19 14:46:33 +02:00
jschoubben	5816ca669f	Say the page's freshness is not yet checked (issue 1222), and fix 08's leftover 'reviewed after its push' (review round 1)	2026-10-19 13:29:22 +02:00
jschoubben	afe83b9124	Keep the drawn overview of the playbooks in hq, for a later docs site	2026-10-19 13:27:55 +02:00
jschoubben	6c607504de	Say a moved trunk is met by the merge check, not promised to step 3 (review round 2)	2026-10-19 13:05:09 +02:00
jschoubben	20c857443c	Bring the branches up to the trunk before the try, and say the try at step 1's end runs the integration tests (review round 1)	2026-10-19 13:04:30 +02:00
jschoubben	7735cfd107	Try before the review, fail first on behaviour, survey every reader of a changed value (playbooks 07 and 08)	2026-10-19 13:03:28 +02:00
jschoubben	19a8e92801	Design 47: R3b's issues, and the two facts its prepare step found for R3c's insight on ADR 0437 (issues 1210-1218)	2026-10-19 11:51:15 +02:00
jschoubben	95bf5cbf20	Design 47: R3a's issues, the two controller fixes it needed first, and R3c's open question on Go-compiling images (issues 1200-1204, 1208, 1209)	2026-10-19 11:09:15 +02:00
jschoubben	643ec2b1bf	Design 47: release 3 is the milestones R3a to R3d by ADR 0437, and answering asks in the view moves to R5	2026-10-19 10:19:55 +02:00
jschoubben	292fae8863	Design 47: R2c is split by its order, the controller's last heard from presence before the node-engine stops sending alive (issue 1183)	2026-10-19 02:12:16 +02:00
jschoubben	d10965a341	Design 47: release 1-2 is the six milestones R1a to R2c, each one release; playbook 04 splits a milestone that holds a release order (the operator, 2026-10-19)	2026-10-19 00:11:02 +02:00
jschoubben	86e66dd51f	Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape (design 47 release 1-2, 2026-10-18)	2026-10-18 21:26:06 +02:00
jschoubben	4a090df25a	Design 47: release 1-2 cut by the orders its prepare step found, with its new decisions and issues (issue 1130)	2026-10-18 20:31:36 +02:00
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	d0a2950bb0	Playbook 02: wrap the check line and name the step it means (review round 1)	2026-10-18 17:05:46 +02:00
jschoubben	8e76098412	Playbook 02: after three review rounds the lead fixes further findings itself and proposes again; only a finding that changes what was decided goes to the operator (the operator, 2026-10-18)	2026-10-18 17:04:38 +02:00
jschoubben	cec72d1dc9	Playbooks 07 and 08: integration tests run once through mesh-controller.try on the pushed branch before the pull request, never on the machine (the operator, 2026-10-18)	2026-10-18 15:02:56 +02:00
jschoubben	ec373556d0	Playbooks 07 and 08: an acceptance criterion is numbered and cited by its test as <issue>/AC<n>, so its check is a grep (review round 1)	2026-10-18 12:50:30 +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
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	17c27ddf83	Playbook 07: a new integration test enters through the path the live trigger takes (issue 1086) ... Milestone 4's test saved its plan by hand, skipped the cut from a batch, and passed while the backup step never ran.	2026-10-18 02:19:20 +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	c10efa4d8c	Playbook 07: the new test failed on its first two runs, not three	2026-10-18 00:30:41 +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
jschoubben	64e357da7d	Playbook 07: a change the new merge script must judge ships the script first (issue 895)	2026-10-17 21:32:35 +02:00
jschoubben	9a9a78f882	Playbook 07: report every ten minutes (the operator, 2026-10-17)	2026-10-17 21:28:46 +02:00
jschoubben	e816b61cb7	Playbook 07: the prepare step splits an issue sized over an hour (the operator, 2026-10-17)	2026-10-17 21:25:39 +02:00
jschoubben	610be93803	Playbook 07: a fixing agent never runs an integration test locally (the operator, 2026-10-17)	2026-10-17 21:23:05 +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
jschoubben	e1987b3654	Playbook 07: the reviewer is kept for the whole release, and a watcher waits for its checks (issue 1042) ... The operator asked why review takes so long: a fresh reviewer per round or per mark reads everything again, and a reviewer waiting on the forge's checks spends its run waiting.	2026-10-17 18:26:06 +02:00
jschoubben	b5d3f23947	Design 57: its milestones name their issues, not their delivery state (issue 1039, folded into 1038)	2026-10-17 18:20:58 +02:00
jschoubben	c753ff068a	Playbook 07: a design names its milestones' issues, never their delivery state (issue 1038) ... The tracker and the delivery records hold whether a milestone is delivered, when and by what; a copy in the design's table is a central status kept by hand (AGENTS.md). Design 47 loses its copied cells.	2026-10-17 18:18:45 +02: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	6b58a6af82	Playbook 07: the glossary's word, the builder (review of #405)	2026-10-17 18:03:52 +02:00
jschoubben	9a39785116	Playbook 07: every wait on the wait list has a watcher agent on the bus (the operator, 2026-10-17)	2026-10-17 18:00:35 +02:00
jschoubben	06440c1522	Playbook 07: the build seat's holder, not a retired word (review of #405's check)	2026-10-17 17:56:21 +02:00
jschoubben	0e7eb9c2da	Playbook 07: read a failed check's whole log; a change to merge-check.sh is judged by main's version	2026-10-17 17:29:43 +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	fb284fa6ee	Playbook 07: the full report shows the whole design's milestones, the running one's issues under it (the operator, 2026-10-17)	2026-10-17 14:13:28 +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
jschoubben	edff1f25a1	Playbook 07: one milestone is one branch per repository, its steps reuse the name (the operator, 2026-10-17)	2026-10-17 12:04:37 +02: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	75d3ac0f82	Playbooks 04 and 07 after research 055: a milestone's shape from what-if; the Approve on every merge into main; when the two-step exception ends (issue 922)	2026-10-17 00:04:48 +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
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
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	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
jschoubben	0e7a115183	Merge pull request 'Playbooks 07 and 08: mark ready with mesh-delivery.mark-ready (issue 913)' (#383) from feat/913-mark-ready into main ... Reviewed-on: #383	2026-10-16 13:47:15 +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	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	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	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	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	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
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
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
jschoubben	43c3f2c098	Design 58: the operator confirmed the milestones; issues 878 to 887, building after design 57's delivery (playbook 04)	2026-10-16 09:55:11 +02:00
jschoubben	45e2d7e972	Design 58: milestones for the operator to confirm, owners named, and the as-is of logins on the bus (playbook 04)	2026-10-16 03:03:21 +02: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	cb4c18cedc	Design 58: the identity store is read by grant, and sessions never call through the tool runner's login (review round 1)	2026-10-16 02:45:58 +02:00
jschoubben	8f8f1b4337	Design 58: agent work as the mesh's own, graduated from research 053 with ADR 0383 to ADR 0390 ... Threads on the bus, a headless thread handler in a sandbox per session, a workspace toolkit with no general command runner, one identity seat, effects on every tool, signed bus logins and the switch to them; names the build's acceptance tests for the milestones.	2026-10-16 02:44:15 +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