Domain Packs
Domain packs are optional. jinflow works without them — you can build a complete analytical pipeline from an empty tenant AFS. Packs are for teams that want to replicate a proven analytical framework across multiple clients.
A domain pack is a starter kit: entity models, contracts, source-system adapters, signals, theses, verdicts, SMEbits, and reports — all tailored to a specific industry. Run jinflow init --pack to copy the framework into a new tenant instance. From there, the tenant is independent.
jinflow currently ships with four domain packs, each proving the engine across a different industry with different data shapes, source systems, and analytical questions.
Millesime
Section titled “Millesime”Vineyard-to-bottle traceability for Valais winemaking.
Millesime tracks every parcel, harvest, fermentation, and bottling across multiple domaines. It detects yield anomalies, classification mismatches, and traceability gaps from vine to finished wine.
| Domain | Winemaking (Valais, Switzerland) |
| Source systems | Custom CSV exports from winery ERP |
| Tenants | domaine_zufferey, domaine_clavien, domaine_betrisey |
| Tagline | Every bottle has a story |
Entities (10)
Section titled “Entities (10)”| Entity | What it represents |
|---|---|
| Parcels | Vineyard plots with cépage, altitude, exposure |
| Harvests | Harvest events per parcel per year (yield, sugar, acidity) |
| Harvest Trends | Year-over-year metrics per parcel |
| Wines | Produced wines (cuvée, millésime, classification) |
| Cellar Operations | Fermentation, racking, sulfiting, blending steps |
| Lab Analyses | Chemical analysis (pH, alcohol, SO2, volatile acidity) |
| Barrels | Oak and steel vessels with capacity and age |
| Bottle Movements | Bottling, labeling, storage, dispatch events |
| Sales Orders | Customer orders with quantities and pricing |
| Customers | Restaurants, retailers, private buyers |
Analytical Focus
Section titled “Analytical Focus”- Yield anomalies — parcels producing significantly above or below historical norms
- Traceability gaps — wine without complete parcel-to-bottle chain
- Lab compliance — analyses outside AOC/DOC thresholds
- Cellar timing — operations happening outside expected windows
Signals: 12 | Theses: 3 | Verdicts: 3 | SMEbits: 5
Section titled “Signals: 12 | Theses: 3 | Verdicts: 3 | SMEbits: 5”Alptrack
Section titled “Alptrack”Lift-to-ledger reconciliation for ski resort operations.
Alptrack matches ticket sales, lift rides, snowmaking costs, and equipment rental across resorts. It detects revenue leakage from unpaid passages, equipment utilization gaps, and operational waste.
| Domain | Ski resort operations |
| Source systems | SkiData, Axess |
| Tenants | resort_alpine, resort_family, resort_glacier |
| Tagline | Every passage counts |
Entities (10)
Section titled “Entities (10)”| Entity | What it represents |
|---|---|
| Gate Passages | Turnstile events (lift, entry, parking) |
| Guests | Visitor profiles with pass type |
| Lifts | Chairlifts, gondolas, drag lifts with capacity |
| Passes | Ski passes (day, season, multi-day) with validity |
| Slopes | Pistes with difficulty, length, snowmaking coverage |
| Snowmaking Ops | Snow cannon operations (hours, water, energy) |
| Weather Obs | Temperature, precipitation, wind at station level |
| Revenue Events | Ticket sales, rental charges, F&B transactions |
| Rental Equipment | Skis, boots, helmets with condition and location |
| Rental Transactions | Equipment checkouts and returns |
Analytical Focus
Section titled “Analytical Focus”- Access revenue leakage — passages without valid passes (fare evasion, system errors)
- Equipment utilization — rental fleet sitting idle vs overbooked
- Snowmaking efficiency — energy and water cost per skiable hour produced
- Capacity planning — lift utilization vs queue times vs weather
Key Signals
Section titled “Key Signals”| Signal | Type | What it detects |
|---|---|---|
probe_passage_without_valid_pass | balance | Gate passages with no matching valid pass |
probe_lift_capacity_utilization | distribution_outlier | Lifts running far above or below capacity |
probe_revenue_reconciliation | balance | Ticket sales vs gate passage counts |
probe_snowmaking_efficiency | ratio | Energy cost per hour of produced snow |
probe_rental_return_overdue | hand_written | Equipment not returned within expected window |
Signals: 12 | Perspectives: 2 | Theses: 3 | Verdicts: 3 | SMEbits: 5 | Reports: 5
Section titled “Signals: 12 | Perspectives: 2 | Theses: 3 | Verdicts: 3 | SMEbits: 5 | Reports: 5”InterLogic
Section titled “InterLogic”Shipment-to-checkpoint accountability for global freight forwarding.
InterLogic tracks every checkpoint, customs declaration, and carrier handoff across 3 continents and 3 source systems. It detects visibility gaps, duty overpayments, and carrier SLA erosion.
| Domain | Global logistics and freight forwarding |
| Source systems | CargoWise, SAP TM, WMS Manhattan |
| Tenants | express_europe, global_freight, pacific_trade |
| Tagline | Every shipment tells a story |
Entities (12)
Section titled “Entities (12)”| Entity | What it represents |
|---|---|
| Shipments | Freight shipments with origin, destination, carrier, mode |
| Shipment Items | Line items with HS codes, quantities, values |
| Checkpoints | Tracking events (pickup, customs, transit, delivery) |
| Routes | Planned routes with legs and transit times |
| Route Legs | Individual legs (sea, air, road, rail) with carriers |
| Carriers | Freight carriers with SLA tiers and regions |
| Customers | Shippers, consignees, brokers |
| Containers | TEU/FEU/reefer containers with capacity |
| Customs Declarations | Import/export filings with duty rates |
| Warehouses | Distribution centers, port terminals, bonded stores |
| Inventory Snapshots | Warehouse stock levels at point-in-time |
| Incidents | Delays, damage, loss, customs holds |
Analytical Focus
Section titled “Analytical Focus”- Checkpoint visibility — shipments with gaps in the tracking chain
- Customs duty reconciliation — declared values vs actual duty paid
- HS classification consistency — same product classified differently across declarations
- Carrier SLA compliance — actual transit times vs contracted SLAs
Key Signals
Section titled “Key Signals”| Signal | Type | What it detects |
|---|---|---|
probe_checkpoint_gap | temporal_sequence | Missing checkpoints in the journey chain |
probe_customs_duty_reconciliation | balance | Duty paid vs duty expected from declared values |
probe_hs_classification_mismatch | duplicate | Same product with different HS codes |
probe_carrier_performance | ratio | Actual vs contracted transit times |
probe_container_utilization | distribution_outlier | Under/over-filled containers |
Key Theses
Section titled “Key Theses”| Thesis | Question |
|---|---|
hyp_customs_overpayment | Is inconsistent HS classification causing systematic duty overpayment? |
hyp_carrier_sla_erosion | Are carriers systematically underperforming their SLA commitments? |
hyp_shipment_visibility_gap | Are tracking blind spots causing operational and financial risk? |
Signals: 12 | Theses: 4 | Verdicts: 4 | SMEbits: 5 | BitBundles: 1 | Reports: 5
Section titled “Signals: 12 | Theses: 4 | Verdicts: 4 | SMEbits: 5 | BitBundles: 1 | Reports: 5”Lexflow
Section titled “Lexflow”Matter-to-invoice integrity for multilingual Swiss legal practices.
Lexflow tracks billable hours, expenses, disbursements, and compliance obligations across law firms operating in German, French, and Italian Switzerland. It detects billing anomalies, compliance gaps, and conflict-of-interest risks.
| Domain | Legal office operations |
| Source systems | Abacus Legal, Kleos, WinJur |
| Tenants | cabinet_geneve, kanzlei_bern, studio_lugano |
| Tagline | Every hour is accountable |
Entities (9)
Section titled “Entities (9)”| Entity | What it represents |
|---|---|
| Matters | Legal cases/mandates with practice area, status |
| Clients | Clients with KYC/AML status |
| Counterparties | Opposing parties in matters |
| Lawyer Profiles | Attorneys with hourly rates, specializations |
| Time Entries | Billable and non-billable time records |
| Invoices | Client invoices with line items |
| Payments | Payment receipts against invoices |
| Documents | Case documents with classification |
| Deadlines | Court and regulatory deadlines |
Analytical Focus
Section titled “Analytical Focus”- Billing integrity — time entries without invoices, invoices without matching time
- AML/KYC compliance — clients with incomplete know-your-customer documentation
- Conflict of interest — matters where the firm represents both sides
- Revenue concentration — over-dependence on a single client
- Deadline risk — approaching court deadlines without activity
Key Signals
Section titled “Key Signals”| Signal | Type | What it detects |
|---|---|---|
probe_aml_missing_kyc | mandatory_item | Clients with high-value invoices but incomplete KYC |
probe_client_revenue_concentration | distribution_outlier | Clients representing disproportionate revenue share |
probe_unbilled_time | balance | Time entries without corresponding invoice lines |
probe_deadline_at_risk | temporal_sequence | Deadlines approaching without recent activity |
probe_conflict_of_interest | duplicate | Matters where firm acts for both parties |
Signals: 15 | Verdicts: 4 | SMEbits: 5 | Reports: 3
Section titled “Signals: 15 | Verdicts: 4 | SMEbits: 5 | Reports: 3”Cross-Pack Comparison
Section titled “Cross-Pack Comparison”| Millesime | Alptrack | InterLogic | Lexflow | |
|---|---|---|---|---|
| Industry | Winemaking | Ski Resorts | Logistics | Legal |
| Entities | 10 | 10 | 12 | 9 |
| Source systems | 1 | 2 | 3 | 3 |
| Signals | 12 | 12 | 12 | 15 |
| Theses | 3 | 3 | 4 | — |
| Verdicts | 3 | 3 | 4 | 4 |
| SMEbits | 5 | 5 | 5 | 5 |
| Reports | — | 5 | 5 | 3 |
| Tenants | 3 | 3 | 3 | 3 |
Each pack proves a different aspect of the jinflow engine:
- Millesime proves agricultural traceability (parcel → bottle)
- Alptrack proves real-time operations (passage → revenue)
- InterLogic proves multi-system logistics (3 ERPs → 1 checkpoint chain)
- Lexflow proves compliance-first analytics (KYC, conflicts, deadlines)
Creating Your Own Pack
Section titled “Creating Your Own Pack”You don’t need a domain pack to use jinflow. But if you want to package your analytical framework for reuse:
- Build your instruments in a tenant AFS (signals, theses, verdicts, SMEbits)
- Validate that they work across at least 2 tenants
- Extract the AFS into a pack repository
- New tenants start from your pack:
jinflow init --pack mypack --tenant new_client
See Tutorial: Publishing a Domain Pack (coming soon) for the full walkthrough.
jinflow is a jazzisnow product