Operating Modes
Five topologies.
One product.
Input and build. AFS, KLS, OPS.
Where things live. Where make happens.
The Split
The pipeline has two phases.
- Input phases — Phase 0 extracts from the declared contract; Phase 0b syncs changed CSVs from the DLZ. They commit to git before anything reads. Has side effects.
- Build phases — validate, enrich, compile, dbt, bake. Read only from AFS. Write only to KLS. No OPS access. No external fetches. A pure function.
- The cut is the security boundary. Whoever controls make controls the analytical truth. Every build is reproducible from its AFS commit.
- Everything that goes into make is in git. Auditable. Reversible. Reproducible.
The Three Stores
AFS. KLS. OPS.
Each has its own role, its own access pattern.
AFS
The Analytical Framework.
A git repo. YAML instruments.
Everything a human authored.
Read + write by the input phases of make.
A git repo. YAML instruments.
Everything a human authored.
Read + write by the input phases of make.
KLS
The Knowledge Store.
A DuckDB file. Immutable after build.
Bronze → Silver → Gold → findings.
Written by make. Read by JinDesk.
A DuckDB file. Immutable after build.
Bronze → Silver → Gold → findings.
Written by make. Read by JinDesk.
OPS
The Operational Store.
A SQLite/WAL file. Mutable.
Notes, bookmarks, bell resolutions.
Outlives every KLS. Never rebuilt.
A SQLite/WAL file. Mutable.
Notes, bookmarks, bell resolutions.
Outlives every KLS. Never rebuilt.
The Pipeline
Make. Desk. Console.
Make
AFS in, KLS out.
Pure function.
No side effects.
Pure function.
No side effects.
→
Desk
Reveals the KLS.
Notes and bookmarks
land in the OPS.
Notes and bookmarks
land in the OPS.
→
Console
Drafts instruments.
Reads AFS + KLS.
Writes the AFS.
Reads AFS + KLS.
Writes the AFS.
Three verbs, three stores. No arrow leaves the OPS.
The loop closes by authoring — console drafts into the AFS, and the next make reads it.
jinflow
Five Modes
Same product. Different placement.
- 1. Local — everything on one machine. Developer's laptop. No auth. Simplest and most private.
- 2. Proxy (P2P2P) — KLS on the owner's machine. JinDesk in the cloud. One OPS in the cloud. Your data. Your machine. Their browser.
- 3. Cloud (R2) — KLS uploaded to Cloudflare R2. JinDesk + OPS in the cloud. GitHub OAuth. Always on.
- 4. Semi-Cloud — KLS stays local (via proxy). OPS in the cloud. For compliance: the KLS can't leave the site, the OPS can.
- 5. Make-as-a-Service — make runs in the cloud. Triggered by git push. No local machine needed. The endgame.
Which Mode?
Pick by data sensitivity and collaboration
Only you use it
Mode 1 — Local
Simplest. Everything on one machine.
Multi-viewer, sensitive data
Mode 2 — Proxy (P2P2P)
KLS stays local. Tunnel serves remote viewers. Ctrl+C unplugs.
Non-sensitive, always-on
Mode 3 — Cloud (R2)
Upload KLS. Standard cloud auth. 24/7 availability.
Compliance: data can't leave
Mode 4 — Semi-Cloud
KLS stays local via proxy. User activity (OPS) OK in cloud.
Automated CI/CD builds
Mode 5 — Make-as-a-Service
Cloud worker runs make (extract + sync + build). Git push triggers.
Mixed fleet
All five can coexist
JinDesk picker shows cloud tenants, proxy tenants, or both.
One OPS per Tenant
The operational record.
Never split. Never rebuilt.
Memory (long-term)
Notes, bookmarks,
bell resolutions, preferences.
Operational citizens. They stay
in the OPS — nothing publishes them.
Survives every rebuild.
bell resolutions, preferences.
Operational citizens. They stay
in the OPS — nothing publishes them.
Survives every rebuild.
Messenger (short-term)
Recents (navigation journal),
session state, scroll position.
Rotated, never published.
Ephemeral by design.
session state, scroll position.
Rotated, never published.
Ephemeral by design.
One Location
Local mode: developer's machine.
All cloud modes: in the cloud.
Restored from backup,
never regenerated.
No splits. No merge conflicts.
All cloud modes: in the cloud.
Restored from backup,
never regenerated.
No splits. No merge conflicts.
The Flow
One path. All five modes.
DLZ
source data
source data
→
make — gather
Phase 0 + 0b
Phase 0 + 0b
→
AFS
git
git
→
make
pure function
pure function
→
KLS
JinDesk reads
JinDesk reads
In Mode 1, this whole flow runs on the developer's laptop.
In Mode 5, it runs in the cloud on git push.
The code paths converge. Only the placement differs.
Operating Modes
One product.
Five topologies.
Start with Local for development.
Move to Proxy (P2P2P) for sensitive data.
Cloud (R2) when you want always-on.
Make-as-a-Service when you want CI/CD.
The code paths converge. The security boundary holds.
jinflow
jinflow.io