Diagram Index

All mermaid diagrams used across the documentation, collected in one place for reference and reuse.

Analytical Pyramid

The layered instrument stack from data ingestion to root cause explanation.

Used in: Instruments Guide

The River, the Garden, and the Interface

The River (temporal view — data in motion) and the Garden (structural view — the analytical framework arranged in place) meet at Entity + Contract: the seam where the River delivers into the Garden. Two views of the same jinflow landscape. See Sense 42 — The Landscape for the full model.

Used in: Big Picture · Design Principle 18

Instrument Relationships

The entity-relationship map of jinflow’s analytical instruments — how they connect, what they produce, and what they consume.

Used in: Big Picture, Instruments Guide

Build Pipeline

The phases of jinflow make from source data to knowledge store.

Used in: Make Guide

Data Flow

How data moves from the landing zone through the build pipeline to JinDesk.

Used in: Tenants Guide

Contract Dependency Chain

How the 7 contracts relate to each other.

Used in: Contracts Reference

Evidence Chain

A concrete example: signal finding to thesis status to verdict with root cause.

Used in: Tutorial: From Finding to Verdict

Core Loop

The make, explore, evolve cycle that drives all jinflow work.

Used in: Quick Start

Collaboration Flow

How domain packs, tenant AFS instances, and GitHub interact for team collaboration.

Used in: Collaboration Guide

Make — Input Phases Feed the Build Phases

make gathers its inputs on the way in (Phase 0 extract from the DLZ) and commits them to the AFS before the build phases read them. The build phases are deterministic: AFS in → KLS out.

Used in: Pipeline Overview, Make Guide, Operating Modes

Operating Modes — Decision Tree

Which of the five deployment topologies should I use?

Used in: Deploy Guide, Operating Modes