Recordation
What PacSpace records, what stays private, and how both sides check the same proof.
Recordation means recording usage when it happens so the invoice can be checked later.
Written by one side. Visible to both. Owned by neither.
What Gets Recorded
You emit a delta when usage happens. Usage can be anything you meter: model tokens, GPU-hours, agent-to-agent transactions, API calls. PacSpace records the event, creates proof fields, and makes those proof fields checkable.
Business data stays private. Proofs can be checked.
What Both Sides See
Both sides can see the same proof for the same record. That does not mean both sides see the same private metadata.
The proof answers three questions about any record:
Is this exactly what was committed? When was it committed? Has it changed since?
That is the whole job. Everything a checker does reduces to those three, whatever the unit: model tokens, GPU-hours, agent-to-agent transactions, API calls. Applied to an invoice, they add up to the claim that matters commercially: the usage was recorded before the bill that charges for it, and neither side can revise the record after the fact.
What PacSpace Does Not Do
PacSpace does not replace your meter, billing system, payment processor, or contract. PacSpace records usage and makes the proof checkable.
The Operating Rhythm
What recordation looks like in a working month, with who does what:
- Wire it once. Engineering adds one call where your metering closes a window: emit the customer's usage as a delta. See the Quick Start.
- The flush runs on its own. On the cadence you set, each customer's usage commits to their record. Nobody watches it on a normal day.
- Anyone can check mid-period. Derive shows the running balance at any time, and a Shared Record link lets the customer's team watch the month build instead of meeting the total on the invoice.
- Close locks the period. Before invoices go out, checkpoint the window. Invoice Readiness shows which customers are ready and which need action. The invoice goes out carrying its proof root and verification link.
- Questions start from the record. When a number is challenged, both sides open the same record and Compare their views. The conversation starts from a specific delta on a specific day, not a disputed total.
Who Touches It
- Engineering wires the flush once, then stops thinking about it.
- Billing ops watches readiness and locks periods at close.
- Finance closes from a record that no longer moves, and answers auditors from the same one.
- Support replies to usage questions with the record link instead of escalating to engineering.