Teach the system once. Keep the meaning current everywhere.
Activity Schema and a shared operating record connect customer decisions, source evidence, definitions, work, review, and change history so the same meaning can support the next report, investigation, workflow, and AI task.
Bespoke models are why the second question costs as much as the first.
Without one
Every new question means a new join, a new model, new assumptions, and a new place for the definition to drift.
With one
The events are already in a shape that answers temporal questions. Most new questions are a configuration, not a project.
The compounding part
Definitions, decisions, and evidence accumulate against the same shape, so the system genuinely gets more useful.
02 / Why the data design matters
Why data design makes Poly so powerful.
Text-to-SQL can jump from a question to unfamiliar tables and produce an answer that looks plausible. Poly works through a constrained path of business objects your team can inspect.
Each step is named, contained, and human-understandable—so Poly can show its work, stop at uncertainty, and reuse logic that has already been approved.
-
01
Goal is explicit
AI
Starts with the business question
Poly identifies the output and the decision it needs to support. -
02
ReportsUse is visible
Reads logic people already review
The existing report shows which result, filters, and business interpretation matter. -
03
Metrics DimensionsMeaning is named
Resolves the governed concepts
Metrics name what is calculated. Dimensions name how the answer may be grouped or constrained. -
04
DatasetsScope is contained
Uses tables assembled for the job
Poly works from a bounded analytical dataset instead of roaming across the warehouse. -
05
ActivityBuilding block is reusable
Connects everything to a reusable business event
An Activity records what happened, to whom or what, when, under which dimensions, and according to which approved definition. -
06
Logic is reviewable
Source query
Builds each block with small, inspectable logic
A focused query translates source-specific records into the Activity instead of hiding meaning in one enormous generated query. -
07
Changes are traceable
Source table
Tracks the data underneath for changes
Schema, freshness, and source behavior are monitored so affected definitions and outputs can be found.
How work actually moves each week.
A task states what is being answered, for whom, and what would make it acceptable. Poly can create one when it cannot finish.
The backlog is reordered with you against the current business priority — not against a fixed statement of work.
What was decided and why goes into Knowledge, so the next piece of work inherits it instead of re-litigating it.
The grammar, in the product.
Three screens showing the shape and what gets reused from it.
A method, not a lock-in.
Business data, processing, transformations, and queries execute in your warehouse.
Every definition has your owner, your approval, and a review date. It is documented business logic, not a black box.
Bring a question you have asked three different ways.
If the same question keeps getting rebuilt, the grammar is the problem.
Book a working session