CCC documentation
Entry point for the Contribution Calculation Center documentation, routed by what you need to do.
The Contribution Calculation Center is KATO Group's in-house ETL, data warehouse and reporting platform. It pulls financial, order, product and traffic data from the rest of the stack into one database, classifies every transaction, applies configurable calculation rules, and reports contribution margin per transaction and per sales order.
This collection explains how it works and what its fields mean. It is written to be read one document at a time, so each page states what it is before it states any detail.
Pick your path
| You are | Start with |
|---|---|
| Reading a CCC screen and wondering what a number means | Using CCC |
| Changing CCC, as a person or as an agent | Developing CCC |
| Building a dashboard, an export or a query on CCC data | Consuming CCC |
The five questions people arrive with
"What does this number mean?" Contribution margin for the margin chain, the glossary for a term, and the in-app dictionary at /dictionary for a specific column.
"Where did it come from?" Sources for each upstream system and what it delivers. Objects for what CCC builds from them, including which period came from where.
"Why did it change?" Calculation rules for how margin is produced, and data freshness and history for when a figure is simply not refreshed yet.
"How do I configure this correctly?" Configure a calculation rule, then learn from existing rules.
"Where must I change the code, and how do I check it?" The change map and verification.
How this collection is organised
| Folder | Holds |
|---|---|
sources/ | An upstream system, as the data arrives. What it delivers, how often, and what it cannot give you |
objects/ | A concept CCC owns and publishes. What it means here, its tables, and which period came from which source |
concepts/ | Mechanics belonging to no single object: the pipeline, classification, rules, margin, identity, freshness |
guides/ | Task walkthroughs, start to finish |
pages/ | Only the screens that are themselves the subject. Most screens are explained by their object |
runbooks/ | Symptom, diagnosis, repair, and the check that confirms recovery |
reference/ | Coverage ledger, data model, field index, interface contracts |
development/ | Architecture, local setup, the change map, and how this collection is maintained |
Who can read this
Every role with application access can read this collection, including the Guest role that new users are provisioned into. That is a deliberate decision: the documentation contains no personal data, no credentials and no production output, and a reader who cannot reach it is a reader the collection does not serve.
It is not an authorisation mechanism. The audience label on a document is navigation, and a screen a document describes may still refuse you.
Screens with their own document
Most screens are explained by the object behind them. These seven are the subject themselves:
- The calculation rules screen and the impact screen
- The income statement
- The sales order detail view
- The daily dashboard
- The export screen and the jobs screen
- The fields dictionary
What is not here
Company-wide context lives in the KATO vault at <https://www.kato.tools/docs/view/ccc>: what the system is for, who uses it and where it sits in the stack. This collection covers how it works.
Repository rules live in AGENTS.md and .specify/memory/constitution.md, and they keep their authority. Nothing in this collection is a rule.
Related
- Documentation maintenance, the authoring contract
- Coverage, what is covered and what is not
- Type
index - Status
active - Updated
2026-09-14 - Created
2026-09-13