Declared schema
The shared planning vocabulary — units, metrics, measurements — declared up front. Nothing is written against an undeclared aspect.
- — glossQL DECLARE ASPECT
- — Facts, queries and column measurements
- — Versioned with every change
Platform
Read-only middleware between your source systems and planning. Start with a single component; your existing stack stays.
01 — 7 items
The shared planning vocabulary — units, metrics, measurements — declared up front. Nothing is written against an undeclared aspect.
Each metric carries its SQL and every assumption with a confidence score, so planning knows exactly what a number means.
Suggested mappings and unit conversions go to your experts once. Approved rulings are reused across loads and markets.
Every new load is checked against approved rulings before it reaches planning, with deviations flagged by market.
Every statement is a commit with author and data snapshot. Scrub back to see what planning was told at any point.
Sits between source systems and your existing integration layer. Delivers in your current import format.
The open-source language GlossDB is built on.
02 — 3 items

Causal discovery
Separates consumption signals from distortions caused by batching, promotions and shortage ordering.

Counterfactual evaluation
Compares interventions on planning policies and parameters before anything changes in production.

Safety envelope
No experiment runs unless it stays inside the combined safety envelope.
03 — 3 items

Exception handover
Brings planning drift and operational exceptions into one focused daily view.

Governance levels
Agents may flag, propose, or act within agreed limits — set per decision type.

Outcome loop
Measures what happened after each approved action and feeds learning into the next cycle.
04 — 1 item

Diagnostic kit
A 1–2 week read-only assessment of order amplification across your tiers.