1768 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
jochen	91f2a61763	ADR 0274, progressive insight: the router judges whether a channel can carry the ask	2026-10-10 13:04:22 +02:00
mesh-admin	cf529b567c	Merge pull request 'ADR 0275, to-be 53: the issue tracker's module is mesh-issues, holding the seat issue-tracker' (#272) from decisions/0275-the-issue-trackers-module-is-mesh-issues into main	2026-10-10 10:59:54 +00:00
jochen	8d9eae7224	ADR 0275, to-be 53: the issue tracker's module is mesh-issues, holding the seat issue-tracker ... The operator named the module on 2026-10-10: the mesh's own parts carry the mesh- prefix, and the seat is the role. A dated insight in ADR 0275 says so, and that compare-and-set state was already in the runtime (ADR 0259): slice 1 added the SDK's Increment. To-be 53 and the glossary say the same, and the design is handed to mesh-catalog and mesh-sdk (in progress).	2026-10-10 12:52:37 +02:00
mesh-admin	2798306de7	Merge pull request 'ADR 0276: merges are assembled in a rolling window, and each batch is delivered by one walk (issue 362)' (#271) from decisions/0276-merges-are-assembled-in-a-rolling-window into main	2026-10-10 10:44:53 +00:00
jochen	d159bfa36a	ADR 0276: merges are assembled in a rolling window, and each batch is delivered by one walk ... Two catalogue merges 18 s apart opened two walks; the second superseded the first and nothing gave it its word for 58 minutes (issue 362). The operator decided that merges are collected in a rolling merge window (90 s, at most 10 min) and each batch is walked once, one commit per repository (the later one of a repository, which contains the earlier), one walk at a time; the walk-to-delivery bookkeeping is repaired too and every wait has a condition. Amends to-be 47 and 10, adds merge window and batch to the glossary, and corrects the issue's account of the S16 condition.	2026-10-10 12:39:13 +02:00
mesh-admin	9395c752cc	Merge pull request 'ADR 0275 and to-be 53: the mesh numbers and tracks its issues in a module of its own' (#270) from decisions/the-mesh-keeps-its-own-issues into main	2026-10-10 10:34:51 +00:00
jochen	015ff1adfb	Graduate research 042 into ADR 0275 and to-be 53, so issue numbers stop colliding ... Numbers taken by reading a repository many branches write at once collide; one counter in a module of the mesh's own, advanced by compare-and-set, ends that at the source. The operator delegated the five open questions on 2026-10-10; each is decided as the research recommended. The glossary gains the issue tracker, retires "ticketing system" and lists ticket as a homonym, since ADR 0258 already uses it for an answer's one-time token.	2026-10-10 12:31:32 +02:00
mesh-admin	835d7acc1a	Merge pull request 'ADR 0274: an agent proposes a shared instruction section, and every node takes it only on the operator's warrant' (#268) from decisions/0274-shared-instructions-on-the-operators-approval into main	2026-10-10 10:09:39 +00:00
jochen	b18bf66ae2	ADR 0274 accepted, with its two limits: to-be 36 rests on it	2026-10-10 12:06:51 +02:00
jochen	a211644102	ADR 0274: variation selectors, blank letters and every heading form refused	2026-10-10 12:06:38 +02:00
jochen	842ed805cc	ADR 0274: hold the review's findings — invisible text, any @, the record judged at decide, older approvals never undo later ones	2026-10-10 12:06:38 +02:00
jochen	891608814e	ADR 0274: an agent proposes a shared instruction section, and every node takes it only on the operator's warrant ... The operator asked for mesh tools to add shared instructions and context. Issue 340 made that text the terminal's until a surface of the operator's own exists; the operator channel is that surface. Proposed, for the operator to accept.	2026-10-10 12:06:38 +02:00
mesh-admin	7c866e7356	Merge pull request 'Issue 364: the merge gate refuses a module that uses a seat another module declares' (#269) from issues/364-the-gate-refuses-a-module-that-uses-a-seat-another-declares into main	2026-10-10 02:05:20 +00:00
jochen	7b096f2471	Issue 364: the merge gate refuses a module that uses a seat another module declares	2026-10-10 03:53:06 +02:00
mesh-admin	d457921486	Merge pull request 'Issue 363: ADR 0267 was decided and never built' (#266) from issues/363-adr-0267-was-decided-and-never-built into main	2026-10-10 01:34:44 +00:00
mesh-admin	014554ce9b	Merge pull request 'Research 042: the mesh keeps its own issues' (#267) from research/042-the-mesh-keeps-its-own-issues into main	2026-10-10 01:02:22 +00:00
mesh-admin	591731ab54	Merge pull request 'Issue 341: a merge check judges the pull request's head, not what merging it makes' (#242) from issues/341-a-merge-check-judges-the-head-not-the-merge into main	2026-10-10 01:02:09 +00:00
mesh-admin	b106518cda	Merge pull request 'Issue 338: a module built from a shared repository moves on every merge to it' (#231) from issues/338-a-module-built-from-a-shared-repository-moves-on-every-merge-to-it into main	2026-10-10 01:01:58 +00:00
jochen	028f3b6ae5	Research 042: the mesh keeps its own issues ... Opens the effort the operator asked for on 2026-10-10: an issues module on the bus that hands out numbers atomically, so agents stop colliding on them, and takes in the 357 issue folders. Findings cover the first slice, where the truth lives, the import, conditions, views, and hits as a model.	2026-10-10 02:58:37 +02:00
jochen	f45f5f6f20	Issue 363: ADR 0267 was decided and never built, so a controller merge still moves three modules ... The operator took the rule as live. Track its build, as issue 354 does a deferred rename.	2026-10-10 02:46:35 +02:00
mesh-admin	503e144ab6	Merge pull request 'Issue 361: the setuid search shows its progress, and the operator can ask for a fresh one at the terminal' (#265) from issues/361-the-setuid-search-shows-its-progress into main	2026-10-10 00:06:34 +00:00
jochen	2d0a6ba4bc	Issue 361: a setuid find counts only where the agent account can execute it	2026-10-10 02:00:09 +02:00
jochenandClaude	a8e9a9afd4	Issue 361: the setuid search shows its progress, and the operator can ask for a fresh one at the terminal ... Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-10 01:55:52 +02:00
mesh-admin	c2d98bc61b	Merge pull request 'ADR 0266: the control node's agent account is named nox' (#264) from decisions/0266-the-agent-account-is-named-nox into main	2026-10-09 23:32:58 +00:00
mesh-admin	851a5e9f45	Merge pull request 'Issue 362: two merges seconds apart left their delivery waiting for a person' (#263) from issues/362-two-merges-seconds-apart-left-their-delivery-waiting-for-a-person into main	2026-10-09 23:32:52 +00:00
jochen	997e422a32	ADR 0266: the control node's agent account is nox, the operator's choice; the ways not judged are tracked by issue 344	2026-10-10 01:29:42 +02:00
jochen	496452fb54	Issue 362: two merges seconds apart left their delivery waiting for a person, because a walk at a later commit matched no live delivery; issue 349 points at it	2026-10-10 01:28:33 +02:00
mesh-admin	511cea04f2	Merge pull request 'Issue 361: the control-node's agent account is never judged, because its search for setuid programs cannot finish in fifteen minutes' (#261) from issues/361-the-control-nodes-agent-account-is-never-judged into main	2026-10-09 23:18:48 +00:00
jochen	94719d4662	Issue 361: say when a search runs as the fix does it	2026-10-10 01:12:19 +02:00
jochen	46f89cd102	Issue 361: record the review of the fix and what it changed	2026-10-10 01:12:02 +02:00
mesh-admin	288da29d94	Merge pull request 'Research 041: the agent's session runs confined, instead of being proven by a disk-wide search' (#262) from research/041-the-agents-session-runs-confined into main	2026-10-09 23:07:33 +00:00
jochen	4bc0919102	Research 041: the agent's session runs confined, instead of being proven by a disk-wide search ... The setuid search did not finish within its bound on the control-node, so no approval proven there is honoured; a confined start may answer the question ADR 0259 asks directly, at a cost that does not grow with the disks.	2026-10-10 01:04:02 +02:00
jochen	c0c7515e06	Issue 361: the control-node's agent account is never judged, because its search for setuid programs cannot finish in fifteen minutes	2026-10-10 01:03:51 +02:00
mesh-admin	a8b9be8d7f	Merge pull request 'Issue 360: the operator cannot choose a notification's action on a touchpad' (#260) from issues/360-the-operator-cannot-choose-a-notifications-action-on-a-touchpad into main	2026-10-09 22:21:30 +00:00
jochen	fe970e2f00	Issue 360: the operator cannot choose a notification's action on a touchpad ... The desk's actions sit on dunst's middle click, which a touchpad cannot give, and the context menu names a command dunst's PATH does not hold. Located in the dunst module; dunst's own code settles what a tap with do_action does.	2026-10-10 00:07:01 +02:00
mesh-admin	c51aedea22	Merge pull request 'Issue 359: a secret given reached the operator as "needs a look", and nothing said why' (#259) from issues/359-a-secret-given-reached-the-operator-as-needs-a-look into main	2026-10-09 22:00:16 +00:00
jochen	163521f32e	Issue 359: a secret given reached the operator as "needs a look", because its words held a clock time and the fallback was silent	2026-10-09 23:40:57 +02:00
mesh-admin	32c0f6efb1	Merge pull request 'Issue 358: a mesh directory outside a home is changed by path, through any link; issue 356 points at it' (#258) from issues/358-a-mesh-directory-outside-a-home-is-changed-by-path into main	2026-10-09 18:08:04 +00:00
jochen	e68d0ffa1d	Issue 358: a mesh directory outside a home is changed by path, through any link; issue 356 points at it ... The confirmation review of issue 356 found that the by-path chmod and chown of an ordinary mesh directory outside a home follows any link in its path. Issue 356 closed it for a handed-over directory, on every apply; the general gap is older and wider, and is recorded here rather than fixed in passing.	2026-10-09 19:59:06 +02:00
mesh-admin	fbaa8e16e6	Merge pull request 'Issue 353: the controller asked before the bus held its grant' (#253) from issues/353-the-controller-asked-before-the-bus-held-its-grant into main	2026-10-09 17:57:38 +00:00
mesh-admin	0e7af9988a	Merge pull request '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' (#256) from issues/356-the-operators-command-ran-a-stale-engine-and-a-hand-over-had-no-channel into main	2026-10-09 17:57:18 +00:00
jochen	2cb779d06f	Issue 354: quote the condition's old words, which the daemons' lines check refuses as a line to type	2026-10-09 19:46:36 +02:00
jochen	d1b42b7430	Merge remote-tracking branch 'origin/main' into issues/356-the-operators-command-ran-a-stale-engine-and-a-hand-over-had-no-channel	2026-10-09 19:46:03 +02:00
jochen	19776115ef	Issue 356: the subject proves nothing, the signature does; the apply refuses a link at use ... The review of 2026-10-09 proved a responder can reach the hand-over's subject through a reply, and that the apply followed a link the hand-over had refused. The record no longer says only the controller may publish there: it says the ask is signed with the mesh's key and verified by the engine, and that a handed-over directory is changed through a descriptor that followed no link. To-be 45's writers table gains the row for a hand-over asked of a machine.	2026-10-09 19:45:54 +02:00
jschoubben	adbd57a1f9	Issue 353: the condition cleared at 18:11:44, about 15 minutes after the last refusal, not an hour after	2026-10-09 19:35:09 +02:00
mesh-admin	b962e87cae	Merge pull request 'cycle.py: skip a rejected option by its ## section, so one under a ### subheading is skipped too' (#257) from fix/cycle-skips-rejected-options-by-their-section into main	2026-10-09 17:33:52 +00:00
jochen	189dbcef7a	Skip a rejected option by its chapter, so one under a ### subheading is skipped too ... cycle.py skipped a rejected option only when "Options rejected" was its nearest heading; a record that lists its options under ### subheadings of "## Considered Options" had them held as deferrals.	2026-10-09 19:32:16 +02:00
mesh-admin	169200fe55	Merge pull request 'Issue 354: a decided rename was never scheduled, and a record that defers work names its issue' (#255) from issues/354-a-decided-rename-was-never-scheduled-and-the-operator-believed-it-live into main	2026-10-09 17:31:45 +00:00
jochen	2349f4bb63	Hold an insight to the deferrals it speaks about, and name what ADR 0273 left undecided ... A review found the check too lenient: an issue cited as context beside a deferral passed it, and one insight excused every deferral in a record. The tracking issue is now named as tracking it, an insight covers only its section or what it quotes, and the phrases include "not decided here", "postponed" and "future work". ADR 0273's four undecided items get issue 357.	2026-10-09 19:29:18 +02:00
jochen	85da2fb93f	Issue 354: a decided rename was never scheduled, and a record that defers work names its issue ... ADR 0244 left the code renames of the node-engine and the tool runner for later with no issue, owner or date, and two days on the operator believed them live. Open the issue with the inventory, the risk and a staged plan; add the rule to playbooks 02 and 04, as a dated insight on ADR 0244, and as a cycle.py check that found the same gap in ADR 0270 (issue 355).	2026-10-09 19:27:05 +02:00