Q token mark QUADPublic Accountability

From request to closure

Action Lifecycle

A public action should move through named states: owner, request, quote, payment or signature, execution, waiting, receipt, and closure. If the action cannot proceed, refusal, refund, quarantine, expiry, or stale-state labels should say so.

A lifecycle page explains the shape of action. It does not open any route by itself.

Lifecycle Shape

Use the same readable shape across Core, Infra, Bridge, Liquid, support, wallets, and product screens.

StagePublic questionBoundary
1. OwnerWhich surface owns this action and result?Linked pages do not merge chain authority.
2. RequestWhat is being asked: observe, fund, upload, retrieve, route, quote, order, prove, vote, support, or settle?A request is not acceptance.
3. QuoteWhat expected denom, amount, fee class, expiry, route, or service class applies?A quote is not custody, liquidity, redemption, or settlement.
4. Payment or signatureWhat payment proof, wallet signature, chain transaction, or public acknowledgement is required?Signing or paying does not force success.
5. ExecutionWhat did the owner actually do: include, accept, store, route, observe, refuse, hold, recover, or settle?Execution on one surface is not final truth on every surface.
6. WaitingWhat finality, confirmation, review, proof, recovery, or expiry window remains?Delay is a state, not a hidden promise.
7. ReceiptWhich public id proves the bounded event, refusal, refund, proof, route, or settlement request?A receipt proves its own event and owner.
8. ClosureIs the action completed, refused, expired, refunded, quarantined, recovered, stale, or terminal?Closure should not be inflated into reward, sale, allocation, or launch language.

Lifecycle Flow

Good product screens should make the next state obvious without exposing private mechanics.

Request

Name owner, action, asset/object/route, and status.

Quote

Name expected denom, amount, fee classes, expiry, and route or service class.

Commit

Show payment proof, signature, transaction hash, or accepted acknowledgement where required.

Wait

Show confirmation, proof, finality, review, recovery, or expiry state.

Receipt

Give the public id, proof class, owner, status, and boundary.

Close

Completed, refused, refunded, quarantined, expired, recovered, stale, or terminal.

Product Lanes

The lane decides which lifecycle labels matter most.

LaneLifecycle emphasisMust not imply
Core transactionOwner, chain tx, gas, block inclusion, finality, receipt, quarantine/refusal, admitted or terminal label where Core publishes it.Sale access, allocation, liquidity, Treasury admission, or economic activation by itself.
Infra workBIGHT quote, funding proof, upload/retrieve/proof action, accepted work, receipt id, reissue or failure state.Payload truth, Core value, raw compute reward, or guaranteed payout.
Bridge passageIntent, quote, source pool, host cost, finality, gate result, receipt, refund, quarantine, refusal, destination handoff.Destination admission, native ownership, redemption, wrapper minting, or live movement.
Liquid motionQuote, order, expiry, position, risk, wrapper, liquidation/refusal, settlement owner, receipt, and finality label.Final balance truth unless the settlement owner records it.
Support or reissueSurface, public id, current state, evidence packet, reissue quote, receipt, and unchanged proof boundary.Support cannot expand what the original receipt proved.
GovernanceProposal type, affected surface, vote state, threshold class, machine consequence, failure state, and proof route.Private override, discretionary law, or authority outside the proposal's owner.

Stop States

  • Refused: the owner rejected the action, route, payload, quote, or interpretation.
  • Expired: the quote, route, payment window, proof window, or action window ended.
  • Unpaid: the owner has not accepted payment proof or required funding state.
  • Invalid: the request does not match the public contract or expected shape.
  • Unauthorized: the action or private material is not available from the public lane.
  • Unavailable: the route or owner surface is not answering under its public contract.

Holding States

  • Pending: accepted for public processing or waiting for a named condition.
  • Confirming: visible but waiting for more finality, proof, or review.
  • Quarantined: held away from clean state until evidence clears, refuses, or terminalizes it.
  • Degraded: answering below normal freshness or completeness.
  • Stale: old enough that current state cannot be quoted from it.
  • Recovered: a timeout, repair, reissue, retry, or restore has its own receipt or status.

Receipt Closure

A receipt should close a loop, not open an unlimited story.

Closed as completed

The owner records the action, result, fee or amount, finality label, receipt id, and boundary.

Closed as refused

The owner records a refusal reason and public next check without implying retry will pass.

Closed as refunded

The owner records expected amount, actual amount, refund state, and receipt id where public.

Closed as quarantined

The owner records what is held, why public action is blocked, and what public state can clear or terminalize it.

Closed as stale

The owner or main site shows last known state and says current state cannot be verified.

Closed as terminal

The record has no further public action available unless a new owner-published route begins.

Retention And Tombstone States

Some evidence should survive after payload access ends. The public state should say whether a record is retained, pruned, tombstoned, restored, reissued, cold, expired, or terminal.

StatePublic meaningDo not infer
Retained receiptReceipt metadata remains visible enough to interpret the bounded event.Payload access, payload truth, Core admission, Bridge finality, or Liquid settlement.
Payload access endedThe receipt may remain, but payload body or private metadata is no longer public or available from that lane.Deletion proves wrongdoing, endorsement changed, or the record never existed.
TombstonedA handle ended, moved, expired, became unavailable, or reached terminal state with a surviving marker.Custody failure, route failure, payload truth, or private review outcome.
PrunedOld rows, snapshots, or non-current values were removed or replaced.Current state, dataset completeness, or owner acceptance by another surface.
Restore or reissueA new owner-published route or receipt may reopen access, reproduce metadata, or certify old evidence.A new truth claim or expanded scope for the old receipt.

Machine-readable retention rules are published at data/retention-policy.json.

Public Screen Checklist

Any action screen should answer these before it asks a user to act.

Required answerGood public wordingBad public shortcut
OwnerThis action is owned by Infra.The stack will handle it.
CostQuote required; expected denom and expiry shown.Just click pay.
DelayWaiting for finality, proof, review, or receipt closure.Processing.
RefusalRoute refused because the public contract does not support this denom.Something went wrong.
ReceiptReceipt id proves upload acceptance only.Proof complete.
BoundaryThis does not prove Core admission or destination acceptance.Success.