Words
jinflow has one engine vocabulary. Every pack brings its own domain vocabulary. The two are easily confused — “is Scenario part of hr/central? is ‘Signal’ something a workforce analyst should recognise as a domain term?” This page makes the boundary visible by listing every reserved engine word once, then showing how three different packs instantiate the same shape with completely different words.
The pattern to read: the engine words are the same in every pack. The pack words vary completely — different concepts, different language — but every pack instantiates the same two slots: Anchor (who & where) and Fact (what happened, when, by whom). The shape is shared; the words are the pack’s.
Reserved engine words
Section titled “Reserved engine words”These words are jinflow. Every pack uses them; no pack changes them. A pack that ships a “Signal” can’t redefine what a Signal is — the engine’s Signal contract is fixed. Same for everything below.
| Cluster | Reserved engine words |
|---|---|
| Substrate base | Anchor · Fact |
| Analytical chain (Sense 14: data → judgment) | Signal · Perspective · Thesis · Verdict · Finding |
| Expert knowledge | Subject Matter (Statement / Check) · Dossier |
| Observations (Sense 15: notice → ratification → explanation) | Observation (entity, with Explanation and Contributing Factor as facets) |
| Queryable view (Sense 27) | Lens |
| Decision chain (Sense 19: what-if) | Suggestion · Intervention · Scenario · Simulation |
| Identity (Sense 25) | Principal · Pass |
Definitions live in the Glossary; shipped-vs-in-design status lives on the Senses status page.
Pack words — three vocabularies, one shape
Section titled “Pack words — three vocabularies, one shape”Every pack supplies its own Anchors (who & where) and Facts (what happened, when, by whom). The engine doesn’t ship Persons or Cases or Parcels — packs do. But every pack has some. That’s the bridge: same shape, different words.
| Substrate role | numetrix (hospital material flow) | hr/central (workforce + academia) | Millésime (winemaking) |
|---|---|---|---|
| Anchor — who & where | Material · Case · CostCenter · Supplier · Department · SupplyOrg | Person · Cohort · OrgUnit · Infrastructure · Position | Parcel · Wine · Customer · Barrel |
| Fact — what happened, when | BillingEvent · MaterialMovement · CaseUsage · PriceObservation | Assignment · Booking · Contract · Qualification · Affiliation | Harvest · LabAnalysis · CellarOperation · BottleMovement · SalesOrder |
Notice what’s not in the pack columns: no Signal, no Thesis, no Verdict, no Lens. Those don’t change across packs — they’re engine. A hospital materials analyst recognises Material and BillingEvent as part of their domain; they recognise Signal and Thesis as the engine’s analytical language working on their domain.
How to read it
Section titled “How to read it”- Adding a new pack tomorrow → it adds a fourth column to the bottom table. The reserved engine words above don’t grow.
- “Is X engine or domain?” → if it appears in the reserved table, it’s the engine. If it could appear in any pack’s substrate row, it’s domain.
- JinDesk’s Domain tab shows the substrate half for the pack you’re in (just that pack’s column). This page shows what the Domain tab deliberately leaves out — the engine vocabulary — so the Domain tab can stay clean, pack-specific, with no engine overlay.
jinflow is a jazzisnow product