Shared Record Language

The Shared Record describes what PacSpace does precisely: PacSpace records a vendor attestation at the time it is made and makes that record independently checkable later.

The universal customer-facing word is recorded.

Required Labels#

Use these labels on customer-facing Shared Record pages, invoice copy, customer preview, exports intended for customers, and middleware templates:

• Recorded this period
• records this cycle
• {amount} {unit} recorded
• Recorded by {Vendor}
• Verified through {date}
• Proof available
• This record was written by {Vendor}. It can be independently checked.

Prohibited Customer-Facing Labels#

Do not use these words to describe the Shared Record total or customer activity:

• used
• consumed
• deducted
• reduced
• charged
• expected
• PacSpace measured
• PacSpace metered
• PacSpace calculated usage
• PacSpace says you used
• risk
• score
• rank
• health
• anomaly
• expected usage
• normal usage
• correct
• incorrect
• neutral truth

Developer APIs may still expose signed values such as signedDelta and netDelta because independent recomputation needs the math. Customer-facing labels should render the recorded fact first and reserve signed values for detail/export contexts.

English-Only Launch Stance#

Phase 1A, Phase 1B, and Phase 2 ship customer-facing Shared Record strings in English only. Locale and timezone may format dates and numbers, but the words themselves stay English.

Translations are a Phase 3 path. Before any translated Shared Record string ships:

1. The translation must pass a neutrality review.
2. The translated string must avoid local equivalents of the prohibited labels above.
3. The translated string must stay behind a feature flag until review is complete.
4. The terminology gate must include the translated string source.

Why This Matters#

"Recorded" keeps PacSpace in its role as a neutral record layer. The vendor writes the attestation. PacSpace records it and makes the record checkable. The customer and vendor decide what to do with that evidence in their own workflow.