Journal

The journal is jinflow’s developer log. Each post is a retrospective written from the commit history (and sometimes the pack’s Subject Matter) but with opinions. It is closer to field notes than to a changelog.

The journal is in three voices:

• Engine — weekly + monthly. One post per ISO week tracing what shipped in the platform itself, plus a monthly retrospective that pulls threads across weeks.
• nuMetrix — Lessons. Evergreen, content-focused. Each Lesson starts from a Wisdom in the pack and tells the story of what we learned about hospital material flow and how it changed the analysis.
• hrcentral — Genesis. Time-stamped, forward-looking. Documents the first weeks of the pack coming alive — written because the pack is too young to retrospect on. Closes when the pack accumulates enough Wisdom to begin Lessons.

The journal is published as written, with the project’s voice intact. Some weeks are dense and noisy; some are quiet and substantive. Either way, the goal is the same: leave a trail anyone could read in a year and understand why the architecture is the shape it is now.

Why this exists

The Release Notes tell you what changed. The journal tells you why it mattered, what got walked back, what surprised us, which moves looked small at the time but turned out to be load-bearing. Most projects have changelogs. Almost nobody has a serial retrospective. We think the second one ages better.

Months

• February 2026 — From bootstrap to pyramid
• March 2026 — The month the architecture grew language for itself
• April 2026 — The month of the Senses
• May 2026 — Twenty-four senses, the Atelier shipped, the pipeline got its voice
• June 2026 — The Stage, the Ledger, the sentence
• July 2026 — The month the system drew its boundaries

Weeks

Week	Title
W07	Origins
W08	The first vocabulary
W09	The roof goes on
W10	The pack era begins
W11	Shippable
W12	The Second User
W13	The Config Engine, and the cleanup behind it
W14	The Signal paradigm
W15	Sense 14 closeout, identity, P2P2P
W16	The DuckDB migration and the monolith drain begins
W17	Search grammar v3, Sense 20, the extraction discipline
W18	Foundations week
W19	hrcentral lands, the Lens arrives, the funnel narrows
W20	The Explorer learns to write back
W21	Three threads cross the working line
W22	The pipeline settles into shape
W23	What signs and what remembers
W24	The picture arrives
W25	The worktrees agree
W26	The diamond, said in one sentence
W27	The identity source moves to Clerk
W28	Truth: the system describes itself
W29	Selection: the system learns to be pointed at
W30	The house: a front of house, and a foundation
W31	The instrument, and the ground
W32	The store: travels light, and learns custody

Milestones

The curated read — the weeks where something foundational landed or shifted. The weekly table above is the chronicle in order; this list is the same corpus organised by what mattered. (See Sense 45: The Loom for why both views coexist.)

• W11 — Shippable. The first release the team could put in front of a customer. Before this, the engine ran; after this, it shipped.
• W14 — The Signal paradigm. The full Probe → Signal vocabulary rename. Every layer learned the new word at once.
• W17 — Sense 20, extraction discipline. The Seam landed (pack ↔ tenant relationship) and the extractor contract (pipeline.yml, SHA-256, append-only journal) closed the trust boundary.
• W19 — hrcentral lands. Second pack era begins. The engine became multi-product.
• W20 — Atelier + Bell. The Explorer learned to write back (Atelier authoring) and to raise its hand (Bell notifications). Bidirectional in the same week.
• W21 — Identity / Simulation / Types. Three Sense arcs — 25, 19, 14.2 — each crossed from sketch to working in the same seven days.
• W22 — The pipeline settles into shape. Six passes on the Sense 42 diagram took it from “graph with filters” to a working visual language. Three new Senses (45 Loom, 46 Roster, 47 Log). Sense 17 The House folded in.

House style

• Lede that names the week’s stakes in one sentence.
• Themed sections, not chronology. Threads, not transcripts.
• Direct quotes from commit bodies where the original voice beats paraphrase.
• Commit hashes inline so anyone can jump from prose into code.
• Numbers at the end — releases, commits, what’s countable.
• Forward hook — what the week made possible.

Reading order is up to you. The arc reads cleanly start-to-finish; individual weeks stand alone.