747 Commits

Include renames

Author	SHA1	Message	Date
jochen	9a9934d47e	Design 59: say each milestone 2 issue's order, as the tracker holds it	2026-10-20 23:37:14 +02:00
jochen	7f3a3113aa	Design 59: no grant split (ADR 0472), and milestone 2's issues as split at its prepare step	2026-10-20 23:35:53 +02:00
mesh-tools	2713e131b4	Name ADR 0465, 0466 and 0469 in design 47, and write the day's lessons on watchers, pushes and what a merge moves into playbook 07	2026-10-20 19:44:57 +00:00
mesh-tools	1d7cfed47a	Name ADR 0457 and ADR 0463 in design 47, and write the day's delivery lessons into playbook 07 ... Design 47's catch-up of merges nobody heard is decided by ADR 0457 and bounded by ADR 0463, so other sessions read them from its frontmatter. Playbook 07 gains four lessons from 2026-10-20: a Retry is never asked beside an Approve (issue 1408), an ask is named only after it is read on the router, a check's wait is read from its delivery and not the build queue, and a catalogue change removing a module is tried against the controller (issue 1406).	2026-10-20 17:57:57 +00:00
jochen	d2dccddc27	Say the notifier's bundle is its own process under its own account, as main.go says	2026-10-20 19:12:04 +02:00
jochen	dcc6f185d4	Answer the review: the mail modules are separate modules, the notifier has no process, nothing future in the as-is; 1433 depends on none	2026-10-20 19:11:06 +02:00
jochen	e925a843ce	Write the mail modules' as-is design, so what design 59's milestone 2 replaces is recorded before it is built ... Playbook 04 step 3: the one grants list that gives reading and sending at once, and mesh-mail-notifier's pop-up for every new mail, read from mesh-catalog main a67f0196 and the live mesh.	2026-10-20 19:08:13 +02:00
jochen	66bb013b85	Write milestones 2 to 4's issues into design 59, as the operator confirmed them ... Playbook 04 step 6. Also names ADR 0378 §5 beside ADR 0440 §4 for the page's use of mail-reading, its writes with correct and undo, and issue 1419 in §8's last sentence, as the graduation's review noted.	2026-10-20 19:02:56 +02:00
jochen	a0a4edabc9	Space mail reading's batches 160 s apart, as ADR 0459 §15 now says	2026-10-20 16:25:02 +02:00
jochen	ebc7665b2a	Say that milestone 4 waits for the decision on its thread's caller	2026-10-20 16:22:53 +02:00
jochen	f96f964a2d	Answer the review: carry test 4 over as the direction words it, make milestone 4 wait for milestone 2, fix ADR 0461's clause numbers in the glossary	2026-10-20 16:21:49 +02:00
jochen	4a2c15f725	Graduate research 066 into design 59: mail reading, mail signals, granted reading apart and the mail conversation, with the Mail domain in the glossary ... Research 066's confirmed direction becomes ADR 0458 to 0462. Design 59 gains the sections and milestones 2 to 4 they decide, the glossary gains Mail as the thirteenth domain with four homonym rows, and design 49 lists Config and Mail so its count matches the glossary.	2026-10-20 16:17:50 +02:00
mesh-tools	440279fec4	Date the SDK-before-users order of design 47's release 1-2 note by R4e	2026-10-20 06:07:29 +00:00
mesh-tools	3439d19d06	Answer review round 1 of design 47's release 4 cut: dates of the status, the builder, test 4 and the issues	2026-10-20 06:07:17 +00:00
mesh-tools	89c4295f6d	Name release 4's seven releases R4a to R4g in design 47's table (ADR 0453)	2026-10-20 06:00:37 +00:00
mesh-tools	3e061bbd99	Cut design 47's release 4 into R4a to R4g by the orders it hides (ADR 0453)	2026-10-20 06:00:11 +00:00
mesh-tools	6ffd3709d8	Cut design 47's R3d into R3d and R3e, and name the terminal-free fix in R3d (ADR 0450, ADR 0449) ... R3d's prepare step found four things the gate reads that must ship before it, and two steps that needed the operator's terminal; R4 gains the controller's deletions (1318).	2026-10-19 21:27:20 +00:00
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
jochen	f6311a66bf	Answer design 59's review: mesh-mail's caller check, tests for the send state and the seat's verbs, no tracker state in the design; milestone 1 starts	2026-10-19 20:36:39 +02:00
jochen	c04c0ebb76	Name design 59's milestone issues, confirmed by the operator	2026-10-19 16:41:32 +02:00
jochen	491de157da	Design the mail web client: mesh-mail-web on the private network behind Keycloak, reading and sending through mesh-mail (ADR 0440); cite ADR 0439 in the as-is of a module's state	2026-10-19 16:38:55 +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	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
jochen	550487fc90	Say in the as-is of bus logins that a module's process may have a login of its own (ADR 0436, ADR 0438)	2026-10-19 11:02:57 +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	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	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
jochen	05ff547358	Design 55: hq owns part of the third slice's code, its checks and links (review round 1)	2026-10-18 04:25:11 +02:00
jochen	1def984c07	Design 55: designs and the glossary become records, and the knowledge base owns a design's state (ADR 0423, ADR 0424)	2026-10-18 04:23:10 +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	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	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
jochen	21c4d212ec	Correct three facts in the designs' states (issue 1072, review round 1)	2026-10-17 22:55:02 +02:00
jochen	1bd6f4611e	Say where nine half-built designs stand (issue 1072) ... The records cleanup found them saying proposed or designed although their code is on main; each now says in-progress and what is built and left.	2026-10-17 22:53:10 +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
mesh-tools	499407c669	Take in main up to 2cf1c64e24 (issue 1024) ... hq main moved after this change's check; it touches neither design 29 nor anything this change edits. The branch's tree is the reviewed design 29 change merged with main.	2026-10-17 18:09:09 +00:00
mesh-tools	4e0dd1b0d3	Say in design 29 how a folder a module owns treats files it did not write (issue 1024, ADR 0422) ... Design 29 is ADR 0422's home: it now says what `unknown` and `knows` mean on a directory under a home, that the found class no longer holds in ~/.ssh (ADR 0415, 0417), and lists ADR 0412, 0415, 0416, 0417 and 0422 among its decisions.	2026-10-17 16:23:05 +00: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	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