814 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	28d84f31bf	Merge remote-tracking branch 'origin/main' into feat/1126-nodes-compose	2026-10-26 21:56:52 +01:00
jschoubben	7c88f297fc	Design 47: a settings-form module's values in the placement file, the vault's own, both sources' readers, the switch when placed, and the order of the delivery and the seed (issue 1126)	2026-10-26 19:45:32 +01:00
jschoubben	495d740d5f	Design 47: a placed node's want says self and names no composition; a yes names the composition allowed (issue 1126, ADR 0547 §2, §3)	2026-10-26 19:17:48 +01:00
jschoubben	df4ff3d039	Design 47: a model-access consumer placed before the vault serves licences is refused by the guard (issue 1126)	2026-10-26 19:09:16 +01:00
jschoubben	a6cc3d2e0b	Design 47: a node never applies a stand-in, and composes nothing of its own until the vault seals its secrets to it (issue 1126)	2026-10-26 18:59:06 +01:00
jschoubben	b6572acd72	Design 47: every read a node's account gains to compose, and that a module with an own secret does not move until the vault seals it to the node (issue 1126, ADR 0555)	2026-10-26 18:49:09 +01:00
jschoubben	ebc1a84e59	Design 53 §13: the seed closes a milestone whose issues are all done, wontfix or resolved with no live fix included, as the tracker counts it (issue 1781)	2026-10-26 18:40:12 +01:00
jschoubben	5bb109e36e	Design 47: the node-record read is the composer copy's one intended grant beyond the controller's, and what a hand-back means for it (issue 1126, ADR 0555)	2026-10-26 18:33:46 +01:00
jschoubben	d948774794	Design 47: the node record rides in the node's own have key (issue 1126, ADR 0555 §3)	2026-10-26 18:30:28 +01:00
jschoubben	68f8a8c198	Design 47: the found tunnel is decided at adoption; adoption and enrolled peers are read, not written (issue 1126, ADR 0555)	2026-10-26 18:26:53 +01:00
jschoubben	b5b84fafc6	Design 47: config placement, as ADR 0348 words it (issue 1126)	2026-10-26 18:21:31 +01:00
jschoubben	0488bc1801	Design 47 says what a node composes from: placement with the node's decided facts and settings layers, and the node's own record (issue 1126, ADR 0549, ADR 0555)	2026-10-26 18:20:51 +01:00
jschoubben	973182cdf9	Design 53: milestones are records of the tracker, an issue's milestone is its own link, and the seed reads the design's table once (ADR 0493, issue 1781)	2026-10-26 18:00:18 +01:00
jschoubben	97d600650a	Design 47: each issue in one milestone row, R4a's range written out, and row M1 for the milestone records, so the tracker's seed takes the table without a guess (issue 1781)	2026-10-26 18:00:18 +01:00
jschoubben	a6e27687db	Design 47: 1945 is L1's issue alone, and milestone 3 names 774 with 1126's rest carried by its note (issue 1947, review round 1) ... An issue belongs to one milestone (ADR 0493 §2); R6 is delivered and named 1945 for parts L1 now carries.	2026-10-26 17:03:14 +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	250c3ff605	Design 24: the pointer to 'Every secret lives in the vault' says above	2026-10-26 13:33:23 +01:00
jschoubben	a3f6e967c0	Design 24: the controller hands the vault only the covered accounts' values until the third milestone, and the break-glass recovery is below (review of ADR 0550's amendment)	2026-10-26 13:32:37 +01:00
jschoubben	11b0a450c3	Designs 47, 24 and 39 follow ADR 0548 to 0551: one check per set of heads with carried verdicts and merge turns, placement in the catalogue, every secret in the vault ... Design 47 names ADR 0548 (a check runs to its end, a trunk move carries a verdict by its package digests, the hold and the merge turn), ADR 0551 (the hold and turns only while the check gates merges), ADR 0549 (placement files read by the indexer) and ADR 0550 (the vault signs and adopts the loaded hashes), and ADR 0547's answers on placement and signing. Design 24 gains every secret in the vault; design 39 moves grants and tokens into it. The glossary gains carried verdict, merge turn and placement file.	2026-10-26 13:29:30 +01:00
jschoubben	f1c50d3e01	Design 47: the assigner's acceptance test names its six rules, as ADR 0547 §4 leaves them; the bus node follows the controller's list until the third milestone, for hand-back; placement stays where it is for now (issue 1126)	2026-10-26 02:59:58 +01:00
jschoubben	d70791ddee	Design 47: sentences that still named the controller as composer, issuer or reader of grants follow ADR 0547 as amended	2026-10-26 02:58:12 +01:00
jschoubben	5bdeb8db83	Design 47: take-over's test as ADR 0547's insight states it	2026-10-26 02:57:45 +01:00
jschoubben	d94f8a05a8	Design 47 follows ADR 0547: node agents compose their own modules, a grants part composes who may say what, the bus node writes the user list alone, and the controller leaves build and delivery in three milestones	2026-10-26 02:57:45 +01:00
jschoubben	de4c69d476	Name no node in design 47's test 10 proof: hq is public (issue 1130, review round 2)	2026-10-26 01:28:32 +01:00
jschoubben	9eb963d5f1	Give each restated acceptance test of design 47 its own proof, and add puts, the hand path and the builds bucket to as-is 04 (issue 1130, review round 1) ... Tests 18 and 19 do not cover tests 3, 7, 9, 10 and 11 as restated, so each now names the test or live read that proves it, or says it is not yet proved.	2026-10-26 01:27:21 +01:00
jschoubben	c255fd071c	Describe delivery after release 6: as-is 04 and 13 follow wants, compositions and haves, design 47's acceptance tests restated (issue 1130) ... Release 6 is delivered, so the as-is designs still describing the controller's plans were wrong, and design 47's tests 1 to 12 named batches, plans and the merge window that no longer exist.	2026-10-26 01:21:42 +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	3dbb5d4e65	Design 47: the switch needs release 5's bus grants and the operator's key first, the record hold's exception after the switch, and nothing checks the budgets (review of 4b514e4, issue 1130)	2026-10-24 21:06:41 +02: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	d08cac4e86	Answer the review of hq's finish: role names in the as-is delivery, ADR 0524-0529 named, stale check names fixed (issue 1296)	2026-10-24 04:40:02 +02:00
jschoubben	b3b778a1a6	Describe delivery as it runs after R4g: the parts, the build modules, the one check (issue 1296, H9)	2026-10-24 03:41:01 +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	e8bd9171cd	Design 47: the gate reads mesh/check, the forge requires no status (ADR 0534 §1 changes ADR 0447 §5)	2026-10-23 16:31:15 +02:00
jschoubben	d49dccb8d5	Use the glossary's word composition check where the merge gate was struck (issue 1303)	2026-10-23 16:10:08 +02:00
jschoubben	6ead37ee7b	Design 47: no status is required on any repository, so hq's Python checks go after the delivery (ADR 0534), and ADR 0529 is named	2026-10-23 16:10:01 +02:00
jschoubben	75056fa931	Design 47 says what R4g and R5 build as one milestone: asks on streams, the assigner's wants, hq's Go tests, the hand path (issue 1130)	2026-10-23 15:15:18 +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
mesh-tools	fa7629d02b	Merge pull request 'Design 42: the package manager and kernel rows as ADR 0507, 0508 and 0510 decide (upgrade safety)' (#467) from feat/upgrade-safety into main	2026-10-22 18:34:11 +00:00
jochen	030e985694	Answer the review's second round: the mockup's sheet holds invented sales figures; milestone 5's row lists only teaching and the counts	2026-10-22 19:21:38 +02:00
jochen	eddd7ba684	Answer the review: mockup data invented throughout, later milestones' scope marked proposed, design 59 says where it is replaced, playbook 10 aligned with 04 and 07	2026-10-22 19:19:52 +02:00
jochen	5d745d04db	Write design 63 and playbook 10, so the mail page's next steps are built from a picked design ... Design 63 turns the mail page into the operator's list with Owly beside it (ADR 0515 to 0519), in six milestones with their issues; its reference mockup is kept beside it, its data invented. Playbook 10 says how a page is designed before it is built: mockups with fixed data, the operator picks, the pick is the reference. The as-is of the mail modules now describes mail reading as delivered, the glossary gains design 63's words, design 59's milestone 4 is marked replaced, and AGENTS.md allows a design's mockup. Issues 1855 and 1856.	2026-10-22 18:42:42 +02:00
jschoubben	333e73830c	Amend design 42 for the package view, one-at-a-time upgrades and the fallback kernel (ADR 0507, ADR 0508, ADR 0510; issues 1840, 1841)	2026-10-22 17:41:15 +02:00
jschoubben	c07483081d	Cite ADR 0494 in design 47: the checker's milestone is one group, not two deliveries	2026-10-21 22:54:18 +02:00
jschoubben	1955d7f624	Correct design 47 after review of #463: R4e timing of the SDK group, the wait list's Waited-by condition, and what builds images from R4g	2026-10-21 22:52:18 +02:00
jschoubben	38020bee9a	Name the accepted decisions 0480 to 0493 in design 47 and state in its prose what they changed, so the design matches what holds	2026-10-21 22:44:29 +02:00
jochen	ac72fe6422	Design 36: the waits mirror's file is named by Claude Code's session id	2026-10-21 19:30:21 +02:00
jochen	9483caae2d	Design 36: the waits mirror is the module's own entry in the agent's home; the hook tools refuse mesh and node scope ... Review of the hooks paragraph: the mirror in the agent's home was not in the home's table, so the home look would count it as drift.	2026-10-21 19:29:38 +02:00
jochen	302ab2856a	Design 36: the plugin's session-start and Stop hooks beside the guard (ADR 0489, ADR 0490) ... Delivered in mesh-catalog#420 on 2026-10-21; the design said the guard was the plugin's only hook.	2026-10-21 19:27:33 +02:00
jschoubben	373b7e7dd1	Correct design 47's R4c row (installed toolchain, ADR 0477/0478) and move 1305 from R4e to R4f	2026-10-21 13:35:58 +02:00