The Senses — Current Status

Companion to the The Senses slide deck. The per-Sense Doc column references the design papers in the engine repo (docs/design/sense_*.md); those are working documents, not part of this site.

The Senses — Current Status

Companion to the_senses.html. Each Sense earns its number by being lived first; this page tracks where each one stands today.

Status legend. — foundation (Senses 1–12): settled instincts, written into the bones; not actively edited. — concept : named and reasoned about, no implementation work yet. — proposed : design doc landed, awaiting implementation; details may still shift. — implementing : actively being built; partial in the codebase. — shipped : implementation complete; behaviour matches the design doc. — folded : the Sense was absorbed into another and no longer stands alone.

All dates below are the last_verified field of the source design doc — i.e. the latest moment the doc was confirmed to reflect reality. They are not the date the Sense first emerged.

Foundation (Senses 1–12)

These do not have individual design docs; they are baseline disciplines the rest of the system rests on. Captured collectively in the_senses.html under “Settled instincts, written into the bones.”

#	Name	Status
1	Layered Truth	foundation
2	Tenant Isolation	foundation
3	Declarative First	foundation
4	Contracts at Boundaries	foundation
5	No Silent Filtering	foundation
6	Rebuildable by Default	foundation
7	Make / Explore Split	foundation
8	Source-System Agnosticism	foundation
9	Quality is Queryable	foundation
10	Computed Aggregates	foundation
11	AI in the Studio, not the Pipeline	foundation
12	Form follows Data	foundation

Modern Senses (13–53)

Each of these has a design doc under docs/design/sense_*.md.

#	Name	Status	Verified	Doc	One-line
13	The Canvas	concept	2026-04-04	sense_13_the_canvas.md	Composable workbench — pages are panels declared in YAML, not hand-coded Svelte.
14	The Signal	shipped	2026-04-04	sense_14_the_signal.md	Signal / Perspective / Thesis / Verdict — typed observation with polarity, score, direction, impact.
14.2	Typed Signals	implementing	2026-07-09	sense_14_2_typed_signals.md	Five base types grounded in UCUM, ISO 4217/8601/80000. Phase 5 typed aggregates shipped 2026-07-09 across seven packs.
15	Observation, Validation, Explanation, Contributing Factor	shipped	2026-07-11	sense_15_observation_and_explanation.md	The strategic top of the system — signed claims, empirical proof, human theories with cited factors. Live in delta with quadrilingual observations.
16	P2P2P (Peer-to-Peer-to-People)	shipped	2026-05-04	sense_16_p2p2p.md	Your data, your machine, their browser — sovereignty as physical fact. Proxy chain shipped.
17	The House	folded	2026-06-07	sense_17_the_house.md	Guided 3D tour of the pipeline — narrative ambition folded into Sense 42 (Landscape); the 3D-engine cost was dropped.
18	The Ledger	implementing	2026-04-16	sense_18_the_ledger.md	Computational provenance as narrative — every headline traceable through bronze → silver → gold → signal → verdict.
19	The Simulation	shipped	2026-04-17	sense_19_the_simulation.md	Suggestion → Intervention → Scenario → Simulation — the leap of faith becomes a measured step. Phase 5 read-side shipped 2026-05-24.
19.1	Simulation Prerequisites	proposed	2026-05-05	sense_19_1_simulation_prerequisites.md	What needs to land before Sense 19 can be built.
19.2	The Incremental Scenario	proposed	2026-05-25	sense_19_2_the_incremental_scenario.md	Copy KLS + dbt state-aware build — scenario rebuilds proportional to the intervention’s reach, not always full pipeline.
20	The Seam	shipped	2026-04-24	sense_20_the_seam.md	The pack/tenant boundary, with five named concepts: scope, provenance, merge base, conflict taxonomy, promotion.
21	The Heartbeat	implementing	2026-04-27	sense_21_the_heartbeat.md	Six discrete beats — make, capture, publish, sync, pulse, reconcile — each with its own command, log, and UI.
22	The Legend	implementing	2026-04-27	sense_22_the_legend.md	Every label is a self-describing artifact: rule, threshold, description, action, icon, colour.
22 (impl)	Legend Implementation	proposed	2026-04-28	sense_22_legend_implementation.md	Phased build-out plan for The Legend.
23	The Engine’s Seam	proposed	2026-05-01	sense_23_the_engines_seam.md	Three actors at the boundary — pack, tenant, and engine — each with its own cadence.
24	The Steward	proposed	2026-05-03	sense_24_the_steward.md	The third native habitat — for the person who operates the estate.
25	The Pass	implementing	2026-06-14	sense_25_the_pass.md	Product-agnostic access model — Identity → Roles → Passes → Capabilities over one scope tree. Auth providers swap; the model doesn’t. Clerk dial-tone shipped; invitation flow live.
26	The Workshop	shipped	2026-05-04	sense_26_the_workshop.md	A pack ships its own design notes — browseable, searchable, translated. A clone of the pack is a workshop.
27	The Funnel	shipped	2026-05-04	sense_27_the_funnel.md	The cloud holds the picture, not the dataset. Aggregate at the source; never widen on the way out.
28	The Direct Line	proposed	2026-05-04	sense_28_the_direct_line.md	The cloud doesn’t even hold the picture — query results travel browser → laptop → browser.
29	The Atelier	implementing	2026-05-06	sense_29_the_atelier.md	Intelligent, git-aware, role-gated workshop for the AFS. Five layers of intelligencia, each optional.
30	The Wire	proposed	2026-05-08	sense_30_the_wire.md	The outward contract — typed, identified, reasoned, rate-aware. Same wire whether the consumer is another jinflow or anyone else; bonus when both speak jinflow: no semantic loss in transit.
31	The Inlet	shipped	2026-05-12	sense_31_the_inlet.md	The channel is the unit — six channel types (supplier, synthetic, web, manual, computed, fixture) replace four competing pipeline.yml keys. Where bytes come from is the channel’s business.
32	The Chores	shipped	2026-05-12	sense_32_the_chores.md	The human-cadenced pulse — complement to Sense 21 (Heartbeat). Registry of recurring upkeep at docs/operations/chores.md. Retired chores stay visible.
33	The Bell	shipped	2026-06-05	sense_33_the_bell.md	Where the noticing becomes a sound — a typed Notification substrate with severity-graded volume so five feeds ring the right person, not the same table nobody reads.
34	The Breeze	shipped	2026-05-14	sense_34_the_breeze.md	Lateral signalling between tabs of the same JinDesk instance. Completes the triptych with Wire (outward, 30) and Inlet (inward, 31). Announcement, not command — receivers decide.
35	The Drift	shipped	2026-05-14	sense_35_the_drift.md	Server → browser ambient system events. Per-tenant generation counter polled by the browser; on bump, an unobtrusive toast announces “data has moved.” Tap on the shoulder, not a pull on the sleeve.
36	The Lineage	implementing	2026-06-05	sense_36_the_lineage.md	A tenant remembers where it came from. The durable, anchored record of pack-init; the Seam (20) protects the boundary, the Lineage protects the relationship. Phase 1 shipped 2026-05-16.
37	The Snapshot	proposed	2026-06-05	sense_37_the_snapshot.md	A working KLS witnesses what is; a snapshot witnesses what was, as of when we said it was. Photograph, not livestream — immutable, refuses overwrite by design.
38	The Scribe	implementing	2026-06-05	sense_38_the_scribe.md	Who carries the author’s action past a credential boundary the user themselves cannot cross. Authoriser + Carrier — two names where there used to be one, so the audit trail no longer lies about whose hand pushed the bytes.
39	The Governance	proposed	2026-05-20	sense_39_the_governance.md	A rule is a sentence with a calendar. The bi-temporal discipline that lets jinflow answer retrospective, reproductive, and compliance questions honestly.
40	The Metamodel	proposed	2026-05-20	sense_40_the_metamodel.md	The engine describes the language used to describe worlds; the pack describes its world. Draws the line between engine-shaped and pack-shaped contracts so shared sentences stop drifting.
41	The Relevance	proposed	2026-06-05	sense_41_the_relevance.md	Severity says how loud, capability says who may act, Relevance answers who this is for — per-person filter computed at ring time so the right rings reach the right inbox.
42	The Landscape	implementing	2026-06-07	sense_42_the_landscape.md	Renamed from “The Pipes” 2026-06-07. The analyst’s vantage over the diamond — a garden on the slope, a river in the valley, paths between them. Absorbs Sense 17’s ambition.
43	The Cascade	implementing	2026-06-05	sense_43_the_cascade.md	Configuration as layered authority. Engine → pack → tenant → entity → explorer, resolved top-down, provenance baked into the KLS. One mechanism, two namespaces (analytical_defaults + display).
44	The Forge	proposed	2026-05-24	sense_44_the_forge.md	Eighteen universal subsystems every pack must answer for. The seventh pack shouldn’t have to discover them one missing piece at a time.
45	The Loom	proposed	2026-06-05	sense_45_the_loom.md	A corpus is read both as chronicle and as curation. Warp is time, weft is theme; the reader picks which axis runs vertical. Same loom on senses, releases, notebooks, Subject Matter.
46	The Roster	shipped	2026-06-05	sense_46_the_roster.md	Clerk authors, AFS materialises. Identity decisions happen where identity already lives; the AFS is a deterministic projection, not a competing truth. SIS overlay pattern shipped 2026-07-09 (browser admin invite/revoke).
47	The Log	implementing	2026-06-05	sense_47_the_log.md	The system’s write-once memory. Append-only, attributable, queryable, replayable. Without it, every Sense above is an event without a tape.
48	The Stage	proposed	2026-06-14	sense_48_the_stage.md	Dev/prod plane separation. Prod is the system; dev is a controlled affordance for developers. The env distinction flows through auth, app code, data, membership, and every CLI command.
49	The Branch	proposed	2026-07-02	sense_49_the_branch.md	A pack is a trunk; branches are opt-in modules carrying Anchors, Facts, source systems, Gold contract entries. A tenant grafts what it needs — same pack, different weight per tenant.
50	The Beacon	proposed	2026-07-08	sense_50_the_beacon.md	A showcase tenant declares itself in its own KLS; the cloud discovers it, routes to it, gates it, renders its welcome page — automatically. One command, not eleven declarations across four repos. Born of the delta.jinflow.io publishing incident.
51	The Skill	proposed	2026-07-09	sense_51_the_skill.md	Cross-domain analytical patterns. A Skill is a what many packs can answer; a pack is a how that answers many Skills. Names the layer above pack-specific instrumentation where analytical intent is portable.
52	The Cartography	proposed	2026-07-09	sense_52_the_cartography.md	Declarative geographic maps as first-class JinDesk artifacts — entities plotted at real-world lat/lon on a real base map, switchable layers, rich per-point content. Not “Map Salon”; this is the real map. V1 shipped alongside delta.
53	The Codex	shipped	2026-07-11	sense_53_the_codex.md	Industry-recognised standards live in the platform, not in packs or tenants. jinflow declares which standards it speaks; packs opt in by reference. Thirteen standards in the registry as of 2026-07-11, including UCUM, ISO 4217/8601/80000, JCGM 100:2008 (GUM), and jinflow_naming.

How to update this page

1. When a Sense moves from proposed → implementing → shipped, update the status: field in its design doc, then update the matching row here.
2. When a new Sense lands, add a row + a slide in the_senses.html + a closing-list entry.
3. When a Sense is retired or merged into another, leave the row and add a note in the One-line column (don’t delete history).

The Pattern, from the_senses.html:

A Sense earns its number by being lived first. Naming the Sense is what stops the loop — building the feature is easy after that. The hard part is the naming.