On this page
SPECTRE
Carries signed events and evidence references under declared communication contracts. Routing and relay admission do not prove settlement.
Communication contractsSPECTRE · OFN receipts
Follow the evidence.
Inspect who acted, under which authority, what was recorded and what remains unresolved. Delivery, settlement and anchoring keep separate states.
A common trail. Typed records.
Skyzai’s current design uses a common receipt envelope and evidence trail, with immutable typed records for authority, execution, effects and outcomes. Hash references connect the relevant records; domain payloads retain their own meaning.
OFN · ofn.app owns the economic receipt payload, ofn.economic_receipt.v1. It records parties and roles, order and payment references, exact decimal amounts and currencies, the payment rail, settlement state, and named tax, refund and remedy responsibilities.
OFN is separately owned. An economic receipt is one typed payload inside the common trail; it does not replace every other record or give its holder authority to act.
Three questions. Separate answers.
- Delivery
- Did the intended recipient acknowledge the message under the delivery contract? A Nostr relay’s OK indicates relay admission, not end-recipient delivery.
- Settlement
- What state does the economic record report, on which rail, with which supporting evidence? A recorded payment claim is not proof of product delivery or agreement fulfilment.
- Anchoring
- Has an evidence reference been anchored, where, and with which finality evidence? A separate append-only AnchorReceipt tracks this lifecycle. An unanchored local record can still be evidence within its stated scope.
These states can change independently. The interface must show the claim, source, scope and unresolved work rather than collapse everything into one “verified” badge.
The launch direction uses Hedera and Nostr, with later integration into SPECTRE. An OFN receipt would identify the actual payment rail and its settlement evidence; the platform names alone do not prove delivery, payment or anchoring.
Read one record, without assuming the outcome.
This synthetic teaching example shows the questions an economic receipt should answer. It is not a signed OFN receipt, a schema conformance fixture or a real transaction.
The missing fields are meaningful. A converter should return a typed failure when required economic evidence is absent, rather than manufacture a valid-looking payment receipt.
Where OFN connects.
SoResFi and Markets
Financial arrangements and commercial journeys supply their own domain facts. Product, payment, fulfilment and remedies retain separate evidence.
Financial arrangements · Skyzai MarketsMe, We and They are the participants’ views into these journeys. Permissioned evidence should travel with enough context to be inspected, without treating private records as public by default.
Inspect the source. Know the maturity.
The current boundary is specified in the normative decision register and its receipt-envelope, economic-receipt and relay-acknowledgement resolutions. These are design resolutions, not evidence of a connected production settlement or anchoring service.
The GitHub sources may require repository access. Implementation, validation, converter fixtures and deployed anchoring remain separate completion gates.