One measure, one meaning.
A governed semantic layer defines the entities and metrics once — Revenue, Margin, DSO with a single definition each — so the number is the same in a report, a chart and an agent's answer. A natural-language question resolves through the governed metric, not a guessed query. Early access, pre-production.
design-record
Governed semantic / metrics layer
dbt Semantic Layer · Cube · LookML · AtScale
A metrics layer defined once over the real ERP ledger — so a metric resolves the same number in every report, chart and agent answer, with a natural-language path that goes through the governed metric, not a modelling layer bolted onto a nightly export. design-record
| ENTITY | KEY | RELATES TO |
|---|---|---|
| Customer | CardCode | Invoice · Payment |
| Product | ItemCode | Invoice line · Stock |
| Invoice | DocEntry | Customer · Product · GL |
| 3 entities | one definition each | EARLY ACCESS |
The nouns, defined once.
Early access · the nounsA customer, a product, an invoice — each defined once, with its keys and its relationships, so every question means the same customer and the same invoice. The entities are the shared vocabulary the whole platform reads from. design-record
| METRIC | DEFINITION | GRAIN |
|---|---|---|
| Revenue | Σ net line, posted, ex-VAT | invoice |
| Gross margin | Revenue − COGS | invoice line |
| DSO | AR ÷ revenue × days | customer |
| 3 metrics | one definition each | EARLY ACCESS |
One measure, many renderings.
Early access · the measuresA metric is defined once — its formula, its grain, its filters — and every surface renders from that one definition. Revenue posted ex-VAT is the same number in a report cell, a chart bar and a dashboard tile, because there is only one Revenue. design-record
resolve metric: Gross margin governed, not guessed
filter region = Nakuru · period = Jun from the entities
answer the defined metric auditable to source
Ask in words, get the governed number.
Early access · the questionA natural-language question is resolved through the governed metrics — not by guessing SQL over raw tables. “Margin in Nakuru last month” becomes the defined Gross-margin metric, filtered and grouped, so the agent's answer is the governed number a human would get, and it is auditable back to the definition. design-record
Everything on the Leysco Akili platform.
In this line| Governed Semantic Layer | Early access | This page — entities and metrics defined once. |
| MCP Tool Server & Agent Gateway | Early access | The governed AI surface over the metrics. |
| Leysco Licia (governed AI operator) | Early access | The operator that reads the governed metrics. |
| Master Data Resolver | Early access | Money-safe entity resolution behind the nouns. |
| Document Ingestion | Early access | Email / WhatsApp / PDF to a governed draft. |
| Immutable Multi-book Ledger | Early access | Append-only accounting core — designed native. |
One definition. One number. Every surface.
Signature · One measure, one meaningDefine the measure once, and it means the same thing in every report, chart and agent answer. The entities are defined once — a customer, a product, an invoice — and the metric is defined once over them: Revenue = Σ net line, posted, ex-VAT. One definition resolves to one governed number, and the report cell, the chart bar and the agent’s answer all render that same KES 4.82M — because there is only one Revenue. Early access, pre-production. design-record
reconciliation
The metrics are defined over the same production ledger the house posts 1.66M+ distribution invoices on — so “Revenue” is the real posted revenue, resolved once, not a figure re-keyed differently in each report.
The live ledger the metrics govern is the Leysco100 strength today. The governed semantic layer — entities, metrics and the natural-language-to-query path — is a Leysco Akili capability in early access, pre-production. We chip it as it is.
- define Revenue, Margin and DSO once and get the same number everywhere
- give every report, chart and agent one shared set of entities
- answer a question in words through the governed metric, not guessed SQL
- audit any number back to the one definition that produced it
Every report with its own Revenue formula, and three numbers in one meeting → one governed definition per metric, rendered many ways, one number