2026-10-13 - 2026-11-13
Overview
261 Pull requests merged by 2 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)