diff --git a/AGENTS.md b/AGENTS.md index c0eedcb..bf2be93 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,5 +1,7 @@ # AGENTS.md - how to work in this repository +**Owner**: `git-rhizoid-builder` - the role that keeps git-rhizoid (this design log and the rhizoid tool), whichever session holds it (signing as `git-rhizoid-builder.RUN`); another session sends it the change - a message, or an upstream item naming git-rhizoid - and does not land here itself. + This repo is a small versioned "database" kept as plain files. The data lives as JSON lines, its tables declared in `tables.toml`; [tad](https://github.com/creation-guidelines/tad-engine), a released Rust tool, checks it, keeps it canonical and renders it, and CI enforces that it stays so. **Work on the content.** diff --git a/data/backlog.json b/data/backlog.json index ae0e7ce..272deca 100644 --- a/data/backlog.json +++ b/data/backlog.json @@ -1,13 +1,13 @@ -{"id":"design-consumption-side","title":"Design the consumption-side manifest","status":"open","note":"How a repo declares \"I depend on this org's fork of X at version Y\" and pulls it in - deliberately not designed yet, kept separate from the fork-management side.","opened":"2026-09-22"} -{"id":"implement-cli","title":"Implement the actual rhizoid CLI","status":"open","note":"Boundary layer implemented: manifest infra, 7 argenv-typed commands, 39 tests, real CI including MSRV all green (see implement-boundary-layer). init and remove fully work; add/import/update/status/refresh are typed and tested but stubbed, waiting on the GitHubPort adapter. Parked 2026-11-11: tad's duties move into ocoeco; this returns there, or with the first cutting. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-09-22"} -{"id":"verify-pages-root","title":"Verify Pages serves at the org root","status":"done","note":"git-rhizoid.github.io should serve at https://git-rhizoid.github.io/ once Pages is enabled here, since the repo name matches the org.github.io convention - not yet confirmed live.","opened":"2026-09-22"} -{"id":"decide-dot-github-repo","title":"Decide whether a separate git-rhizoid/.github repo is worth adding","status":"open","note":"For org-wide issue/PR template defaults - a different, smaller thing than this repo, and not yet built.","opened":"2026-09-22"} -{"id":"dc-check-blocks-empty-recovery","title":"dc.py check() blocks recovering from an all-empty table","status":"done","note":"Gone with the switch to tad in Rust (2026-11-11): tad has no rule that every field must appear on some line, so an empty table checks out and canon keeps it - tried on a copy.","opened":"2026-09-22"} -{"id":"tui-for-rhizoid","title":"Add a TUI for Rhizoid","status":"open","note":"Explicitly a later phase, after the CLI (init/add/import/update/status/refresh/remove) is working - not designed at all yet.","opened":"2026-09-22"} -{"id":"rhizcut","title":"rhizcut: the tool that takes a cutting","status":"open","note":"Named by the milestone rhizoid-carries-ocoeco's criteria but never recorded: found 2026-11-12 when ocoeco check followed every link. The milestone is right to depend on it.","opened":"2026-11-12"} -{"id":"slice-consumption","title":"Consumption mode for a slice: take a named list of files from a pinned release of a repository into one that has its own files","status":"open","note":"Found 2026-11-17 by grenudi/ideal-knowledge-base (research chain-follow-world, decision 2026-11-17-chain-follow-by-slice). Its chain - idealkb to device-template to device bases - lays a slice, not a repository: a source names what it gives (a generic list, files whole or the part between two marker lines), a follower pins a release and names its own files, and the verdict says whether the follower changed a generic file (idealkb's bin/follow.sh ends 3). rhizoid today takes a whole fork (a cutting); this is the consumption side design-consumption-side leaves open. follow.sh and update-pins.sh are the prototype; when rhizoid has it, idealkb can hand its chain over. Also lacking for that chain: the pin read from the follower's own file, a release gate (every follower answers before a release is tagged), and sending a changed generic file back as a patch. Also 2026-11-17: the tools home (linux-phone-oco/lab-tools) has the same slice case for the device-template files that go with a tool - the [boot] manifest skeleton, hook examples, an initramfs skeleton - beside the tool's own version pin (see cutting-as-cargo-dependency, followers-one-pin-bump). Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-11-17"} -{"id":"cutting-as-cargo-dependency","title":"A cutting consumed by a language manager: the patched fork of a Rust tool as a cargo git dependency at a pinned tag, written and bumped by rhizoid","status":"open","note":"Found 2026-11-17 by linux-phone-oco/docs (research bringup-home-follow-and-rhizoid, decision 2026-11-17-bringup-in-lab-tools). A device repository uses lab-tools' bringup as a pinned binary or cargo git dependency; when it must patch the tool itself before upstream takes the change, the true case is a cutting of lab-tools (tracking branch pristine, patch branch merged from it, clean patch back). What rhizoid lacks is the consumption side for it: the follower declares this tool, this cutting, this tag, and rhizoid writes the pin where the language manager reads it (Cargo.toml git tag or [patch] entry; a rust-script file's cargo header; a version line in a manifest) and bumps it when the tracking branch has a new release - the open item design-consumption-side, for a case that now has a user. Until then: a plain fork and a [patch] line by hand, recorded as a problem.","opened":"2026-11-17"} -{"id":"followers-one-pin-bump","title":"Many followers, one pin and one verdict: a slice, a cutting and a tool version bumped by the same weekly job","status":"open","note":"Found 2026-11-17 by linux-phone-oco/docs (same research). A device repository follows three sources - idealkb (a slice), device-template (a slice) and lab-tools (a tool version, maybe a cutting) - each with its own pin line, and today an updater (idealkb's update-pins.sh) only for the slices. Lacking: one pin file the follower owns (source, kind slice|cutting|tool, release), one command that bumps every pin to the newest release and opens a pull request per source, and one verdict (up to date, behind, own change to a generic file) that CI can gate on. update-pins.sh and follow.sh's exit 3 are the prototype; slice-consumption is the first kind. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-11-17"} -{"id":"send-back-writes-the-upstream-item","title":"Sending a change back: a patch to the source as a pull request, and the follower's own record of it","status":"open","note":"Found 2026-11-17 by linux-phone-oco/docs (same research). clean-patch-back says a diff of the patch branch against the pristine tracking branch is a clean patch; the CLI that makes it and opens the pull request is stubbed. The follower's bases keep an upstream item per change (idealkb: ikb upstream-item, form patch, draft, ready on the person's word, sent with the PR address, landed when released). Lacking: a rhizoid verb that, for a changed generic file or a patch branch, writes the patch, opens the pull request only after the person says ready, and returns the PR address and later the release that carried it, in a form the follower's record command takes - without rhizoid knowing that base's tables. It never sends in the person's name by itself. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-11-17"} -{"id":"status-over-every-edge","title":"rhizoid status: one read-only report over every edge a repository has - a slice (pin vs source release, followed files equal, own files on their way up), a tool pin (vs latest tag), a cutting (tracking vs upstream head) - exit 1 on drift","status":"open","note":"Found 2026-11-18 by linux-phone-oco (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)). The first command to build: no risk, it replaces docs' graph-drift.sh (36 FAIL today) and passes it line for line. Edges are read from the pin files followers already own (idealkb.toml, devicebase.toml, lab.toml [tools], a fork's .rhizoid/module.toml), so the follower lists derive from the pins. Rust with argenv, the CLI's status command.","opened":"2026-11-18"} -{"id":"follow-by-conformance","title":"rhizoid follow lays a slice exactly as idealkb's bin/follow.sh does, proven by its fixtures, before update-pins calls it","status":"open","note":"Found 2026-11-18 by linux-phone-oco (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)). Passes grenudi/ideal-knowledge-base bin/test-follow.sh byte for byte and keeps three things its owner names: the pin names its source, one owner per file (check-one-owner), the followers' gate before a release (followers-answer.sh). Adds #! from = DIR/ and own needing an upstream item (idealkb items idealkb-slice-from-prefix, idealkb-own-needs-item) only after idealkb has them. Until it passes, the shell is the tool. Blocked by status-over-every-edge.","opened":"2026-11-18"} +{"id":"design-consumption-side","title":"Design the consumption-side manifest","status":"open","note":"How a repo declares \"I depend on this org's fork of X at version Y\" and pulls it in - deliberately not designed yet, kept separate from the fork-management side.","opened":"2026-09-22","rank":null} +{"id":"implement-cli","title":"Implement the actual rhizoid CLI","status":"in-progress","note":"Boundary layer implemented: manifest infra, 7 argenv-typed commands, 39 tests, real CI including MSRV all green (see implement-boundary-layer). init and remove fully work; add/import/update/status/refresh are typed and tested but stubbed, waiting on the GitHubPort adapter. Parked 2026-11-11: tad's duties move into ocoeco; this returns there, or with the first cutting. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word. Unparked 2026-11-18, the author said: 'yes, if its the best we came up with, grounded in our extensive research and consideration, which it seems it did, so yes' (through the Top Coordinator, 2026-11-18; docs session-log 2026-11-18-author-yes-device-layer-and-rhizoid): git-rhizoid has the research's scope and order - status-over-every-edge, follow-by-conformance, send-back-writes-the-upstream-item, then cuttings - each replacing shell only once it passes the shell's tests. Owner: git-rhizoid-builder. This item is the umbrella; its first step is status-over-every-edge.","opened":"2026-09-22","rank":null} +{"id":"verify-pages-root","title":"Verify Pages serves at the org root","status":"done","note":"git-rhizoid.github.io should serve at https://git-rhizoid.github.io/ once Pages is enabled here, since the repo name matches the org.github.io convention - not yet confirmed live.","opened":"2026-09-22","rank":null} +{"id":"decide-dot-github-repo","title":"Decide whether a separate git-rhizoid/.github repo is worth adding","status":"open","note":"For org-wide issue/PR template defaults - a different, smaller thing than this repo, and not yet built.","opened":"2026-09-22","rank":null} +{"id":"dc-check-blocks-empty-recovery","title":"dc.py check() blocks recovering from an all-empty table","status":"done","note":"Gone with the switch to tad in Rust (2026-11-11): tad has no rule that every field must appear on some line, so an empty table checks out and canon keeps it - tried on a copy.","opened":"2026-09-22","rank":null} +{"id":"tui-for-rhizoid","title":"Add a TUI for Rhizoid","status":"open","note":"Explicitly a later phase, after the CLI (init/add/import/update/status/refresh/remove) is working - not designed at all yet.","opened":"2026-09-22","rank":null} +{"id":"rhizcut","title":"rhizcut: the tool that takes a cutting","status":"open","note":"Named by the milestone rhizoid-carries-ocoeco's criteria but never recorded: found 2026-11-12 when ocoeco check followed every link. The milestone is right to depend on it.","opened":"2026-11-12","rank":6} +{"id":"slice-consumption","title":"Consumption mode for a slice: take a named list of files from a pinned release of a repository into one that has its own files","status":"open","note":"Found 2026-11-17 by grenudi/ideal-knowledge-base (research chain-follow-world, decision 2026-11-17-chain-follow-by-slice). Its chain - idealkb to device-template to device bases - lays a slice, not a repository: a source names what it gives (a generic list, files whole or the part between two marker lines), a follower pins a release and names its own files, and the verdict says whether the follower changed a generic file (idealkb's bin/follow.sh ends 3). rhizoid today takes a whole fork (a cutting); this is the consumption side design-consumption-side leaves open. follow.sh and update-pins.sh are the prototype; when rhizoid has it, idealkb can hand its chain over. Also lacking for that chain: the pin read from the follower's own file, a release gate (every follower answers before a release is tagged), and sending a changed generic file back as a patch. Also 2026-11-17: the tools home (linux-phone-oco/lab-tools) has the same slice case for the device-template files that go with a tool - the [boot] manifest skeleton, hook examples, an initramfs skeleton - beside the tool's own version pin (see cutting-as-cargo-dependency, followers-one-pin-bump). Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-11-17","rank":3} +{"id":"cutting-as-cargo-dependency","title":"A cutting consumed by a language manager: the patched fork of a Rust tool as a cargo git dependency at a pinned tag, written and bumped by rhizoid","status":"open","note":"Found 2026-11-17 by linux-phone-oco/docs (research bringup-home-follow-and-rhizoid, decision 2026-11-17-bringup-in-lab-tools). A device repository uses lab-tools' bringup as a pinned binary or cargo git dependency; when it must patch the tool itself before upstream takes the change, the true case is a cutting of lab-tools (tracking branch pristine, patch branch merged from it, clean patch back). What rhizoid lacks is the consumption side for it: the follower declares this tool, this cutting, this tag, and rhizoid writes the pin where the language manager reads it (Cargo.toml git tag or [patch] entry; a rust-script file's cargo header; a version line in a manifest) and bumps it when the tracking branch has a new release - the open item design-consumption-side, for a case that now has a user. Until then: a plain fork and a [patch] line by hand, recorded as a problem.","opened":"2026-11-17","rank":7} +{"id":"followers-one-pin-bump","title":"Many followers, one pin and one verdict: a slice, a cutting and a tool version bumped by the same weekly job","status":"open","note":"Found 2026-11-17 by linux-phone-oco/docs (same research). A device repository follows three sources - idealkb (a slice), device-template (a slice) and lab-tools (a tool version, maybe a cutting) - each with its own pin line, and today an updater (idealkb's update-pins.sh) only for the slices. Lacking: one pin file the follower owns (source, kind slice|cutting|tool, release), one command that bumps every pin to the newest release and opens a pull request per source, and one verdict (up to date, behind, own change to a generic file) that CI can gate on. update-pins.sh and follow.sh's exit 3 are the prototype; slice-consumption is the first kind. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-11-17","rank":4} +{"id":"send-back-writes-the-upstream-item","title":"Sending a change back: a patch to the source as a pull request, and the follower's own record of it","status":"open","note":"Found 2026-11-17 by linux-phone-oco/docs (same research). clean-patch-back says a diff of the patch branch against the pristine tracking branch is a clean patch; the CLI that makes it and opens the pull request is stubbed. The follower's bases keep an upstream item per change (idealkb: ikb upstream-item, form patch, draft, ready on the person's word, sent with the PR address, landed when released). Lacking: a rhizoid verb that, for a changed generic file or a patch branch, writes the patch, opens the pull request only after the person says ready, and returns the PR address and later the release that carried it, in a form the follower's record command takes - without rhizoid knowing that base's tables. It never sends in the person's name by itself. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word.","opened":"2026-11-17","rank":5} +{"id":"status-over-every-edge","title":"rhizoid status: one read-only report over every edge a repository has - a slice (pin vs source release, followed files equal, own files on their way up), a tool pin (vs latest tag), a cutting (tracking vs upstream head) - exit 1 on drift","status":"in-progress","note":"Found 2026-11-18 by linux-phone-oco (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)). The first command to build: no risk, it replaces docs' graph-drift.sh (36 FAIL today) and passes it line for line. Edges are read from the pin files followers already own (idealkb.toml, devicebase.toml, lab.toml [tools], a fork's .rhizoid/module.toml), so the follower lists derive from the pins. Rust with argenv, the CLI's status command. Unparked 2026-11-18 (see implement-cli): first in the author's order. Built in rhizoid-cli: status reads a graph file of the edges and each follower's own pin files at origin/main, reports every edge current, behind or moved by hand, exits 1 on drift, and is proven by graph-drift.sh's cases as fixtures and by agreeing with graph-drift.sh run on the real graph.","opened":"2026-11-18","rank":1} +{"id":"follow-by-conformance","title":"rhizoid follow lays a slice exactly as idealkb's bin/follow.sh does, proven by its fixtures, before update-pins calls it","status":"open","note":"Found 2026-11-18 by linux-phone-oco (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)). Passes grenudi/ideal-knowledge-base bin/test-follow.sh byte for byte and keeps three things its owner names: the pin names its source, one owner per file (check-one-owner), the followers' gate before a release (followers-answer.sh). Adds #! from = DIR/ and own needing an upstream item (idealkb items idealkb-slice-from-prefix, idealkb-own-needs-item) only after idealkb has them. Until it passes, the shell is the tool. Blocked by status-over-every-edge.","opened":"2026-11-18","rank":2} diff --git a/data/glimpses.json b/data/glimpses.json index c6b5598..97504e4 100644 --- a/data/glimpses.json +++ b/data/glimpses.json @@ -12,3 +12,4 @@ {"id":"g-20261117-193335","at":"2026-11-17T19:33:35Z","by":"research-bringup-tools","kind":"docs","summary":"Backlog: what a tools home needs of rhizoid (cargo pin, one pin bump, send back)"} {"id":"g-20261118-144738","at":"2026-11-18T14:47:38Z","by":"rhizoid-graph-research","kind":"docs","summary":"Backlog: rhizoid's scope - the follow tool for every edge, status first, by conformance"} {"id":"g-20261118-145705","at":"2026-11-18T14:57:05Z","by":"tad update-pins","kind":"build","summary":"tad 0.7.1: the pin moved, the data and documents re-rendered"} +{"id":"g-20261118-150749","at":"2026-11-18T15:07:49Z","by":"git-rhizoid-builder.b1c7f3","kind":"docs","summary":"git-rhizoid unparked: items ranked in the research's order, owner named"} diff --git a/data/session_log.json b/data/session_log.json index 784225e..541d06e 100644 --- a/data/session_log.json +++ b/data/session_log.json @@ -19,3 +19,4 @@ {"id":"2026-11-11-tad-in-rust","entry_date":"2026-11-11","title":"tad in Rust replaces the vendored Python engine","done":"This repository moved to tad in Rust: tables.toml is the authority, tad comes from its pinned release, the vendored .tad, schema.sql, load.sql and checks/ are gone, and AGENTS.md got simpler. The open item about dc.py blocking recovery from an empty table closed with it.","considered":null,"rejected":null} {"id":"2026-11-11-one-word-summary","entry_date":"2026-11-11","title":"A concept's text is its summary","done":"The concepts table's statement field is now summary, the word the shared language (ocoeco's language.toml) and twenty other projects use; the observatory showed this repository's concepts without their text because of it. Found by checking every project against the shared language.","considered":"Teaching the shared language a second word for the same thing.","rejected":"That: one role, one word."} {"id":"2026-11-18-scope-every-edge","entry_date":"2026-11-18","title":"Scope from linux-phone-oco's graph research: the follow tool for every edge, status first, by conformance","done":"A research lead of linux-phone-oco measured its repository graph (12 edges, 3 moved by a job, 6 by hand, 5 behind) and the world (no Rust or shell tool carries root-level files down and changes up; only copybara, on a JVM; josh needs a monorepo; subtree/subrepo need a prefix - the tad/subrepo lesson of 2026-09-22 again). It filed status-over-every-edge and follow-by-conformance here and reshaped slice-consumption, followers-one-pin-bump, send-back-writes-the-upstream-item and implement-cli to that order (source linux-phone-oco-base-graph).","considered":"Porting idealkb's follow.sh into rhizoid now; rhizoid as a template engine; rows as an edge kind.","rejected":"A port before conformance (the shell works and is tested); a template engine or a merge of data (bases are data); rows (docs' feeds own them)."} +{"id":"2026-11-18-unparked-by-the-authors-yes","entry_date":"2026-11-18","title":"git-rhizoid unparked by the author's yes: the follow tool for every edge, in the research's order","done":"The author's word, verbatim (through the Top Coordinator, 2026-11-18, recorded in linux-phone-oco/docs as session-log 2026-11-18-author-yes-device-layer-and-rhizoid): 'yes, if its the best we came up with, grounded in our extensive research and consideration, which it seems it did, so yes'. It unparks implement-cli with the scope of 2026-11-18-scope-every-edge and its order, now the backlog's rank: 1 status-over-every-edge (passes graph-drift.sh), 2 follow-by-conformance (passes idealkb's bin/test-follow.sh, keeping the pin names its source, one owner per file, the followers-answer gate), 3-4 slice-consumption and followers-one-pin-bump, 5 send-back, 6-7 cuttings (rhizcut, cutting-as-cargo-dependency). Owner: git-rhizoid-builder, who keeps AGENTS.md's Owner line here and in git-rhizoid/rhizoid. Each step replaces shell only once it passes; idealkb's update-pins and follow.sh stay until step 2 passes.","considered":"Unparking only status and leaving the rest parked; ranking only the first two.","rejected":"Leaving the order in notes: the rank is a field now, so the next builder reads it rather than infers it."} diff --git a/docs/backlog.md b/docs/backlog.md index b3b4f24..d385e0f 100644 --- a/docs/backlog.md +++ b/docs/backlog.md @@ -19,10 +19,10 @@ Opened ### Implement the actual rhizoid CLI Status -: open +: in-progress Note -: Boundary layer implemented: manifest infra, 7 argenv-typed commands, 39 tests, real CI including MSRV all green (see implement-boundary-layer). init and remove fully work; add/import/update/status/refresh are typed and tested but stubbed, waiting on the GitHubPort adapter. Parked 2026-11-11: tad's duties move into ocoeco; this returns there, or with the first cutting. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word. +: Boundary layer implemented: manifest infra, 7 argenv-typed commands, 39 tests, real CI including MSRV all green (see implement-boundary-layer). init and remove fully work; add/import/update/status/refresh are typed and tested but stubbed, waiting on the GitHubPort adapter. Parked 2026-11-11: tad's duties move into ocoeco; this returns there, or with the first cutting. Reshaped 2026-11-18 (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)): rhizoid's scope is the follow tool for every edge (slice, tool pin, cutting), built in order status-over-every-edge, follow-by-conformance, send-back, cuttings; each replaces shell only once it passes the shell's tests. Unparking implement-cli waits on the author's word. Unparked 2026-11-18, the author said: 'yes, if its the best we came up with, grounded in our extensive research and consideration, which it seems it did, so yes' (through the Top Coordinator, 2026-11-18; docs session-log 2026-11-18-author-yes-device-layer-and-rhizoid): git-rhizoid has the research's scope and order - status-over-every-edge, follow-by-conformance, send-back-writes-the-upstream-item, then cuttings - each replacing shell only once it passes the shell's tests. Owner: git-rhizoid-builder. This item is the umbrella; its first step is status-over-every-edge. Opened : 2026-09-22 @@ -92,6 +92,9 @@ Note Opened : 2026-11-12 +Rank +: 6 + ### Consumption mode for a slice: take a named list of files from a pinned release of a repository into one that has its own files @@ -105,6 +108,9 @@ Note Opened : 2026-11-17 +Rank +: 3 + ### A cutting consumed by a language manager: the patched fork of a Rust tool as a cargo git dependency at a pinned tag, written and bumped by rhizoid @@ -118,6 +124,9 @@ Note Opened : 2026-11-17 +Rank +: 7 + ### Many followers, one pin and one verdict: a slice, a cutting and a tool version bumped by the same weekly job @@ -131,6 +140,9 @@ Note Opened : 2026-11-17 +Rank +: 4 + ### Sending a change back: a patch to the source as a pull request, and the follower's own record of it @@ -144,19 +156,25 @@ Note Opened : 2026-11-17 +Rank +: 5 + ### rhizoid status: one read-only report over every edge a repository has - a slice (pin vs source release, followed files equal, own files on their way up), a tool pin (vs latest tag), a cutting (tracking vs upstream head) - exit 1 on drift Status -: open +: in-progress Note -: Found 2026-11-18 by linux-phone-oco (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)). The first command to build: no risk, it replaces docs' graph-drift.sh (36 FAIL today) and passes it line for line. Edges are read from the pin files followers already own (idealkb.toml, devicebase.toml, lab.toml [tools], a fork's .rhizoid/module.toml), so the follower lists derive from the pins. Rust with argenv, the CLI's status command. +: Found 2026-11-18 by linux-phone-oco (docs research base-graph-measured, base-graph-world; decision 2026-11-18-device-layer-from-docs; upstream item rhizoid-scope-every-edge (linux-phone-oco/docs)). The first command to build: no risk, it replaces docs' graph-drift.sh (36 FAIL today) and passes it line for line. Edges are read from the pin files followers already own (idealkb.toml, devicebase.toml, lab.toml [tools], a fork's .rhizoid/module.toml), so the follower lists derive from the pins. Rust with argenv, the CLI's status command. Unparked 2026-11-18 (see implement-cli): first in the author's order. Built in rhizoid-cli: status reads a graph file of the edges and each follower's own pin files at origin/main, reports every edge current, behind or moved by hand, exits 1 on drift, and is proven by graph-drift.sh's cases as fixtures and by agreeing with graph-drift.sh run on the real graph. Opened : 2026-11-18 +Rank +: 1 + ### rhizoid follow lays a slice exactly as idealkb's bin/follow.sh does, proven by its fixtures, before update-pins calls it @@ -169,3 +187,6 @@ Note Opened : 2026-11-18 + +Rank +: 2 diff --git a/docs/index.md b/docs/index.md index 6cfd696..fe79317 100644 --- a/docs/index.md +++ b/docs/index.md @@ -4,5 +4,5 @@ - [Backlog](backlog.md): 13 - [Concepts](concepts.md): 14 -- [Session Log](session_log.md): 21 +- [Session Log](session_log.md): 22 - [Sources](sources.md): 12 diff --git a/docs/session_log.md b/docs/session_log.md index 9cce18d..45d6c80 100644 --- a/docs/session_log.md +++ b/docs/session_log.md @@ -322,3 +322,21 @@ Considered Rejected : A port before conformance (the shell works and is tested); a template engine or a merge of data (bases are data); rows (docs' feeds own them). + +--- + + + +### git-rhizoid unparked by the author's yes: the follow tool for every edge, in the research's order + +Entry date +: 2026-11-18 + +Done +: The author's word, verbatim (through the Top Coordinator, 2026-11-18, recorded in linux-phone-oco/docs as session-log 2026-11-18-author-yes-device-layer-and-rhizoid): 'yes, if its the best we came up with, grounded in our extensive research and consideration, which it seems it did, so yes'. It unparks implement-cli with the scope of 2026-11-18-scope-every-edge and its order, now the backlog's rank: 1 status-over-every-edge (passes graph-drift.sh), 2 follow-by-conformance (passes idealkb's bin/test-follow.sh, keeping the pin names its source, one owner per file, the followers-answer gate), 3-4 slice-consumption and followers-one-pin-bump, 5 send-back, 6-7 cuttings (rhizcut, cutting-as-cargo-dependency). Owner: git-rhizoid-builder, who keeps AGENTS.md's Owner line here and in git-rhizoid/rhizoid. Each step replaces shell only once it passes; idealkb's update-pins and follow.sh stay until step 2 passes. + +Considered +: Unparking only status and leaving the rest parked; ranking only the first two. + +Rejected +: Leaving the order in notes: the rank is a field now, so the next builder reads it rather than infers it. diff --git a/tables.toml b/tables.toml index 59d9ee5..05d6aba 100644 --- a/tables.toml +++ b/tables.toml @@ -29,6 +29,11 @@ name = "opened" type = "date" required = true +# where the item stands in the order the author unparked git-rhizoid with (1 first; empty: after the ranked) +[[tables.backlog.fields]] +name = "rank" +type = "integer" + [tables.concept_sources] key = ["concept_id", "source_id"]