Open Commons ObservatoryEnglish·Русский
РизомаИдеяСутьНасколько мы близкиПонятия и решенияБэклогЖурналСделано работой

Бэклог

Работа впереди — и уже сделанная.

Открыто · 26

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

git-rhizoid.github.io

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 g…

Decide whether a separate git-rhizoid/.github repo is worth adding

git-rhizoid.github.io

For org-wide issue/PR template defaults - a different, smaller thing than this repo, and not yet built.

Design the consumption-side manifest

git-rhizoid.github.io

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.

Many followers, one pin and one verdict: a slice, a cutting and a tool version bumped by the same weekly job

git-rhizoid.github.io

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) - eac…

Implement the actual rhizoid CLI

git-rhizoid.github.io

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/ref…

rhizcut: the tool that takes a cutting

git-rhizoid.github.io

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.

Sending a change back: a patch to the source as a pull request, and the follower's own record of it

git-rhizoid.github.io

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 pu…

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

git-rhizoid.github.io

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…

Add a TUI for Rhizoid

git-rhizoid.github.io

Explicitly a later phase, after the CLI (init/add/import/update/status/refresh/remove) is working - not designed at all yet.

The first user ahead on day one

rhizome

The tool that helps one person, alone, at once - the only bar that matters for adoption.

Phase 0: a reproducible environment

rhizome

A pinned toolchain; empty crate stubs build.

Phase 1: load a workspace and list what is in it

rhizome

The extraction pipeline wires together, on a tiny fixture kept for ever.

Phase 2: real connections, not text

rhizome

References resolved semantically into an adjacency list.

Phase 3: identity from structure

rhizome

Four checks: determinism; a renamed local changes nothing; a renamed item keeps its hash; one changed line cascades up and nowhere else.

Phase 4: one shared store, a warm daemon

rhizome

Four tables: hash to form and references, hash to source span, name to hash, the reverse index.

Phase 5: graft - the round trip

rhizome

A closure walked, emitted verbatim, built and tested: identity survived the trip and the output runs.

Phase 6: sync by difference

rhizome

Two stores compared; only what differs moves.

Phase 7: graft something real, and write down what breaks

rhizome

One function out of a small real crate; the deliverable is the honest list of gaps.

Changing things while they run

rhizome

The index of where things live; changes classified beforehand.

The reach-against-change engine

rhizome

Conflicts resolved by computing what a consumer reaches against what changed; the same engine for impact and for live-swap classes.

Conjuring a whole project

rhizome

Many entry points; the full rz verbs; a real transport in place of local sync.

Layers and predicates

rhizome

Additive pieces with conditions.

Rhizoid's repositories under this organization

rhizome

Offered by the author; a transfer changes their addresses (its design log's site is tied to its organization's name), so it is to be done deliberately. The Rhizome lens gathers Rhizoid where it is mea…

The warm base and confinement

rhizome

The genome process; a shoot's world derived from its closure.

Hypha grown from its own graph

rhizome

The fixpoint: built from the graph, it re-emits itself to the same hash.

Views: everything visible, nothing present

rhizome

The filesystem view; the editor that navigates relationships; values beside the code.

В работе · 0

Готово · 4

dc.py check() blocks recovering from an all-empty table

git-rhizoid.github.io

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.

Verify Pages serves at the org root

git-rhizoid.github.io

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.

The manifesto

rhizome

Stop managing software. Start growing it. - the whole idea, for a reader who does not write software (MANIFESTO.md).

Hypha's roadmap

rhizome

The first milestone in eight phases, with its decisions and what it leaves out (ROADMAP.md).