Trackers

Every tracker in the portfolio, in one place. A tracker answers one of two questions: where is this work, or does this thing actually run. Same honesty rule as everywhere else — if something is not built, it says so.

On this site

Live

RootsDjinn — Pipeline Tracker v2

All 47 pipelines in the app, grouped by purpose, each with a plain-English health status: working, scaffolded, bounded, or not built.

Rendered from data/rootsdjinn-pipelines.json, emitted in the RootsDjinn repo from PIPELINE_INVENTORY.md + PIPELINE_TEST_REGISTRY.md. No status is invented, and this page holds no copy of the tracker.

In dev

TeaMark — Pipeline Tracker

All 60 pipelines, grouped A–H from capture through to the shared reference set, each with the same plain-English health status. 40 working, 17 good to a known limit, 2 uncharacterized, 1 built but not switched on, none failing.

Data is here at data/teamark-pipelines.json, same schema as RootsDjinn's, emitted in the TeaMark repo by npm run tracker. In dev means the data is live here and the page that renders it is not written yet - the RootsDjinn renderer hardcodes a genealogy-specific section, so serving both apps means making it generic first. The JSON is already readable by anything wanting pipeline health without a page.

In their own apps

Demo means it runs, but inside the app it describes rather than on this site - these are React components, so a static page cannot serve them. Listed here so the set is complete and nothing gets forgotten again.

Demo

RootsDjinn — Pipeline Tracker v1

One end-to-end run through the seven steps a researcher walks. v1 asks "how did this session go"; v2 asks "what can we rely on".

RootsDjinn/docs/pipeline-tracker/pipeline-tracker.html

Demo

Progress trackers × 8

Magpie · TopEx · TripSafe · Juniper · Master DevTools · Field Guide · Parallax Debater · ProveIt. Phase-by-phase build progress per app. Six were rescued out of chat artifacts into version control 2026-07-31; the rest were built against the code as it actually stood. Juniper’s was rebuilt at v6.4.0 after drifting 15 PRs behind; Magpie’s replaced one that described a different app entirely.

<repo>/docs/progress/*Tracker.jsx

Missing

Not built

CERTHerd · DiscoveryCharts

No tracker of either kind exists for these. DiscoveryCharts was never on this list and should have been. Master DevTools’ tracker references sections for some apps, but those were planned and never built — the reference is aspirational, not a lost file.

RootsDjinn and TeaMark have no progress tracker either, and are off this list on purpose: both carry a pipeline tracker instead, which answers the harder question.

The progress-tracker skill in this repo is the recipe.

How this stays honest. The tracker page holds no copy of the tracker — it renders from trackers/data/*.json, emitted by the builder in the app's own repo. Refresh it with node scripts/sync-tracker-data.mjs <source> <path-to-repo> (rootsdjinn or teamark — they live in different repos), which reports what actually changed (“P19: Failing → Works, to a point”) rather than silently overwriting; add --check to fail instead of update, so a stale copy can gate a deploy.

The same JSON is the machine-readable surface — an agent wanting pipeline health reads it instead of scraping this markup.

Both tracker pages are noindex: they carry internal file paths and test names. Nothing secret and no open vulnerabilities, but more implementation detail than the rest of this site shows, so that should be a decision rather than an accident.