OFN Receipts
Active portfolio classification — 2026-07-25 [D]. OFN Receipts is
shared proof substrate beneath Skyzai Personal and Skyzai Work. It is not an
independent SKU, package, authority, regulated audit, or live protocol.
Product-shaped or commercial language in linked historical sources does not
override this classification; route names do not prove deployment.
Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system.
A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt.
PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer.
AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt.
Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt.
Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.
Scope: proof substrate beneath Skyzai Personal and Skyzai Work — not a standalone SKU or authority source. See The Product Family.
Surface: ofn.app / OFN SDK surfaces (receipt-native substrate)
Status: PLACEHOLDER CANON
Evidence tier: [C] for this public wiki page until linked to the live OFN source package and external integration receipts.
What OFN Receipts Is
OFN Receipts is the shared receipt schema used by Skyzai surfaces to record consequential events: API usage, payments, event coordination/check-in, settlement badges, personal receipts, and organization-level audit events.
The role of this page is routing clarity. The product pages can point to one receipt primitive without claiming that a live public OFN protocol is operating from this .org wiki.
Required Boundary
- Receipts are evidence records, not legal advice.
- A stored receipt is not automatically a regulated audit, tax filing, or court-enforceable agreement.
- Consequential action must cross the authorization membrane first: a Natural Person authorizes their own typed private act; a Legal Person acts through lawful external authority and required executors; a public-DAV consequence requires a complete exact-consequence receipt bound by at least two natural-person councilors. PRISM records and verifies only.
- Receipt publication, replay, export, and anchoring remain deployment-gated until the exact runtime and counterparty integration are verified.
Relation to Product Surfaces
| Surface | Uses OFN Receipts For |
|---|---|
| API Pay | API usage receipts and replayable monetization events |
| Personal Receipts | User-owned receipt vaulting and export |
| Pay POS | Point-of-sale transaction evidence |
| Events | Non-economic invite, RSVP, attendance, and check-in receipts; ticket value routes separately to Pay |
| DEX Settlement Badges | Settlement evidence indicators |
Proof Gates
This page graduates from placeholder to active technical canon only when:
- The canonical OFN source package is linked from this repo path.
- A receipt can be emitted, verified, replayed, and exported from at least one Skyzai product surface.
- The integration has a test receipt and a human-readable verification receipt.
- The claim-control page confirms what is live, what is simulated, and what remains future-state.
See Also
K3 public-DAV authority history — 2026-07-12
K3 historical reference — not active authority
Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.