May 2026 — Twenty-four senses, the Atelier shipped, the pipeline got its voice

1 May – 31 May 2026 · 1,003 commits · 0.46.x → 0.51.14

If April was the month jinflow learned to think out loud, May was the month the system started naming the layers it stands on. Twenty-four new design papers landed in docs/design/ — Senses 23 through 47, with most either shipped, scaffolded, or settled by month’s end. The pattern from April held: name what’s load-bearing before building it. The shift was in altitude. April’s senses were about analytical concepts (Signal, Canvas, Ledger). May’s senses were about the system’s own infrastructure — the seams, the cascade, the wire, the inlet, the breeze, the roster, the log, the loom. The architecture stopped naming what the engine does and started naming what the engine is.

A thousand and three commits. Bigger than March, bigger than April, and dense with structural moves: the Atelier turned the browser into an authoring surface, the Bell gave the system a voice, hrcentral landed as the second pack, the pipeline got its working visual language across six passes, the Cascade started cascading, and the AI co-pilot became something with memory and taste.

The Senses cascade — round two

If you list the new design papers in order of commit date, the cadence is dizzying:

Sense	Name	Date
23	The Engine’s Seam	May 3
24	The Steward	May 3
27	The Funnel	May 4
28	The Direct Line	May 4
29	The Atelier	May 6
30	The Wire	May 8
31	The Inlet	May 11
25	The Pass (settled form)	May 13
32	The Chores	May 12
33	The Bell	May 13
34	The Breeze	May 13
35	The Drift	May 14
36	The Lineage	May 15
37	The Snapshot	May 16
38	The Scribe	May 17
39	The Governance	May 20
40	The Metamodel	May 20
41	The Relevance	May 21
42	The Pipes	May 22
43	The Cascade	May 24
44	The Forge	May 24
45	The Loom	May 26
46	The Roster	May 28
47	The Log	May 29

Twenty-four senses in thirty-one days. Plus Sense 17 (The House) retired into Sense 42, Sense 14.2 reshaped through four sub-phases, and Sense 19 (The Simulation) shipped Phases 1–5 end-to-end in W21. The numbering stopped being a curiosity and became navigational infrastructure — Sense 25 The Pass, Sense 33 The Bell, Sense 42 The Pipes are how the architecture refers to itself now, the way s3:// and git push once stopped needing footnotes.

The Atelier shipped (W20)

The decisive move of the month was structural, not vocabulary. Sense 29 — The Atelier turned the Explorer from a reading instrument into a place where the analytical stack gets authored. Subject Matter forms with live validation (054eb969), every save as a git commit (e923f5ec), signal editors with line-level diff, Observation and Contributing Factor authoring surfaces (028b33d7, 8eb93a5a) — the browser became bidirectional. The Atelier didn’t replace the CLI; it gave the analyst a second hand.

By W22, every authoring surface had an UnsavedChangesGuard so sidebar clicks didn’t eat in-progress edits (a5923878, 9a2bbc24). The principal layer landed clickable PrincipalLinks everywhere (36189811). Notes started showing co-authors as “by <author> (with Claude)” (690df932). The Atelier became the place craft happens.

The Bell, then Pulse (W20 → W22)

The other half of the Atelier week was Sense 33 — The Bell: the system’s notification primitive (05b52ca1). The pipeline’s thousand silent noticings turned into something a person actually hears — an Inbox, a header bell, per-page banners, a CLI, durable across the AFS↔KLS round-trip. Authoring on one side, noticing on the other; the system stopped being a mirror and became a workbench.

Two weeks later, the same instinct landed as Sense 21 (The Heartbeat / Pulse) — the system-data arm rendered at /system/pulse (9d7ed784), then interactive with auto-refresh (e42847d3). Heartbeat had been a Sense for weeks; Pulse made it a visible surface. The Bell rings; the Pulse beats; the Atelier writes; the Explorer reads. Four shapes, one engine.

hrcentral lands (W19)

The product became multi-pack. hrcentral — HR analytics for academic institutions, people as the atomic unit — launched with VAI (Val d’Oria Academic Institutions) as the synthetic reference tenant (the W19 weekly tells the full story). The Sense 13.1 grammar instantiated against a new entity type (people instead of materials) with zero Svelte changes — the rooms had been entity-agnostic for weeks and now we had proof. The Joiners Lab and Cohorts pivot landed as the workforce-pulse and hiring-pulse surfaces. Federated-ID resolution across SAP SuccessFactors, SIS, and ZORA-style publication repos closed the loop on cross-source identity.

The engine stopped being a one-pack platform. After May, jinflow was a product that hosts packs the way Postgres hosts databases.

The pipeline gets its voice (W22)

Sense 42 — The Pipes closed in on its working shape across six visible passes in the last week of the month. The diagram went from “graph with filters” to a diamond-radial layout with collapsible eight-area sidebar (8c66f4f6), area clouds behind the node groups (b9c38575), dynamic centroid sizing (4fe9b158), zoom-aware edges (5763713c). Underneath the polish, PipelineView became a transportable artifact (a794a526) — a curated pipeline view is shareable now, the same way a Lens is. The pipeline also picked up per-node hide/isolate (fbcfa125) and note-embedded diagrams (fb96f30e) so a notebook entry can carry a focused subgraph.

By end of month, Sense 17 (The House) — the 3D walk-through that had been the early pipeline-as-experience — folded into Sense 42 (344316eb). The House was always one realisation of the pipeline narrative; Sense 42 carries the concept at the right altitude.

The Simulation shipped, end to end (W21)

Sense 19 — The Simulation went from sketch to five working phases in one week. Suggestion and Intervention became first-class YAML instruments (461fedcc); jin scenario create cuts an AFS branch and applies interventions to a temp tree (9b21c6ff); jin scenario build runs the standard pipeline against that branch and emits a sibling KLS marked with scenario metadata (941e05db); the Compare loupe gained a scenario mode (8cb7c76a); and Verdict detail pages now surface Suggestions tied to the verdict, with the Scenario Builder one click away (878b1ef9).

A reader who sees a confirmed thesis can now ask “what if?” without leaving the verdict page. Scenarios stopped being a sketch and became an analytical move.

Identity & Passes — Clerk lands (W21–W22)

For months the cloud refused to refresh: the owner ships a build, the deployed Explorer 403s on the new KLS. Sense 25 Phase 3a fixed it with a Deploy Pass — a per-instance owner token presented on refresh (25d45f25) — and Phase 3b.1 brought the embedded Clerk dial-tone to /admin after a day of wrestling SSR sharp edges (abb3e0f6). Phase C in W22 made jin invite --web send real Clerk invitations (d61844b5).

Then Sense 46 — The Roster named the authority flow itself (eefc8272). Clerk is the writer of identity; the AFS is the readable materialisation. Six steps shipped the same week: tenant-keyed map shape (360d0bd9), jin sync-principals (7d42d8f1), principals as A-tier orphan-branch artifact (ac81c27a), hooks.server.ts reading identity from publicMetadata (91a36a49), retire email-bind fallback (5142f408). The engine’s identity story has a real authoring root now.

Typed Signals — currency arrives (W21–W22)

Sense 14.2 crossed from “renders” to “enforces” then to “converts” in three weeks. Phase 1 (typed out_* columns in the Explorer) and Phase 2 (window: driving SQL WHERE; severity_from; type-checked thesis evidence) closed in W21. Then four sub-phases of currency machinery in W22: the cross-currency safety net for perspectives (cadf9cca); conversion infrastructure (cde45536); perspective compiler integration (174ff89a); not_null tests on converted columns (c9526103).

Multi-currency stopped being a sketch. Signals now know their units.

The Cascade cascades, the platform retires (W22)

Sense 43 — The Cascade moved from concept paper to working machinery in one week. Phase 1 marked shipped (a5a86a95), Phase 2 partial — currency.gap_policy cascade-driven (8bb83a07) — Phase 3.a — L4 display overrides via URL params (8ffd8c64), and the actual cascade fix — engine ⊕ pack ⊕ tenant at bake time (bec3074d). Layered authority stopped being aspirational.

Adjacent to the cascade work, the platform layer was retired (5d08fb38) — “single-tenant KLS is the future.” One fewer thing for the cascade to cascade through.

The Loom — naming the navigation pattern

Late month, Sense 45 — The Loom named the two-axis pattern that had been hiding in the senses index, the journal, and the field manual (83a5bf41). A corpus has a chronicle (the warp — temporal/numerical sequence) and a curation (the weft — editorial grouping). The reader stands at one crossing of the two. Sidebar walks the curation; footer walks the chronicle; index shows both. The same shape applies to release notes, the Field Manual, Subject Matter — wherever a corpus has both meaningful time and meaningful grouping.

Two days later, Sense 46 (The Roster) named the Clerk/AFS authority pattern, and the day after that Sense 47 (The Log) named the system’s write-once memory — the substrate the Bell, the Pulse, and the build logbook had all been carrying ad-hoc. By month’s end, the engine’s own infrastructure had vocabulary the way analytical work had had it since April.

Evolve v2 — the AI co-pilot, properly (W22)

The big invisible arc was evolve v2. The first three phases landed end-to-end, taking the AI co-pilot from “REPL that runs jin commands” to something with memory, taste, and a voice. Streaming responses, confirmation gates on side-effect tools, cost visibility, slash-command coverage, conversation persistence, a light-background theme, and instructions to the AI to use display labels (notes) not slugs (notebook) in prose. The roadmap papers that opened the week (159de497, 6bbdff5f) were the spec-before-code instinct landing in the AI surface itself.

After May, the co-pilot remembers yesterday’s conversation and admits when it ran out of credit.

The shape of the month

A thousand and three commits. The prefix histogram tells a building story: 355 feat: against 219 fix:, with 201 docs: carrying the conceptual scaffolding for twenty-four new Senses, the Sense 14.2 / 25 / 43 design rewrites, the Atelier and Bell papers, the evolve v2 roadmap, and the Loom / Roster / Log triple. Twenty-five releases — 0.50.10 through 0.51.14 — shipped on a near-daily cadence.

April was about analytical concepts; May was about the system’s own scaffolding. The Senses grew vocabulary for the engine’s own seams (Sense 23), its operating instincts (Sense 24, 32), its directional connections (30, 31, 34), its narrative surfaces (18, 36, 37, 47), its authority flows (25, 38, 46), its governance posture (39, 40, 41), and its core conviction about how navigation should work (45 The Loom). The names came first; the implementations followed; the implementations propagated into ship-ready surfaces — Atelier, Bell, Pulse, Pipeline.

By month’s end the engine could author its own knowledge (Atelier), notify when it noticed (Bell), pulse its operating heartbeat (Pulse), narrate its analytical pipeline (Sense 42), simulate what-if scenarios (Sense 19), enforce signal units (Sense 14.2), cascade layered authority (Sense 43), host two packs (numetrix + hrcentral), bind identity through Clerk (Sense 25 + 46), remember its own write-once events (Sense 47), and reflect on the two-axis pattern by which all of this is read (Sense 45).

After May 2026, the system has vocabulary for itself.