48 tools, one loop
Explore
1 tool with a web appsurfaces the fleet — a read-only view of the shared ledger, plus
myserver serve — localhost:8787Development harness
14 tools runs the autonomous cyclethe rule engine — evaluates an `Action` to allow / ask / deny,
(no purpose seam found)
curate a `TODO.md` — a repo's own (`mytodo repo`) or an org-wide
takes one picked issue (a `Candidate` from `my-orchestrator`,
(no purpose seam found)
reads a target repo's `dev-ledger/` entries since the last
Renders the fleet's status two ways — an org-wide front page
keeps `MyThingsLab/mythingslab.github.io` — the fleet's
reads every backlog across the fleet — open issues per repo, and
produce and maintain a priority-ordered, multi-item plan — "here's
keep the fleet's GitHub Project board (and any linked org-wide
reads the shared `Ledger` and each repo's `dev-ledger/`, and
<one line — what this tool does>
runs pytest with coverage, finds one uncovered unit, and opens a
Services
7 tools stays up, gets consumedbridges the harness to the user over Telegram: pushes ledger
surfaces the fleet — a read-only view of the shared ledger, plus
Casual development
16 tools make or learn somethingmaintains a unified catalog of a personal book/materials
given a local CSV file, deterministically profile it
explores a rough idea (a `my-idea`-labeled issue) by
given a local image file, deterministically extract dimensions,
given a task issue ("convert Markdown to HTML", "typeset a
given a natural-language animation concept, run one Engine call
a personal freeform note-capture tool — a note is filed as a
given a talk issue labeled `my-presentation` (topic, audience,
given a topic issue, discovers external sources **live** (web
given a URL and a question, fetch the page deterministically and
indexes a repo's files and ranks the ones most relevant to a
given a local CSV time-series file, compute an FFT power
given a content or design-change issue (label `my-site`) on a
given a document-drafting issue labeled `my-typster` (a report,
given a "field of study" issue, decomposes the field into a
Unshelved
11 tools⚠ Drift made visible, not silent: a new repo lands here until it is classified in shelves.toml.
given a reference-request issue (`doi:`, `arxiv:`, `isbn:`, or
given a design brief filed as an issue, produces a self-contained
the fleet's human-in-the-loop director. An end-of-day interactive
the learn-loop's **spaced-recall drilling** step. `build` makes
defines a term from a document corpus (PDFs, notes, slides) and
the learn-loop's **summative assessment** step. `grade` takes a
the fleet's front door for someone who has never opened a
the learn-loop's practice-and-assess step. `quiz` draws questions
bootstraps a brand-new `My[X]` tool repo from a proposal issue —
the learn-loop's **decompose** step. `decompose` reads a course
fleet orchestration/ops tooling — the pick-and-build dispatch