Columna
Governed meaning, not physical procedure, determines what may be served.
What Columna is
The Manifold declares the analytical world. Frame-QL expresses requests against it. Columna adjudicates what that declared world and current support entitle the system to serve.
Adjudication has four outcomes, and they are data, not prose. A request is served (the number), disclosed (the number and the assumptions riding with it), clarified (the question has more than one lawful reading — choose), or refused (the declared world does not define this, and here is why). One contract carries all four, and the same contract reaches a Python caller, an HTTP client, and an agent over MCP.
A separate question is where the declared meaning came from — and since
columna-server 0.11.0 that has its own shipped chain:
publication → compile → receipt → provision → governed admission
A governed publication compiles to an execution image; a lowering receipt binds the two by
content digest over the bytes as shipped; a provisioner places them; and the server admits the
result as governed rather than taking a runtime's word for it. The package ships one:
firstlight at version 1.0.0, admitted
governed with no conditions — the standing, shown →
The public release consumes governed authority. It does not provide the authoring and ratification machinery that produces it.
The Case
Whether it does that is a question about a real warehouse.
Cascadia Retail is a fictional chain with an ordinary warehouse and two famous bad numbers. The case works the whole arc — the company, the data, the design and its reasons, and the system live — and every number in it is recorded from the shipped package, never illustrated. The movement is here; the record is at /case.
-
The company, and the data they actually have
A 24-store chain, an ordinary warehouse, and two numbers everybody quotes and nobody trusts.
14 tables — and daily_revenue_summary carries 716 rows against the calendar's 731
-
The design, and the wall it puts up
One authored graph, two projections: the logical spec everyone reads, and the many-to-one physical map with its rejects kept.
15 map rows — and no physical identifier reaches the logical spec
-
The system live
The claims stand trial against the warehouse, then the questions get asked — including the ones with no lawful answer.
four asks, four moods — clarify · refuse · disclose · serve
Read the whole record — three chapters, every exhibit generated →
Earned exits
The vocabulary the Case just spent — collected, one question at a time.
-
What is the thing that holds the meaning?
The Manifold — the data model of substance, where the relational model was the data model of form. Or browse a real one.
-
How do you ask it something?
Frame-QL — the query language of the Manifold — the Frame is the query.
-
How does the answer appear at the machine boundary?
Read the wire — six ideas for reading what comes back — result and disclosure, always a pair.
-
Why is it built this way?
Building on the Data World — the architecture note — one engineered consequence of taking an independent Data World seriously.
None of this has to be taken on the page's word. Install it and run the demo — a clarify, a refuse and a disclose print on your own machine, as real wire JSON, in about two minutes.
These behaviours are not product personality. They follow from the rule that absence of contradiction is not permission. Analytical Governance →