Metadata, facts and authoritative storage

Application PostgreSQL is authoritative for application metadata, facts, revisions, grants, durable work and receipts. The fixed server validates operations and controls publication. Derived projections are maintained in generations. A repair can rebuild a projection from its authoritative history and activate the repaired generation through its publication controls.

Read a consistent, typed view

• A coordinate combines member IDs across the applicable dimensions. Exact numeric values are represented as decimal strings. Present numeric zero, present empty text and absence are distinct states to preserve through transfers.
• facts.cube.scan reads bounded cube cells. For supporting detail, it can return the derived numeric cell total. facts.export.page exposes the underlying LineDetailLiteral representation when you need to inspect or transfer the detail lines.
• For another scan page, use the opaque continuation with the optional page limit. The cursor carries the original selection and snapshot. A later write therefore does not move the in-progress scan to a new revision.
• After a write, read back the affected coordinates and confirm the publication revision using the operation receipt or provenance. See First bounded read for the tested pagination contract.

Aggregation boundary

The packaged database initialization checks for the pinned pg_duckdb extension profile. The default exact cube aggregate route is postgres_exact_sql. A candidate acceleration route has a separate qualification boundary that checks exact equivalence, isolation and measured performance before selection.