Week 26 / 2026 — the diamond, said in one sentence

22 Jun – 28 Jun 2026 · 0.55.9 → 0.56.0

Three threads converged this week. The jinflow — V2 turned the five-name mental model into one sentence and three renamed feeders. jin package — V1 turned a tenant build into a double-clickable macOS bundle. And the public docs surface got a tidy: Forming senses retired from nav, a For developers group moved into the Explorer (where identity is real), claim purged from the vocabulary.

The week’s working theme: the model is the same; what we call its parts isn’t.

The jinflow — V2

The mental model didn’t change. The way we say it did.

Jinflow fosters Evolution by gaining Insights through Observations, Knowledge, and Data.

That sentence is the product, said once. It pairs with the surface tagline (“talk to your data, so it speaks to you”) — the analytical model and the marketing surface finally say the same thing.

The renames:

Was	Becomes	Why
Analysis	Data	Says what the layer is. Simpler.
Strategy	Observations	The layer doesn’t do strategy — it carries observations. Sense 15 already lives at this altitude.
Subject Matter / Expertise	Knowledge	Abstracts from “what experts have” to “what the system holds.” Matches the substrate.

Three structural moves landed alongside the renames:

• Observation IS the entity. Explanation and Contributing Factor are facets it carries, not peer sub-entities. Sense 15 gets a small reframe.
• Theses + verdicts are pack-shipped activatable patterns, not a separate tier. Verified across all 7 packs and 5 live tenants — every tenant inherits the pack’s set verbatim, no tenant authors its own. The “Strategy tier” was overstating what was actually happening.
• Provenance — 📦 pack-original, ✏️ pack-modified, 🆕 tenant-original — is a property carried horizontally by every artifact (theses, verdicts, perspectives, signals, dossiers), not a category one belongs to. Each artifact’s detail page will make its provenance state visible (UI implementation queued).

The new canon lives at the_jinflow.md (engine) and The jinflow (public). The ripple to the rest of the public surfaces — big-picture (EN/DE/FR), glossary, guide/findings — landed this week. The Explorer i18n + Diamond rendering + presentations deck queue.

Two structural concerns held for their own working sessions: Evolution anatomy (recommendations vs suggestions — synonyms or distinct? Where does Direction sit relative to scenarios and interventions?) and the Growing-the-Diamond elaboration page V2 (the long-form pedagogical doc that builds the diamond up stage by stage; the V1 was 778 lines, the V2 carries the new vocabulary + the parallelism note that the three feeders develop concurrently).

And one word retired from the vocabulary: claim. It was sneaking in everywhere — section headers, edge labels, descriptions. Out now, swept across the canonical the_jinflow doc and the big-picture trio.

Commits: 059733d4 (V2 draft) · 12921319 (V2 promoted) · e712bafd (claim purged).

jin package — V1

Sister 3rd shipped a distribution bundler in three phases this week. A tenant build becomes a per-customer macOS .dmg — double-click, drag-to-Applications, the bundled Node server starts, the system browser opens to the tenant’s data. Open / Anonymous auth (no sign-in, no setup) for V1.

• Phase 1A — e08087ab — distribution bundler V1 (the basic .dmg pipeline)
• Phase 1B — 0f98edfc — codesign + notarize
• Phase 1C — e21ad75b — packaging runbook

The CLI command is jin package -f bundle.yaml. Engine integration landed at the same time: package joined the clidocs SECTIONS (e4601a93) so the cheatsheet stays complete.

Sense 48 — The Stage tightens

The dev/prod plane separation shipped over the past two weeks gained one important refinement: jin ship keys on deploy_token, not on dev Clerk keys (31723d3c).

Ship is the one Sense 48 command that doesn’t authenticate a user via Clerk at all — it writes KLS to R2 using the deploy_token (Sense 25 Phase 3a). Conflating its env gate with “dev Clerk keys” would force operators to configure Clerk keys they never use, just to ship data. Since this week, jin ship’s “is this an operator?” signal is the presence of a deploy_token.

Public docs — the tidy

Three changes that don’t show in any single commit but reshape how the docs surface feels:

• Forming senses retired from public nav. The 13 Forming- vitality senses (proposed / sketched / recently arrived) are engineering-internal direction-of-travel. They were advertising an unstable roadmap on a public surface. URLs stay live; discoverable from inside the Explorer’s new “For developers” group (gated by afs:write) and via the unlisted /senses/forming/ index. (54ab06da)
• For developers in the Explorer sidebar. Replaces a “For developers” group I’d briefly added to the docs site — decision was: the public docs has no identity layer, the Explorer does (Sense 25). The developer-facing entries belong where they can be gated. (eb8ea86b)
• Source-path bullets scrubbed. Every public Sense’s “How this manifests” footer had a - **Source**: scripts/foo.py · explorer/src/… bullet pointing at concrete files. Useful for engineers, clutter for everyone else. Removed across 21 in_bloom + steady senses. (16a809d4)

What’s next

• The Growing-the-Diamond V2 rewrite — the long-form elaboration of the V2 model, 15 stages, the page where someone serious about understanding jinflow lands after the one-pager.
• The Evolution anatomy session — recommendations vs suggestions, where Direction sits.
• The Explorer’s Diamond rendering — the SVG/Mermaid the customer sees inside the app needs to carry the V2 names. This is where V2 stops being a doc rename and becomes the product’s own self-portrait.