2026-05-13 - 2026-11-13
Overview
1 Release published by 1 user
Published
archive/initialization-consolidation
582 Pull requests merged by 3 users
Merged
#607 Playbook 07: hold a delivery-system release's push on a dry run with no item open
Merged
#606 Design 47 G: A-352, a bus module's running build counts while its newer build waits for the operator's yes
Merged
#605 Design 47 G: A-350, the catalog's fill starts above every number the builder gave
Merged
#604 Design 47 G: A-349, the pipeline runner's old forms accepted before G
Merged
#603 Design 47 G: A-343 to A-348, the third reader release before G
Merged
#602 Design 47 G: the lead's answers A-339 to A-342, met merging the zfs group into G
Merged
#601 Design 47 G: the lead's answers A-323 to A-334, from the dry run of G on itself
Merged
#600 Design 42 zfs-owns-zfs: the lead's answers A-30 to A-45 met in develop and review (issue 1979)
Merged
#599 Design 42 zfs-owns-zfs: /etc/hostid by the apply, and the lead's answers A-1 to A-26 (issue 1979)
Merged
#598 Design 47 G: lead answers A-321 and A-322, the watchman follows wants by seat
Merged
#597 Design 47 G: A-319 and A-320, the check runs unit and integration tests only
Merged
#596 Design 42: the zfs module owns a node's ZFS and changes nothing that is not set (ADR 0679, issue 1979)
Merged
#595 Design 47 G: lead answer A-318, what keeps its module form in G
Merged
#594 Design 47 G: lead answer A-316, a candidate carries the parts of the modules it adds
Merged
#593 Design 47 G: lead answer A-313, over-bound step answers in the steps state's own objects store
Merged
#592 Design 47 G: lead answers A-306 to A-309 from review round 2
Merged
#591 Design 47 G: lead answer A-304, the checker puts a phase's asks at once
Merged
#590 Design 47 G: correct lead answer A-303; playbook 07: the lead reads what an answer names first
Merged
#589 Design 47 G: the lead's answers A-298 to A-303
Merged
#588 Design 47 G: §717 (the views are named by their seats) and the lead's answers A-294 to A-297
Merged
#587 Design 50: the own resolver's file waits longer than its pass over a silent mesh resolver (ADR 0678, issue 1748)
Merged
#586 Design 47 G: the lead's answer A-293
Merged
#585 Design 47 G: the lead's answers A-291 and A-292
Merged
#582 Design 47 G: the lead's answers A-287 and A-288
Merged
#584 Design 47: the lead's answers for a placed module whose build failed (a small fix on main, issue 1966)
Merged
#583 Design 39 parts: the lead's answers D3 (a list of a place a secret is kept, for §15) and D4 (the database §13 and §14 read)
Merged
#581 Design 39 bus-and-switch: the lead's answer C5, how a carried switch is read
Merged
#580 Design 47 G: the lead's answers A-284 to A-286
Merged
#579 Design 47 G: the lead's answers A-281 to A-283
Merged
#578 Design 25 bus-state: the lead's answer L1, a merged candidate's manifest is newly accepted
Merged
#576 Design 39 parts: the licence manager is built of its parts, and the finished carry-over and its database leave
Merged
#577 Design 47 G: §716 (a group's members and bases before the take-in) and the lead's answers A-274 to A-280
Merged
#575 Design 20 and playbook 06 say what the manifest validator accepts, and how a module is built of parts
Merged
#574 Design 39 bus-and-switch: C4, room and the switch read the weekly window alone
Merged
#573 Design 47 G: §708 to §715, a requirement's provider, the revert ask, the validation before take-in and non-trunk branches
Merged
#572 Design 47 G: the lead's answers A-148 to A-273
Merged
#571 Design 39 bus-and-switch: C1, the licence manager runs as its own account, service and tools in its own runtime
Merged
#570 Design 47 G: the lead's answers A-112 to A-147
Merged
#569 Design 39 bus-and-switch: the lead's answer B44, the carry-over carries live leases
Merged
#568 Design 39 bus-and-switch: the lead's answer B43, a first view keeps a binding an event wrote after it was asked
Merged
#567 Design 39 bus-and-switch: the lead's answer B42, the vault asks one first view again by name
Merged
#566 Design 39 bus-and-switch: the lead's answer B40, a licence's target says where consumers go next
Merged
#565 Design 47 G: the lead's answers A-101 to A-111
Merged
#564 Design 39 bus-and-switch: the lead's answers B38 and B39 met in develop
Merged
#563 Design 39 bus-and-switch: the lead's answers B26-B37 met in develop
Merged
#562 Playbook 07: the prepare reads the code; the lead answers design questions against the principles
Merged
#560 Design 47 G: the lead's answers A-71 to A-92
Merged
#561 Design 39 bus-and-switch: the lead's answers B23 and B24 met in develop
Merged
#559 Design 47 G: the lead's answers A-44 to A-70
Merged
#558 Design 39 bus-and-switch: the lead's answers to the prepare's 22 questions
Merged
#557 Design 39 bus-and-switch: the licence manager keeps its data on the bus and switches on its own usage
Merged
#556 Design 47 G: the lead's answers A-36 to A-43, and corrections of A-27 and A-30
Merged
#555 Design 47 G: the lead's answers A-27 to A-35, each tested against the principles and the design's lines
Merged
#554 Design 47 G: the lead's answers A-16 to A-25, each tested against the principles
Merged
#553 Design 47 G: answer develop's questions against the principles; the outside-cause wait whole (G-19); lead answers (G-20)
Merged
#552 Design 47 milestone G: develop answers batches 6 and 7 (G-16 to G-18, §587-§705), the operator's answers O-1 to O-9 of 2026-11-11
Merged
#551 Design 47 milestone G: develop answers batch 5 (G-15 §560-§586), the operator's answers of 2026-11-11 afternoon
Merged
#550 Agents: hq-record-writer, the definition of the agent that proposes a record from a draft
Merged
#549 Design 25 bindings-first-view §9: compose a bucket's binding from the bus module's list answer, breaking the registry circle (issue 1966)
Merged
#548 Design 47 milestone G: develop answers batch 4 (G-12, G-14), the recovery module and the operator's answers of 2026-11-11
Merged
#547 Design 47 milestone G: develop answers batch 3 (G-10, G-11, G-13), with the operator's answers of 2026-11-11
Merged
#546 A developer reads its build map and the design lines it cites, not the whole design
Merged
#545 Design 47 milestone G: develop answers D-7 to D-10, and design 25's types wording
Merged
#544 Design 47 milestone G: answers to develop's first questions (callers of the bus module's acts, the node-engine's verbs, small body forms)
Merged
#543 Design 25: the grants part takes a first view of the bus module's bindings at every start, so a missed created event is recovered (issue 1966)
Merged
#542 The approval mark and every-event: the prepare's answers, so both parts are complete for develop with milestone G
Merged
#541 Design 47 milestone G: the prepare's answers, so the design is complete for develop
Merged
#540 Designs 34 and 46: sessions wait on any event, and the approval mark gates calls and marked waits, delivered with design 47's milestone G
Merged
#539 Design 47: milestone G's part complete, every operator answer and three review rounds written in
Merged
#538 Design 47: the watchman's take-in seed ends waits the indexer no longer holds (issue 1966)
Merged
#537 Build features from the design alone and ask the operator what it leaves open
Merged
#536 Take back three design 47 choices that broke accepted decisions (issue 1966)
Merged
#535 Amend design 47 with milestone 47/G's joint findings as its own choices (issue 1966)
Merged
#534 Close a research effort with the knowledge base's close verb (issue 1966)
Merged
#533 Glossary: transport fault and kept call; developers run the touched packages' integration tests once per head and use the live seat list (issue 1966, ADR 0668)
Merged
#532 Amend designs 47, 46 and 51 for pipelines per module and milestone G as one milestone (ADR 0666, ADR 0667)
Merged
#530 Amend design 47 for milestone G: the gate's record, the seat git, the merge on the Approve alone
Merged
#531 Developers, design writers and preparers can say a commit others wait on as it lands
Merged
#529 Research writes its requirements from the operator's answers before any option
Merged
#528 Watcher definition: a report along the way does not end the watch
Merged
#527 Glossary names no seat's holder: who holds a seat is read from the mesh
Merged
#526 Agent definitions: no symbolic links; a review proves a fix against the live mesh (issue 1966)
Merged
#525 Design 47's B0 says its one new seat verb is delivered first, alone (issue 1921)
Merged
#524 Design 47's B0 says what was built: the checking program on every check, its input by the checker's verb (issue 1921)
Merged
#523 Design 47 follows ADR 0656 and ADR 0644: the delivery's own parts checked and delivered by their own change (issue 1921)
Merged
#522 Playbooks 01 and 02: one record per question an effort answers; design choices live in the design
Merged
#521 Design 47 follows ADR 0633, 0637, 0638 and 0639: the take-in by the indexer it names, and the group try (issues 1966, 1921)
Merged
#520 Designs and glossary follow ADR 0634, 0635 and 0636: shared code lives with its owner, the seat list from the bus (issue 1966)
Merged
#519 Watcher definition: what a machine runs is read from the machine (issue 1585)
Merged
#518 Developer definition: the manifest validator gets one predefined key list for both cases, always (issue 1585)
Merged
#517 Developer and reviewer definitions: validate every manifest a change touches before handing back (issue 1585)
Merged
#516 Say manifest validator, not judge: the glossary gains the word and retires the noun
Merged
#515 Where new code goes is a design question: playbook 08, the developer and the code reviewer check it against designs 20 and 26
Merged
#514 Designs 20, 25, 26, 32, 51, 55 and playbook 07: the registry milestone as built (issue 1966)
Merged
#513 Designs 51, 32: the windows wake on the node-engine seat's manifest-reads-changed (ADR 0618), and every build stays readable by every counted node-engine (ADR 0624)
Merged
#512 Designs 25, 51: the registry milestone's prepare points (a failed pull retried on the store holder's settled, the owners' read tools, verdicts as a first view, ADR 0622)
Merged
#511 Designs 25, 26, 32, 51, 55: the registry milestone's designs after the review by architectural domain (ADR 0615-0621)
Merged
#510 Graduate research 081: registries are seats published into over the bus, the builder numbers every build, seat definitions on the bus, contracts modules
Merged
#509 mesh-watcher waits on the event of the part that owns the fact it watches
Merged
#508 hq ignores .work/, where every subagent's worktrees and context files live
Merged
#507 Agents work from hq's definitions and start from the knowledge base; every prepare and record gets the seams review
Merged
#506 Bus state by template, no readers, and the ledger: designs 25, 32 and 55 and the glossary follow ADR 0595-0597
Merged
#505 Design 47: the bus module is wanted like any module; only a warranted want replaces its server (ADR 0594)
Merged
#504 A research effort's reading tasks run on one agent definition, research-reader
Merged
#502 Design 55: the knowledge base keeps its records on the bus and is written and reviewed by section (ADR 0592, ADR 0593 §10)
Merged
#503 Playbook 07 and design 47 after the controller left: run as the running checker, let the running parts judge, L2 delivered
Merged
#501 hq's words test reads .claude/, so agent and skill definitions use the glossary's words
Merged
#500 Four reviewer agents carry playbook 01's review by architectural domain, two architectural domains each
Merged
#499 Playbooks 01 and 02: review by architectural domain, sections named by title with no file references, and storage forms that fit (the operator, 2026-11-02)
Merged
#498 Playbook 07: the prepare step reads what exists today before any code
Merged
#496 Design 47 and the glossary follow what L3 to L7 built (issues 774, 1952, 1953, 1954, 1955)
Merged
#495 Playbooks 07 and 08 name the checker's try beside the controller's (issue 774, ADR 0561), rebased onto L2
Merged
#494 Design 47 and the glossary: placement is bus state of the seat mesh-placement (issue 1126, delivery 2 of 2)
Merged
#493 Playbooks 07 and 08: every review asks where each piece of state lives and whether a repository holds mesh setup
Merged
#492 Design 47's L5 row and the glossary follow ADR 0565
Merged
#491 Playbook 07 follows report-cadence: the short report every five minutes, the full one every thirty
Merged
#490 The glossary's word is catalog, not catalogue (group words/catalog)
Merged
#489 Playbooks 07 and 08: lessons of 2026-10-28 (the report's tree, its cadence, named local integration tests, member repositories during a check, delivered means what the nodes run, real-shaped fixtures)
Merged
#488 Design 47: ADR 0564 homes health (L4), and milestones L5 to L7 give the controller's other jobs their homes before L3's lease write
Merged
#486 How-we-build: a bus permission is proven under the real permission (ADR 0560); playbook 07 notes the 2026-10-27 failure
Merged
#487 Design 47: R4d says what it became, three image reworks done and n8n left by ADR 0506
Merged
#485 Design 47: a placement change is answered by the nodes it places before it merges (ADR 0559, issue 1126)
Merged
#482 Design 47 says what a node composes from: placement, its config layers, and the node record (issue 1126)
Merged
#484 Playbooks 07 and 08: one release, one check, no try, push once after the review (ADR 0548)
Merged
#483 Design 47's milestone table names each issue once, and design 53 says milestones are records (issue 1781)
Merged
#481 Design 47 names the controller-exit milestones as rows; the glossary and playbook 07 name progress (issue 1947)
Merged
#480 Designs 47, 24 and 39 and the glossary follow ADR 0548, 0549, 0550, 0551 and ADR 0547's answers
Merged
#479 Playbooks 07 and 08: read the forge branch's head before trusting an agent's push
Merged
#478 Design 47 follows ADR 0547: node agents compose, the grants part composes who may say what, the bus node writes the user list, and the controller leaves build and delivery in three milestones (issue 1945)
Merged
#477 Design 47 and the as-is delivery after release 6: acceptance tests on wants, as-is 04 and 13 as the mesh runs now (issue 1130)
Merged
#476 Playbooks 07 and 08: lessons from the 2026-10-25 recovery
Merged
#475 R6: design 47, the glossary and playbook 07 follow the switch to wants (issue 1130)
Merged
#473 R4g finish: hq's checks as Go tests, the old word struck, the marker (issues 1296, 1935)
Merged
#474 Playbook 07: read a verdict's trunk against main at once, because a lagging source revision makes the Approve merge nothing (issue 1726)
Merged
#472 Playbooks 07 and 08: ask who ends each bus key, how a switch-over goes one node first, how a group's integration level runs; a hand merge runs it first (research 071, issue 1941)
Merged
#471 Playbooks 07 and 08: after a failed try, a local run of the integration level is a good first step (guideline)
Merged
#470 R4g+R5 (hq): its checks as Go tests; design 47, the glossary and playbooks say what R4g builds (design 47)
Merged
#467 Design 42: the package manager and kernel rows as ADR 0507, 0508 and 0510 decide (upgrade safety)
Merged
#468 Playbooks: how a module's old directory is closed, and a refused try (issues 1843, 1854)
Merged
#469 Design 63 (the mail web UI with mail reading and Owly) and playbook 10 (visual design)
Merged
#466 Name the session that pushed a head in its pull request (ADR 0505 §5)
Merged
#465 Never cut a milestone by an order between its parts; the delivery plan keeps that order
Merged
#464 Correct design 47 after the review of #463
Merged
#463 Name the accepted decisions 0480 to 0493 in design 47 and state what they changed
Merged
#462 Design 36: the plugin's session-start and Stop hooks beside the guard, and the waits mirror in the agent's home (ADR 0489, ADR 0490)
Merged
#460 Playbook 07: a new verb of a seat the mesh defines waits for the SDK and a controller delivered with it
Merged
#461 Playbooks 07 and 08: a milestone is one delivery group released by one plan; a fix found during it rides in the group
Merged
#459 Playbooks 07 and 08: the session that opens an issue along the way fixes it
Merged
#458 Playbook 07: name a pull request's own issues as 'issue <n>', and no other
Merged
#457 Correct design 47's R4c row (installed toolchain) and move 1305 from R4e to R4f
Merged
#456 Add milestone F2b to design 60, and make every strict reader of manifests a release order in playbook 07
Merged
#455 Mark design 61 designed now that ADR 0479 is accepted, and follow its last version
Merged
#454 Design 62: name ADR 0481 accepted, and say the page reaches OkiOki only over the bus
Merged
#453 Design 62: the bookkeeping portal (ADR 0481)
Merged
#452 Write design 61, the print and scan page, as the home of ADR 0479
Merged
#451 Name the accepted ADR 0468 in design 60 and break its building into three milestones
Merged
#450 Playbook 08: check a module compiles with go vet, never go build in its folder (issue 1577)
Merged
#449 Correct design 60: status proposed, each brother feature tied to the record that decides it (ADR 0474, ADR 0475)
Merged
#448 Design the brother module whole: scanning, the feeder, printing, settings read and configure
Merged
#447 Playbook 07: read a hand push's plan first, and assign a new module to one machine first
Merged
#446 Design 59: no grant split (ADR 0472), and milestone 2's issues as split at its prepare step
Merged
#445 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
Merged
#444 Name ADR 0457 and ADR 0463 in design 47, and write the day's delivery lessons into playbook 07
Merged
#443 Design 59: milestones 2 to 4 confirmed with their issues, and the mail modules' as-is design
Merged
#442 Graduate research 066 into design 59: mail reading, mail signals, reading and sending granted apart, the mail conversation; Mail as the thirteenth domain
Merged
#441 Cut design 47's release 4 into R4a to R4g, and date each 'release 4' rule by the R4 release that builds it (ADR 0453)
Merged
#440 Cut design 47's R3d into R3d and R3e, and name the terminal-free fix in R3d (ADR 0450, ADR 0449)
Merged
#439 Answer design 47's review for release 4's check (follow-up to #438)
Merged
#438 Design 47's release 4 gains the check: only what changed runs, tests by the language's build module, the composition by the assigner, one status (ADR 0444 to ADR 0447)
Merged
#437 Design the mail web client: mesh-mail-web on the private network behind Keycloak (design 59, ADR 0440)
Merged
#436 Keep three lessons of feature mail-sender in playbook 07: a rule keyed on a shared property, a manifest word's first push, one watcher per wait
Merged
#435 Name R3c's issues and the forge module it takes in, and the orders its prepare step found (design 47)
Merged
#434 Keep the drawn overview of the playbooks in hq, for a later docs site
Merged
#433 Try before the review, fail first on behaviour, survey every reader of a changed value (playbooks 07 and 08)
Merged
#432 Design 47: R3b's issues, and the two facts its prepare step found for R3c's insight on ADR 0437
Merged
#431 Design 47: R3a's issues, the two controller fixes it needed first, and R3c's open question on Go-compiling images
Merged
#430 Say in the as-is of bus logins that a module's process may have a login of its own (ADR 0436, ADR 0438)
Merged
#429 Design 47: release 3 is the milestones R3a to R3d by ADR 0437, and answering asks in the view moves to R5
Merged
#428 Design 47: R2c is split by its order, the controller's last heard from presence before the node-engine stops sending alive (issue 1183)
Merged
#427 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
Merged
#426 Playbook 07: the prepare step looks for the orders a release hides, and fixtures come from the writer's shape
Merged
#425 Design 47: release 1-2 cut by the orders its prepare step found, with its new decisions and issues
Merged
#424 Design 47: the operator confirmed ADR 0429's releases as milestones; release 1-2's issues and their order
Merged
#423 Design 47: the six releases of ADR 0429 as milestones; glossary: the delivery domain, its parts and their words
Merged
#422 Playbook 02: after three review rounds the lead fixes further findings itself; only a finding that changes what was decided goes to the operator
Merged
#421 Playbooks 07 and 08: integration tests run once through mesh-controller.try before the pull request, never on the machine
Merged
#420 Playbooks 07 and 08: tests are written from acceptance criteria on the issue (issue 1118); design 47 gets milestone 5b and cites ADR 0426 (issue 1117)
Merged
#419 Design 55: designs and the glossary become records, and the knowledge base owns a design's state (ADR 0423, ADR 0424)
Merged
#418 Retire the word epic, and define milestone as a group of a design's issues delivered together (issue 1105)
Merged
#417 Playbook 07: a new integration test enters through the path the live trigger takes (issue 1086)
Merged
#416 Design 47: milestone 3 fix names issue 1079 (1084 was its duplicate)
Merged
#415 Design 47: milestone 4 delivered; a fix of milestone 3 comes next. Playbook 07: new integration tests are read against the code before the first push (issues 980, 1082)
Merged
#414 Say where nine half-built designs stand (issue 1072)
Merged
#413 Playbooks 07 and 08 without the ready mark; a fixing agent runs no integration test; large issues split; the merge script ships first (issues 1022, 895)
Merged
#412 Playbook 07: a milestone has steps, runs the whole unit suite, writes its findings into its issues, watches on the smaller model; design 47 names milestone 2b and takes 895 (issue 1053)
Merged
#411 Playbook 07: a new node-engine key needs the controller first, on a branch of its own (issue 1051)
Merged
#409 Design 29: a folder a module owns says how it treats files it did not write (issue 1024)
Merged
#410 Playbook 07: the reviewer is kept for the whole release, and a watcher waits for its checks
Merged
#408 Playbook 07: a design names its milestones' issues, never their delivery state
Merged
#407 Design 47: phase II release 1 delivered (issue 1025)
Merged
#406 Playbook 07: every wait on the wait list has a watcher agent on the bus
Merged
#405 Playbook 07: read a failed check's whole log; a change to merge-check.sh is judged by main's version
Merged
#404 Design 47: one plan per group, no order lines, the Approve as the only gate (ADR 0418, 0419, 0421)
Merged
#403 Design 47: milestones 1 and 2 delivered
Merged
#402 Playbook 07: the full report shows the whole design's milestones
Merged
#401 Playbooks 07 and 04: a milestone is one release, never cut for size or time
Merged
#400 Describe the mesh MCP server as it runs and mark its design implemented (issue 1008)
Merged
#399 Playbooks 07 and 08: a repository's own clone stays on main (issue 1010)
Merged
#398 Playbook 07: the lead writes a design's state back (issue 1009)
Merged
#397 Playbook 07: one design is built at a time (issue 1007)
Merged
#395 Playbook 07: one milestone is one branch per repository
Merged
#396 Design 58: milestones 11 to 14 from research 057, as-is 17, and role names in place of machine and login names
Merged
#394 Design 58 and 36: identities carry logins, run for an identity, a bus password per identity (research 057)
Merged
#390 Feature agents-write-git, step 2: design 29 cites ADR 0399 and ADR 0400 (issue 955)
Merged
#393 Design 47's milestones and issues, and the as-is delivery as it runs today
Merged
#391 Playbook 08: a fix that moves a file to a new filler compares the values first (issue 957)
Merged
#392 Design 47 rewritten from research 055's decisions: hotfix, feature and epic from the trunk, delivery on the bus
Merged
#389 Playbook 07: report the whole issue tree every five minutes, every two while a delivery runs
Merged
#388 Playbook 09 and the hq-cleanup skill: a cleanup that deletes only what is proven done
Merged
#387 Playbook 02: one design per thing
Merged
#381 Design 47: a move of the trunk asks every active check again (ADR 0395)
Merged
#386 Playbook 08: a second fault the delivery shows joins the issue only in the same files
Merged
#385 Playbook 08: needing a decision keeps a fix small
Merged
#372 Design 58: agent work as the mesh's own (graduation of research 053)
Merged
#383 Playbooks 07 and 08: mark ready with mesh-delivery.mark-ready (issue 913)
Merged
#382 Playbooks 01 and 02: place research in the domains; its words reach the glossary at graduation
Merged
#380 Design 41: every file on a node is managed through node-files (WP9, ADR 0394)
Merged
#375 Playbooks 07 and 08: the five rules from the delivery-time audit
Merged
#378 Feature 57 (config and provisioning): release hq's record
Merged
#374 Test levels and time budgets in how-we-build and playbooks 07 and 08 (issue 891, ADR 0391)
Merged
#373 Feature 57 (config and provisioning): designs, playbooks and glossary words into the release branch
Merged
#371 Playbooks 01, 02 and 04: settle decisions before versions, test at the cheapest level, acceptance tests through to milestones
Merged
#370 Cite ADR 0382 in the delivery design (issue 867)
Merged
#368 Playbook 08: a small fix may cover two or three related issues in one repository
Merged
#367 Playbook 08: a small fix gets three review rounds, as a feature does
Merged
#366 Playbooks 01, 02 and 04: one cycle from idea to delivered milestones
Merged
#365 Say rollout, not walk (issue 646)
Merged
#364 Playbook 07 as five bounded phases with reused context; playbook 08 for small fixes
Merged
#363 Add three lessons from feature mail-hardening to playbook 07
Merged
#362 Playbook 07: an issue is one repository and five to ten minutes; a long run says where it stands
Merged
#361 Playbook 07: the ready note and the brief a fixing agent follows
Merged
#360 Playbook 07: up to five Sonnet agents at once, at most two on the larger model
Merged
#359 Playbook 07: three to five review rounds, the reviewer told its round, and the allowance in every report
Merged
#358 Playbook 07: the lead settles an issue's questions before a smaller-model agent builds it, two at a time
Merged
#357 To-be 42: the kernel module holds the kernel's run-time settings, huge pages first (ADR 0369, issue 746)
Merged
#356 To-be 48: cite ADR 0368, the resolver restarts itself for that module alone
Merged
#275 To-be 08: the five connectivity contexts walked through the network layers
Merged
#355 Playbook 07: review the local commits before anything is pushed
Merged
#354 Playbook 07: how several agents work one feature on one branch
Merged
#353 Fit design 57 to walks with no first-machine gate (ADR 0360, ADR 0362)
Merged
#352 To-be 45: the bus module says every user's slow consumer, and S9 raises it (issue 270, ADR 0357)
Merged
#350 To-be 57: building config and provisioning, as 37 packages each an issue (ADR 0348, ADR 0349)
Merged
#351 57/F4: The glossary gains the words of config and provisioning (issue 653)
Merged
#349 To-be 47: a busy container on the first node holds only its walk, and the wait counts (ADR 0335, issue 594)
Merged
#348 To-be 47: a change is built once, at its check (ADR 0350, issue 649)
Merged
#347 Design 27: a served own name with a default, or nested, is refused too (ADR 0346, review 224)
Merged
#344 To-be 46: an ask reads at a glance, and its values are whole where the sender is proven (ADR 0345, issues 383 and 639)
Merged
#345 To-be 27: a provider may serve its own composed names (issue 624, ADR 0346)
Merged
#346 To-be 46: an approved settings change is sent at once (issue 641, ADR 0344)
Merged
#343 Design 36 §12: the names a memory value may carry (issue 367, ADR 0343)
Merged
#342 To-be 36: a session's memory follows the operator (issue 367, ADR 0343)
Merged
#341 To-be 52: the home network's SMB and NFS shares become modules' (issue 613, ADR 0341)
Merged
#340 To-be 47: a merge whose walk said its modules unchanged is delivered (issue 611)
Merged
#339 To-be 8: a port may be reached from the machine's own local network (issue 154, ADR 0340)
Merged
#338 To-be 17: the store genesis raises is the postgres module's server (issue 609, ADR 0338)
Merged
#337 to-be 17: genesis assigns the builder before the package registry exists and hands it the forge it raised (issue 121, ADR 0336)
Merged
#336 to-be 56: the betterbird module owns Betterbird's whole configuration, shown without a credential (issue 586, ADR 0329)
Merged
#334 To-be 46: an agent session asks the operator through its module and reads the answer by a key (issue 589, ADR 0332)
Merged
#331 Glossary: fix time and fix budget (issue 403, ADR 0313)
Merged
#326 To-be 45 §5: the operator-channel holder reads open state before it speaks (issue 271)
Merged
#333 Name the take of a shared folder in the core's writers table (ADR 0325 §8, issue 567)
Merged
#332 To-be 47, to-be 45 §9 and the glossary take ADR 0323: a merge check judges the merge (issue 341)
Merged
#330 Give ADR 0313 a home in design 47, the delivery budget it extends
Merged
#329 to-be 55: a drafted clause may be changed, and a clause another record links keeps its number (issue 494, ADR 0321)
Merged
#328 To-be 47: a covered stop reads covered and stays listed; a one-machine module is covered (issue 480)
Merged
#327 Say in to-be 27 how a value several modules share is set once (issue 415, ADR 0309, ADR 0319)
Merged
#324 Give ten uncited decisions their homes in the designs they change (issue 504)
Merged
#325 to-be 55: a failed whole-set rule is a warning to the operator and leaves the module healthy; cited is judged in the review (issue 504)
Merged
#323 Adopt a mail account the profile already holds instead of adding it twice (issue 345, ADR 0317)
Merged
#321 Say that a condition's looks are kept beside the bucket, not in it (issue 420)
Merged
#322 Design the mail client set up by the mesh (issue 345, ADR 0316)
Merged
#320 To-be 24 names ADR 0305: a provider hands on the credential its software issued (issue 526)
Merged
#319 Add Media as the eleventh domain, with its words (ADR 0302)
Merged
#316 Give ADR 0299 its home in to-be 47: a stop ends only its own change on a shared walk (issue 459)
Merged
#315 To-be 47 names ADR 0298: the bus's grants arrive before a walk's gate (issue 490)
Merged
#318 One word, one thing: the old "knowledge base" uses say what they meant (issue 430)
Merged
#317 To-be 53 names ADR 0300: the issue tracker's record is a log of operations
Merged
#313 Glossary and to-be 53 for ADR 0294: a linked fix, withdrawn, abandoned (issue 483)
Merged
#312 Issue 426, ADR 0290 rule 9: the decision records and research efforts leave hq for the knowledge base
Merged
#314 To-be 55: rests-on and touches links, the import's refresh; ADR 0248's index comes from the knowledge base
Merged
#311 ADR 0290: the knowledge base reviews a proposal itself
Merged
#310 Proposed: ADR 0293, an ask the controller made is delivered again to its seat's worker (issue 334)
Merged
#308 ADR 0290: hq keeps no copy of the records (issue 435)
Merged
#309 ADR 0292: a consumer of the part a provider waits on is held under the wait, and passes its gate as a wait for a person (issue 405)
Merged
#307 ADR 0290 rewritten: a decision record lives whole in the knowledge base
Merged
#306 ADR 0290 and 0291: the knowledge base, and an issue whole in the issue tracker (research 045)
Merged
#304 Research 045 findings: a knowledge base agents ask instead of reading markdown
Merged
#305 Declare every partial supersession in both records, and check it
Merged
#297 ADR 0283: the username lives in its sources entry, and the needs-operator words as built (issue 386)
Merged
#299 ADR 0285: every condition's message says which issue tracks it and where it stands (issue 400)
Merged
#303 ADR 0289: the controller mirrors its records into buckets written only on a change (issue 419, research 036 G2)
Merged
#302 ADR 0286: a tool or verb marked in its manifest runs only on the operator's approval of that one call (issue 417)
Merged
#301 ADR 0287: a seat names the paths its holder owns, and a claim without them is refused (issue 412, research 023)
Merged
#300 ADR 0288: the object store stays on the maintained fork, and Garage is chosen only after the consumers' S3 features are counted (issue 413)
Merged
#298 Close ten research efforts their decisions already settled (issue 408)
Merged
#296 Renumber the fixing-status record to ADR 0284 (issue 406)
Merged
#295 ADR 0283: an agent moves an issue to fixing under its own name, and an issue is resolved only from fixing (issue 399)
Merged
#294 ADR 0283: a part waiting for the operator's secret or setting is said as waiting and passes the first-node gate (issue 386)
Merged
#291 To-be 47: handed to mesh-controller and mesh-delivery for ADR 0282's first slice (issue 382)
Merged
#293 Accept ADRs 0164-0166 and cite them in to-be 42 (issue 398)
Merged
#292 Accept ADR 0242: a recorded build moves only by a person's push
Merged
#289 ADR 0282 (proposed): a leaf fix runs healthy on every node within five minutes of its merge, a core module within ten
Merged
#290 Research 044: the operator's direction, a mesh-monitor module, is the leading hypothesis
Merged
#288 Research 045: a knowledge base the mesh writes (decisions, guidelines, policies)
Merged
#287 Research 044: what leaves the controller next
Merged
#286 ADR 0281, to-be 53 §11: an issue knows whether its fix is delivered, and a fix stuck after its merge is loud
Merged
#285 ADR 0279, to-be 53 §10: the issue tracker triages every new issue, and an issue is ready when what it depends on is delivered
Merged
#283 ADR 0275 slice 3: issue reports carry only opened; the tracker holds every status
Merged
#281 ADR 0278, to-be 53 §9: the issue tracker checks every new issue for a duplicate
Merged
#280 An issue's status lives in the issue tracker: playbook 03, cycle.py and the notes slice 3 of ADR 0275 asked for
Merged
#278 ADR 0277: a trusted setting is proposed through a verb and set on the operator's warrant, and a module's own secret is asked for and typed at the desk
Merged
#277 Issue 362 resolved: ADR 0276 gains the own-path batch rule and a progressive insight, to-be 45 gains S18 and S19
Merged
#273 ADR 0274, progressive insight: the router judges whether a channel can carry the ask (issue 370)
Merged
#274 Playbook 03 takes an issue's number from the issue tracker
Merged
#272 ADR 0275, to-be 53: the issue tracker's module is mesh-issues, holding the seat issue-tracker
Merged
#271 ADR 0276: merges are assembled in a rolling window, and each batch is delivered by one walk (issue 362)
Merged
#270 ADR 0275 and to-be 53: the mesh numbers and tracks its issues in a module of its own
Merged
#268 ADR 0274: an agent proposes a shared instruction section, and every node takes it only on the operator's warrant
Merged
#269 Issue 364: the merge gate refuses a module that uses a seat another module declares
Merged
#266 Issue 363: ADR 0267 was decided and never built
Merged
#267 Research 042: the mesh keeps its own issues
Merged
#242 Issue 341: a merge check judges the pull request's head, not what merging it makes
Merged
#231 Issue 338: a module built from a shared repository moves on every merge to it
Merged
#265 Issue 361: the setuid search shows its progress, and the operator can ask for a fresh one at the terminal
Merged
#264 ADR 0266: the control node's agent account is named nox
Merged
#263 Issue 362: two merges seconds apart left their delivery waiting for a person
Merged
#261 Issue 361: the control-node's agent account is never judged, because its search for setuid programs cannot finish in fifteen minutes
Merged
#262 Research 041: the agent's session runs confined, instead of being proven by a disk-wide search
Merged
#260 Issue 360: the operator cannot choose a notification's action on a touchpad
Merged
#259 Issue 359: a secret given reached the operator as "needs a look", and nothing said why
Merged
#258 Issue 358: a mesh directory outside a home is changed by path, through any link; issue 356 points at it
Merged
#253 Issue 353: the controller asked before the bus held its grant
Merged
#256 Issue 356: the operator's command ran a stale engine, and a hand-over had no channel; ADR 0272 gains the operator's rule and words.py the daemons' lines
Merged
#257 cycle.py: skip a rejected option by its ## section, so one under a ### subheading is skipped too
Merged
#255 Issue 354: a decided rename was never scheduled, and a record that defers work names its issue
Merged
#254 ADR 0273: the agent's home is the module's, and the operator's personal rules and lessons are registered through it
Merged
#252 Issue 352: a gate read another send's report, and a put-back chose a controller older than its store
Merged
#251 Issue 351: a held delivery whose module a backlog walk carried to every machine is never covered
Merged
#211 ADR 0259: an ask is a message on the bus, any channel answers it, and the asker acts on a warrant
Merged
#249 Issue 348: a resolver that stopped answering ran on unnoticed, and builds sent after it were blamed
Merged
#248 ADR 0272: progressive insight — the terminal's mark, the login session, ordinary lines are reads and settings
Merged
#244 Issue 344: the known gaps in the agent's boundary, accepted for now
Merged
#247 Issue 347: a pull request opened after its push is never checked, and nothing says so
Merged
#243 ADR 0272 (accepted) and issue 343: the controller's terminal has no command; mesh-cli on every node
Merged
#225 ADR 0266 and issue 333: on the control node, agents run under an account of their own
Merged
#246 Issue 346: a setting a verb may set is pasted raw into its file, so an untrusted file is an injection point
Merged
#245 Issue 345: a calendar reminder shows transparent and empty, and the mesh had no tool to look at it
Merged
#240 Issue 340: an agent can plant a hook in every agent session on the mesh
Merged
#241 ADR 0270 and 0271 (accepted): a held delivery a later merge contains, or that moves nothing, ends by itself; a send held for the bus's step is told at once
Merged
#228 Issue 336: a send held for the bus's planned step raises no condition, so the operator is never asked
Merged
#239 Record hygiene: resolve issues 310, 312, 313, 314, 318, 325, 327, 330 and 337, whose fixes are merged and live
Merged
#238 ADR 0269: what the mesh's own declaration stopped is started again when it goes
Merged
#236 Issue 339: the merge order against mesh-host #61, used-as-found as a behaviour change, the review's follow-ups
Merged
#237 Issue 319: why no walk opened, and four held deliveries closed with stop
Merged
#235 ADR 0268: the login shell's execute is withheld on the control-node until a call to it needs a person's approval
Merged
#233 Research 039: a tool or verb that needs a person's approval
Merged
#234 Issue 339: any caller of the settings verb could have the node-engine hand a system directory to an account
Merged
#232 ADR 0267: an artifact is rebuilt only when its build source changes, and a module moves only along build dependencies on artifacts
Merged
#230 Issue 337: the store's reader can read the controller's signing key (critical)
Merged
#227 Issue 335: a build that passed its gate was failed and put back by the first machine's later reports
Merged
#229 Design 52: until it is adopted, the workstation's fstab line still mounts at boot (review follow-up)
Merged
#223 ADR 0264 and issue 330: a message a consumer gives up on is kept until a person delivers it again or drops it
Merged
#221 ADR 0263 (accepted), research 038, design 52: a share is a provision, a node mounts it on demand
Merged
#224 ADR 0265 and issue 327: a verb that reads is answered on the serving controller's own connection, and every connection says what it is
Merged
#226 ADR 0262: a left-out module's data is backed up as this controller reads it, and an unplaceable line is listed
Merged
#216 ADR 0262: a preference has a default in its manifest, and the operator's own value has none
Merged
#222 Issue 332: the service manager could neither clear a failed unit nor say what wants it
Merged
#220 Issue 331: resolved, the sensors condition cleared live
Merged
#219 Issue 331: fixed-by and replay R331
Merged
#218 Issue 331: a declared tool check is never asked on the live link
Merged
#214 Issue 325 and ADR 0261: an assignment made while its module's build runs is kept pending
Merged
#217 Issues 326-330: research 036's live bus faults, measured again and diagnosed
Merged
#215 ADR 0260: three standing reads, drop-in directories are no module's, the lists grow only in the open
Merged
#213 Research 036: everything moves over NATS — where the mesh still talks around the bus, and what a view onto the bus needs
Merged
#212 ADR 0260: a bar block shows a value its module keeps on the bus, and no module reads another's files
Merged
#207 ADR 0257, issues 321-323, research 035: record the bases builds copy; what the pre-mesh images are
Merged
#210 ADR 0254: correct what the fix covers after its review (progressive insight, issue 318)
Merged
#206 ADR 0256: one module reads a machine's hardware condition, and a fault is said through its health
Merged
#209 ADR 0258: name the mesh MCP server, not the retired console
Merged
#204 ADR 0254: a wait for a person's new login is not a gate's failure, and each module of a send keeps its own pass (issue 318)
Merged
#208 Issue 324 and ADR 0258: a desk click performs only an acknowledgement, an answer is a one-time ticket
Merged
#205 ADR 0255: the bar takes blocks as data from the module that knows the hardware
Merged
#203 Issue 320 and ADR 0253: a condition says itself to the operator in plain words
Merged
#202 Issues 316-319: holds that never lift, holds walked past, and one module's wait stalling every walk
Merged
#198 Issue 314: a large answer was lost on its way back; issue 200 resolved by 265's fix
Merged
#200 ADR 0251 and to-be 51: the registries say what they hold and keep what is named
Merged
#201 ADR 0252: a module puts an account in a group, and the mesh says when a new login is needed
Merged
#199 Issue 315: a failed unit of a module was never raised
Merged
#197 Issue 313: history adopted at the switch was held for a person; ADR 0250 retires it
Merged
#194 Issue 309: two order rules ordered one pair both ways; ADR 0249 gives them a precedence
Merged
#196 Issue 310: a pull request ran its own copy of its repository's check
Merged
#195 Issue 312: no tool said a machine's disk load
Merged
#193 Issue 311: the media catalogue's check ran no tests for its TypeScript modules
Merged
#191 Issue 306: a check on the control node ran past its timeout
Merged
#192 Issues 307, 308: the lab's beds kept the bus and runtime the mesh had left; a lab unit test's verdict depended on the machine
Merged
#190 Issue 305: a recheck left the old verdict standing
Merged
#189 Issue 146: the enrolment-time consumer is answered by issue 208; design 08 names the join's code
Merged
#97 ADR 0217, to-be 44: no change to a machine takes effect unseen
Merged
#94 Issues 303, 304; 240 resolved, 242 located
Merged
#188 Triage issues 279-298: resolve the fixed, with replays R292 and R298
Merged
#187 Triage issues 228-278: close the fixed, re-check the rest
Merged
#186 Issues 092–208 triaged on 2026-10-08: 13 resolved, 1 wontfix, the rest re-checked
Merged
#185 Ignore Python's cache folder
Merged
#184 Issues 301, 302: a push of recorded builds is no repair; the lab's Go replays are checked in Go
Merged
#183 Issues 296, 299, 300: resolved, each with its replay
Merged
#182 ADR 0248: the decision index is generated when it is read, and never stored (issue 297)
Merged
#181 Issue 300: a new module is not built at its merge
Merged
#180 Issue 299: an optional verb makes a holder look silent
Merged
#179 ADR 0247: a machine with a VPN client routes names by domain, through a resolver of its own
Merged
#177 Issue 297: two open decisions always conflict
Merged
#178 Issue 298 and ADR 0246: a seat's new verb is promised before it is required
Merged
#176 words.py: a retired word's plural is the word
Merged
#173 ADR 0245: a verb says what it replaces, and the agent is guarded from working round the mesh
Merged
#175 Issue 296: a plan's clock restarted at every save
Merged
#168 ADR 0241 and to-be 48 §10: a machine says how its network is, and an outside writer of a mesh file is a finding
Merged
#171 Issue 295 and ADR 0242 (proposed): a recorded build moves only by a person's push, and a send says what it recreates
Merged
#174 ADR 0244: the mesh in domains, one word per thing, checked (graduates research 034)
Merged
#172 ADR 0243: the agent module removes a home item it did not place only on the person's word, and keeps a copy
Merged
#169 Issue 294: a quoted value given to the controller's command line cannot hold a quote
Merged
#167 Research 033: split DNS with a VPN client
Merged
#166 To-be 48 Phases B to E are built: what each chose, and what is still to read on the live mesh
Merged
#165 Issues 292-293: a drill counted as a repair; a warning on a required check blocked the merge
Merged
#164 Issues 290-291: a delivery adopted while it waited never got its check; a planned maintenance window failed the applies that met it
Merged
#163 Issue 289: a verb answered during a handover could not run its own build
Merged
#162 To-be 48 Phase A is being built: in-progress, its code named, what the build chose
Merged
#161 Issues 285, 286, 287, 288: the merge gate judged nothing; the seat's check disagreed with agents' machines; a seat and a module of one name were unreachable; the facts still name the installation
Merged
#160 Issue 282: a secret on a command line is kept in the runtime's events
Merged
#159 ADR 0240 and to-be 48: a module says how it is healthy, and the node-engine judges it
Merged
#158 Research 032: a module says how it is healthy — evidence, options, recommendation
Merged
#157 ADR 0239: a waiting walk is said by the controller; Phase B built
Merged
#156 ADR 0239: a delivery is owned by mesh-delivery and runs from commit to delivered
Merged
#155 ADR 0238: a commit is the build at hand — one commit, one change plan, checked off the trunk and published only on it
Merged
#154 Issue 281: a tier sent one module at a time blamed a module for its machine
Merged
#153 Issue 280: a rebuild of an unchanged source was read as a new bus
Merged
#151 Issue 279: a folder cannot be owned by the account a module runs as
Merged
#152 ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges
Merged
#150 Research 032: a module says how it is healthy
Merged
#148 Issue 278: a module held by no machine was read as shared code; ADR 0236's open question answered
Merged
#149 To-be 45 §7: a hand act a person decides by design is no repair, by the verb that recorded it
Merged
#146 ADR 0236, to-be 45 Phase 4: a build is judged on its first machine and put back by something other than itself
Merged
#147 Issue 277: one unanswered question was an urgent alert nobody could read
Merged
#145 Issue 276: the audit logger and the usage store retry, and lose no event
Merged
#144 ADR 0235: the bus is backed up by its own snapshot of each stream
Merged
#143 Issue 276: a handler that did its work was offered it five times
Merged
#142 Issue 275: a machine waiting for its push was said to be urgent
Merged
#141 ADR 0233: a module declares the data it holds, and the mesh protects and watches it
Merged
#140 ADR 0234, to-be 46: the mesh holds a conversation with its operator
Merged
#139 Research 028: a conversation with the operator over channels that are seats; Telegram as first holder
Merged
#138 Issue 274: a provider is granted only the consumers bound to it
Merged
#137 Issue 273 and ADR 0232: a binding to a consumer's data moves only by a person
Merged
#128 ADR 0226: the private network is assigned by its own name, and the proxy names its public issuer
Merged
#135 ADR 0230: a consumer the mesh stops asking for is retired, and deleted only by a person
Merged
#136 ADR 0231: a healer acts on what observation raised, and only observation says it worked
Merged
#134 ADR 0229: the core's order is a lease the store remembers, and an epoch a machine is sent once it reads one
Merged
#133 ADR 0228: a value given by hand lives only until its module's first good start
Merged
#132 Issue 271: a new consumer replayed the morning to the operator
Merged
#131 Issue 208: the bus's objects asserted on every send
Merged
#130 Issue 270: Phase 1 watches signals that come later; to-be 45 in progress
Merged
#129 To-be 45 in progress; issue 269: the controller cannot write a cancelled set
Merged
#125 Research 031: a core that cannot fail silently
Merged
#127 ADR 0225: a consumer's identity is bounded by the provision it requires
Merged
#126 Issue 268: letta printed its passwords into its log
Merged
#124 Issue 267: a reconcile's report overtook the apply that followed it
Merged
#123 Issue 266: a merge on the bus was never handed to the controller
Merged
#122 Issue 265: a push outlived its caller, and the bus refused its answer
Merged
#121 Issue 244: located — the console drops a mesh seat's node, and a push ran on every machine
Merged
#119 Issue 179 recurred; ADR 0224: a provider that keeps failing a consumer is a problem the controller reports
Merged
#120 Issue 264: a self-updating engine lost the report of the apply that delivered it
Merged
#117 Design: resolv.conf is the uplink's holder's; a machine's names are node-hostname's (ADR 0223 parts 2–3)
Merged
#118 Issue 263: every consumer pays for the tightest backend's name limit
Merged
#116 Issues 190, 259, 262: resolved
Merged
#115 ADR 0223: the mesh has two resolvers, and a machine lists only them
Merged
#113 ADR 0222: a module is told where a mesh seat's holder is reached; the controller writes no file a seat's holder owns (issue 190)
Merged
#114 Glossary: node-engine replaces "host agent" and mesh-host
Merged
#112 ADR 0221: a push sends no build a policy or a plan holds back, except to the machine it names
Merged
#111 Issues 260, 262: a service waits for what it reads; a mesh name has no IPv6 address rather than no name
Merged
#110 ADR 0220: what a machine asks needs its uplink held, and the retired resolver pieces go
Merged
#109 Issues 257, 261: a reconcile applied an older declaration over a newer one
Merged
#108 Issue 258: resolved
Merged
#107 Issues 258–260: what the move to one resolver met
Merged
#106 Issue 257: a plan waited on a declaration its first machine never reported
Merged
#105 ADR 0219: the build queue is controlled through the controller and the build seat
Merged
#104 Issues 224, 248-252, 254, 255 resolved; 256 opened and resolved; 253 where it stands
Merged
#103 Issue 255: the journal verb read nothing for a system service
Merged
#101 Issue 248: delivery restored; a merge still heard twice has another cause
Merged
#102 ADR 0218 and issues 250-254: delivery in order, and a store that keeps what it says
Merged
#100 Issues 248, 249: the controller's event consumer replayed a week; a new state is refused until a push
Merged
#99 Issue 247: a module cannot put the operator's account in a group
Merged
#98 Issue 246: the console says a module runs nowhere when a runtime answers late
Merged
#87 Issue 243: resolved
Merged
#96 Issue 245: behind is what a plan decided and has not yet done
Merged
#95 Issue 245: status calls a module behind when only its repository moved
Merged
#93 ADR 0189 collects again; issue 244: a verb with an empty schema cannot be called
Merged
#92 to-be 43: in progress
Merged
#89 ADR 0216: the agent's configuration is registered through its module, at three scopes, and served as one plugin
Merged
#90 to-be 43: backups against mistakes (graduates research 030)
Merged
#91 ADR 0215: the machine's message bus is a node seat, and it is never restarted live
Merged
#88 Research 030 + proposed ADR 0214: backups against our own mistakes
Merged
#86 Issue 195: resolved
Merged
#85 Research 029: the agent configured through its module, as a plugin the mesh serves
Merged
#84 Issue 243: a rebuilt licence store silences every node
Merged
#83 Issues 239–242: a name taken over, a dry run recorded, every database dropped, no backups
Merged
#82 Research 013: the forge and the registries — a seat answers the wrong question
Merged
#81 ADR 0104: a provision may be answered by an adapter to the predecessor
Merged
#80 Issue 093: the successor proxy cannot serve what the predecessor still serves
Merged
#77 Issue 085 resolved
Merged
#76 Issues 088, 089 and 090, found fixing 085
Merged
#75 Adoption mode as built: ADRs 0101–0103, issues 084–086
Merged
#74 ADR 0100 (proposed): a node in use is adopted before it is converged
Merged
#73 Issue 083 resolved: nothing the control queue carries is lost while the store restarts
Merged
#72 Issues 081 and 082 resolved; 083 opened
Merged
#71 Issues 079 and 080, found by running the large mesh bed; 074's addendum
Merged
#70 ADR 0099; issues 077, 078 and 074 resolved; designs 08 and 20 amended
Merged
#69 ADR 0098; issue 076 opened and resolved; ADR 0097's base refusal live; ADR 0096 proven against the public hub; 074 down to one bed
Merged
#68 Multiple fixes: issues 064, 066 and 020 resolved; 074 narrowed to two beds
Merged
#67 Multiple fixes: ADRs 0094–0097; issues 069, 049, 046 resolved; 064's image half decided
Merged
#66 ADR 0093: a fixture that runs a module's runtime carries its name; 074 diagnosed; 075 resolved
Merged
#65 Issues 072 and 073 name their merges, the branches being gone
Merged
#64 Multiple fixes: status vocabulary aligned, 065/026/070/007 resolved, 066/069/049/046 located, 064 diagnosed
Merged
#63 Issue 072 diagnosed: genesis registers the manifest its build produced; design 17 says so
Merged
#62 ADR 0089: a bed reads the catalogue it proves; issue 073 diagnosed; issues 074 and 075 opened
Merged
#61 Issues 031, 035 and 054 name their merges, the branch being gone
Merged
#60 ADRs 0087 and 0088; issues 031, 035 and 054 resolved; issue 041 surveyed; issue 073 opened
Merged
#59 ADR 0086 (a secret reaches a process as a file), the vault shipped, issues 041 and 072
Merged
#58 The secrets vault: handoff, the amended decision, issues 069–071, and the reconciliation of open issues
Merged
#57 Graduate issues 067 and 068 — provider scoping and the secrets vault
Merged
#56 Issues 065 and 066 — the apply failure model's two gaps
Merged
#55 057 and 058 resolved — fixes merged and proven
Merged
#54 ADR 0083 and issues 057/058/060/063/064 — the P1 sweep
Merged
#53 Issue 059 resolved — the broker credential resolves the seat
Merged
#52 ADR 0082 and issues 042/048/061/062 — the registry is reached by name and trusted by the overlay
Merged
#51 Issue 060 — the mesh cannot build most of its own catalogue
Merged
#50 Issue 059 — the broker credential names the hub, not the broker's node
Merged
#49 ADR 0081: decisions are in the chain — no orphan records
Merged
#48 ADR 0080: the development cycle is checked, not trusted — plus review fixes
Merged
#47 Issue 058 — a provisioner runtime crash-loops until the overlay is up
Merged
#46 ADR 0079: foundation seats are named after their servers; issue 056 resolved
Merged
#45 Issue 055 resolved and proven; 056 and 057 opened
Merged
#44 Establish the repo for the completed Phase 0-3 build
Merged
#43 Glossary, the mesh-controller/foundation vocabulary, ADR 0076, Phase 3 closed
Merged
#42 Issue 047 — and the half that runs the other way
Merged
#41 Issue 047 — the firewall does not cover published container ports
Merged
#40 Issue 046 — an upstream image cannot be mirrored into the mesh's registry
Merged
#39 Installing ends with a builder, and the record says so
Merged
#38 A module names its base, so the mesh can act on what it notices
Merged
#37 Two graphs, the builder's arrival, and two findings from building on a live mesh
Merged
#36 Two graphs, and a build chain that orders itself
Merged
#35 Genesis clones from a mesh, and checks what it got
Merged
#34 The catalogue owns the module graph, and genesis builds rather than carries
Merged
#33 A module is a repository and a path, and installing is described to its end
Merged
#32 Genesis is a pivot, public routing is name-agnostic, and five issues the fake registry was hiding
Merged
#31 ADR 0055 — model access is answered by a licence or a node that hosts the model
Merged
#29 ADR 0054 — model usage is a vendor-neutral record at two grains
Merged
#28 ADR 0053 — a scheduled step is a container run on a recurring schedule
Merged
#27 ADR 0052 — a step that runs once before a container (issue 037 / run-once primitive)
Merged
#26 ADR 0051 — shared data is the operator's; a module is granted access (fixes issue 036)
Merged
#25 ADR 0050 (proposed) — model access is vendor-agnostic [awaiting ratification]
Merged
#24 Reconcile: adopt initialization's consolidated HQ as canonical, re-home this session's new work
Merged
#23 Issue 013 — a module cannot run its own code at a lifecycle phase
Merged
#12 Issues 011 and 012 — what the manifest review could not fix
Merged
#22 Playbook 06 — one feature, one branch, one MR per repo
Merged
#21 Issue 009 (fixed) + Issue 008 (resolved via ADR 0053) — module-runtime config & provider contract
Merged
#11 011: measure the graph against every facet a module carries
Merged
#10 The approval is the checkpoint, and what a declaration is
Merged
#9 Tier 0: the questions answered, the decisions taken, and the design
Merged
#8 The router is scenery, and a test defends a decision
Merged
#6 The scenario model, the lifecycle, and what the lab actually costs
Merged
#5 Hand the lab design off to mesh-lab
Merged
#4 The lab comes first, and its first scenario has no pipeline
Merged
#3 Publish-safe: remove two disclosures, and record Nox as the answer to 006
Merged
#2 Retire the HAL name where it points forward
Merged
#1 HQ: the as-is base layer, the process, and the names