Skip to content

investigate: fleet expansion census — CAIRN, hatch, hatch-personal, openclaw-personal, kaneo, and the rest of the touched-but-unmanaged set #2017

Closed

Description

@dezren39

LIST 2. Drew named CAIRN, hatch, hatch-personal, openclaw-personal 'and a few other repos' (earlier dictation also said 'Karen' — check kaneo) that the fleet touches but does not manage. Produce the census: every repo under dezren39 + developing-today that fleet tooling reads/writes, which management each currently gets (keeper, autocommit, sweeps, queues), and what 'adding to the fleet list (the 39) for now' concretely changes for each. Deliverable: a table + the exact list-change PR/issue set to execute the expansion.

Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.

Activity

  1. developing-today commented on Oct 29, 2026

    @developing-today
    Contributor
  2. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Parent epic: #2055 — fleet expansion & placement program (2026-10-28 directive).

  3. added
    priority/highImportant and time-sensitive
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026
  4. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3336 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026
  6. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), lane A shift
    • Session / ID: queue task 3336
    • Found via: queue claim
    • Task: Triage/investigation for the fleet expansion census — verify premise, produce the census (repos fleet tooling touches vs management each gets, and what joining "the 39" changes), record result on this issue and route follow-on work.
    • Expectation: m — done = census recorded on this issue (comment and/or linked doc) with the exact list-change issue/PR set routed as follow-on work.
    • Links: queue task 3336
  7. dezren39 commented on Oct 29, 2026

    @dezren39
    MemberAuthor

    Fleet expansion census — result (queue task 3336, triage of this issue)

    Premise: verified. The named repos exist, fleet tooling reads/writes them, and none of them is in the managed set. "Karen" check: there is no repo named karen/kären under either owner; developing-today/kaneo (fork, "Project Management for the agent era", last pushed 2026-10-25) is the match — the pm-stack in developing-today/code already integrates Kaneo boards (pm-stack/projector, pm-stack/aggregator).

    Key structural finding: there is no single canonical "fleet list (the 39)" to edit. Searched developing-today/code, dezren39/fleet, and hatch-personal on 2026-10-29: no file enumerates a 39-repo managed set. "The fleet" today is five separate mechanisms, each with its own list (or none):

    Mechanism Where its list lives Current coverage
    Issue sweeps + repo queues + producers + fleet monitor This goal's job set (cron/queue config) developing-today/code, developing-today/opencode, developing-today/openchamber, dezren39/nix — the managed four only
    Fleet umbrella repo dezren39/fleet .gitmodules 7 submodules: code, opencode, openchamber, nix, zettel, hatch, hatch-personal
    Laptop repo-keeper (hourly, code#1723) No list — discovery: every primary clone under laptop $HOME to depth 3 Everything cloned on the laptop, incl. all candidates below
    Laptop autocommit (every minute, code#1723) nixos/home/laptop-autocommit.nix repos map in developing-today/code ~/.openclaw (openclaw-personal), ~/hatch, ~/hatch-personal + daily untracked review
    Sandbox hatch-autocommit (every minute) scripts/hatch-autocommit in hatch-personal hatch-personal (full) + hatch (tracked files + whitelisted dirs only)

    Inventory scope checked 2026-10-29 via gh: developing-today = 55 repos; dezren39 = 300+ repos (mostly old forks — the census below is the subset fleet tooling actually touches, per this issue's scope).

    Census — touched but not in the managed four

    Repo Fleet touch (evidence) Keeper Autocommit Umbrella Sweeps/queues/labels
    dezren39/hatch-personal (private) Sandbox workspace itself; stewardship + memory live here ✅ discovery ✅ sandbox full + laptop ✅ ❌
    dezren39/hatch (public) Home-dir tools/docs/config; sandbox clone ~/git/hatch ✅ discovery ✅ restricted (tracked + safe dirs) + laptop ✅ ❌
    dezren39/openclaw-personal (private) OpenClaw state, moved out of code 2026-10-28 (repo description); pushed today ✅ discovery ✅ laptop (~/.openclaw) ❌ ❌
    developing-today/zettel Emanote zettelkasten; fleet submodule; sandbox clones ✅ discovery ❌ ✅ ❌
    dezren39/cairn (private) + dezren39/cairn-private Research journal/skills the fleet reads (code's research-workflow docs cite Cairn as source corpus) ✅ if cloned ❌ ❌ ❌
    developing-today/kaneo (fork) pm-stack reads/writes Kaneo boards; the "Karen" candidate ✅ if cloned ❌ ❌ ❌
    dezren39/fleet The umbrella itself — its .gitmodules is the closest thing to a fleet list ✅ discovery ❌ — (is the list) ❌
    developing-today/nix-cache Fleet infra: Nix binary cache (Workers+R2), sandbox clone present ✅ if cloned ❌ ❌ ❌
    dezren39/hatch-drawer + dezren39/hatch-personal-drawer Overflow shelves paired with hatch / hatch-personal (repo descriptions) ✅ if cloned ❌ ❌ ❌
    dezren39/opencode-muse (fork) Muse provider plugin for OpenCode (fleet session routing touches it) ✅ if cloned ❌ ❌ ❌
    developing-today/opencode-auto-continue Plugin used by fleet OpenCode sessions ✅ if cloned ❌ ❌ ❌
    developing-today/hardware-doc Fleet hardware documentation, pushed 2026-10-28 ✅ if cloned ❌ ❌ ❌
    dezren39/dezren39 Profile repo, actively pushed ✅ if cloned ❌ ❌ ❌
    dezren39/muse-esp32-screen (fork) Muse product repo, pushed 2026-10-24 ✅ if cloned ❌ ❌ ❌

    What "adding to the fleet list" concretely changes, per repo

    Because there is no one list, joining = one change per mechanism the repo should get:

    1. Umbrella (cheap, do first): add a submodule to dezren39/fleet — one PR there. This is the natural home for the canonical list; recommend the expansion also creates the missing canonical list file there so "the fleet list" stops being five implicit lists.
    2. Autocommit (laptop-primary personal repos only): add an entry to the repos map in nixos/home/laptop-autocommit.nix (developing-today/code) — one PR in code. Relevant for cairn / cairn-private / drawers if they live as laptop primaries.
    3. Keeper: nothing — discovery already covers every laptop primary. No change needed or possible.
    4. Sweeps/queues/labels (the expensive step): per-repo label taxonomy + backlog file + producer/queue coverage, following the Phase 3 per-repo pattern. Recommend this ONLY for repos that carry issues worth working (cairn, kaneo, zettel, nix-cache candidates); autocommit-only personal repos (hatch, hatch-personal, openclaw-personal, drawers) gain little from issue sweeps.
    5. Format auto-fix (LIST 1, investigate: fleet-wide format auto-fix workflow — push token, loop guard, concurrency #2014/design+PoC: format auto-fix workflow in one repo, ready to replicate fleet-wide #2015): each added repo joins the replication set once the PoC lands.

    Routed follow-on

    Filed as the execution issue (linked below): umbrella PR list + autocommit-map PR + the canonical-list creation, with a per-repo in/out checklist. The one genuinely-Drew decision — which candidates get full sweep/queue management vs umbrella+autocommit only — is posed as a checklist on that issue; it does not block the cheap steps.

    Gap noted: GitHub Projects state could not be checked (this token lacks read:project scope), so org-Project membership is the one management surface this census could not enumerate.

  8. 3 remaining items

  9. added
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  10. developing-today commented on Nov 3, 2026

    @developing-today
    Contributor

    agent-note:v1
    state: reviewed (coverage loop-back)
    Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 7259 (triage, queued, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
    Found via: coverage loop-back 2026-11-03

  11. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

  12. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  13. dezren39 commented on Nov 3, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triaged / already answered

    • Agent: queue worker repo-worker-code, OpenChamber scheduled lane bf419306-c4ef-470f-a553-beabf93239de
    • Queue task: 7259 (repo-health-code-pilot)
    • Verdict: the fleet-expansion census was already completed by task 3336 and is recorded in the census result on this issue. It lists the touched-but-unmanaged repos and current keeper/autocommit/umbrella/sweep coverage; its noted limitation is that GitHub Projects could not be enumerated.
    • Follow-up: #2230 remains OPEN for the canonical list, umbrella/autocommit changes, and per-repo management decision. The prior done note links it explicitly.
    • Disposition: closing this investigation as already answered; implementation work remains tracked by execute: fleet expansion per census #2017 — canonical list, umbrella + autocommit changes, per-repo management decision #2230. No new code or follow-up packet was needed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority/highImportant and time-sensitivesource/creatorFiled by the new-issue-creator jobtask/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions