Week 09 / 2026 — The roof goes on

23 February – 1 March 2026 · 96 commits

This is the week jinflow stopped being a detector and started being an explainer. On Tuesday, the Diagnosis layer landed — the actual top of the analytics pyramid that the project had been building toward for months. By Thursday, the tenant landing page had been rewritten around hypotheses instead of probes. And by Sunday, two of the longest-running questions in the design — how do experts contribute knowledge? and who is allowed to do what? — had concept papers committed.

It was not a week for shy moves.

The pyramid gets its capstone

On Feb 24, a2010044 shipped the Diagnosis layer. Eight starter rules, a validator (diagnosischeck.py), a compiler (diagnosiscompile.py), a contract, platform views, an Explorer detail section in three languages. The pattern was lifted wholesale from hypotheses — same YAML shape, same registry SQL emission, same dbt model layout. Probes detect, hypotheses interpret, diagnoses explain.

What’s striking, in retrospect, is how modest the commit message is. “Layer 4 of the analytics pyramid.” No fanfare. But this is the change that turns the product from “here are 18 things that look wrong” into “here is why, with confidence, in CFO language.” The diagnostic vocabulary — process_failure, system_failure, data_quality, behavioral, structural, external — would survive the entire Sense 14 rename eight weeks later without revision.

The same afternoon, 0ff36502 committed strategic_directions.md — “five paths evaluated, Diagnosis + Temporal chosen.” The roadmap document arrived after the implementation, which is exactly the right order: ship the thing, then explain the choice.

The overview gets rewritten

On Thursday, b1e9aef3 replaced the probe-centric overview with a hypothesis-centric executive summary. Probes moved to /probes; the front door now opened on verdicts and recommendations. This is a tiny commit by line count and an enormous commit by intent — the product’s primary unit of communication shifted from technical findings to business questions. Anyone who’d been demoing nuMetrix before this week and after had two different products to show.

Risk tier got added the same day (26b966fe) — tiered financial exposure surfacing in reports and Explorer. And qty_at_risk joined the findings contract (518891b0), recognising that the money-at-risk story alone wasn’t enough; sometimes the answer is units, not francs.

A week of concept papers

Three big concept docs landed this week without code attached — papers that would become implementation only weeks later:

• SMEbits (5b6cefc8) — atomic, attributed expert knowledge. Four executable levels (annotation, check, evidence, prescription). The doc gives them as Bronze/Silver/Gold-spanning facts. This would become the Subject Matter system after the 2026-04-13 rename, but the architecture was set here.
• Authorization & journal (2b6a185a) — capability RBAC + hash-chained audit. 13 capabilities, custom roles, S1-style tamper resistance, nDSG + ISO 27001 mapping. This is the seed of the Identity & Passes paper that lands six weeks out.
• Cloud v2.0 (fe0be0c7) — processing/exploration separation. Sense 16 (P2P2P) and the Funnel (Sense 27) are this line of thinking, taken to its conclusions.

The pattern is consistent: design before commitment, in the repo, dated, attributed. The Senses sequence doesn’t yet exist by that name, but the practice is here in spring of 2026.

Authorship, finally

Two changes on Feb 25 dragged probe authorship out of the YAML-and-grep era:

• 59834687 added the probe playground and builder with a roundtrip text layer. You could finally see what a probe did without rebuilding the world.
• 67a83902 added the interactive pipeline graph — a generator script plus an Explorer panel where you could click a node and see its source. Three commits later it gained slide-over source code inspection (b95b4b51).

And 5496a49b added the Jump Bar — Cmd-K command palette across the whole Explorer. Small change, huge daily payoff. Within 48 hours it grew dynamic entity search (04a8013b) and tenant switching (9b44593a).

The desktop app stops being painful

The Tauri build pipeline got hammered into shape across Feb 26-27. Cross-platform builds via GitHub Actions (3965f04f), dynamic port allocation for the Node sidecar (67d505b8), in-place DB use instead of copying to ~/.numetrix (67bf03ea), an Open Database menu (f9f1bfe1). The fix that ended one specific category of pain: 9b482686 — “file dialog deadlock — use rfd before Tauri event loop.” That’s the kind of commit message you only write after a long debugging afternoon.

Quiet but consequential

A few moves that didn’t make the highlight reel but should:

• Monthly → weekly time buckets (d08a683e). All 18 probe YAMLs flipped from bucket: month to bucket: week. The Explorer’s Week granularity tab became real for every hypothesis trend chart. This is what people remember when they say “the charts got better.”
• Entity registry replacing hardcoded maps (3bb13793). The Explorer stopped knowing which entities exist; the registry stopped being an artifact and started being the source of truth.
• data_source + is_backfilled lineage columns (63c1f6bb). Provenance starts being a first-class column instead of a comment.
• Convention-driven auto-filters (c466cc65) on dimension list pages. Less Explorer code, more declaration. This is the Canvas philosophy three months before the Canvas paper.

Numbers

• 96 commits, 7 days
• 4 new analytics-pyramid concept papers (Diagnosis impl, SMEbits, Authz/Journal, Cloud v2)
• 8 diagnosis rules; 18 probes flipped to weekly buckets
• 7 docs/ category folders (the great docs reorg, 84ab2691)
• 70 svelte-check warnings cleared to zero (fb6bf8fa)
• 2 presentations born and translated: Three Compilers, Beyond the Numbers

What this week made possible

By Sunday night, nuMetrix had the shape it would carry through the next eleven weeks: a four-layer pyramid with explanations on top, a hypothesis-shaped front door, command-palette navigation, in-Explorer pipeline introspection, and three concept papers describing where it was going. The 0.46-and-up release line that would dominate April was already implicit in what shipped here. The Sense vocabulary hadn’t been invented yet, but Senses 13 (Canvas), 14 (Signal), 15 (Observation), and 22 (Legend) all owe their seed ideas to this week’s commits.

Not bad for 168 hours.