Q token mark QUADPublic Accountability

Complete enough to claim

Acceptance Paths

Acceptance paths define what a complete journey needs to show before a public page treats it as more than a partial proof. They include success, refusal, delay, recovery, and support paths.

One happy path is not product readiness. A useful journey has a named owner, fee, status, receipt, failure path, and boundary.

Acceptance Standard

A journey is accepted only when the public reader can follow it without private translation.

OwnerWhich chain or surface owns the action and result.
ActionWhat the visitor, operator, route, or module is allowed to do.
CostFee, quote, gas, proof cost, refund, or service charge where relevant.
FinalityDelay, confirmation, expiry, acceptance, settlement, quarantine, or terminal label where relevant.
ReceiptThe public id or proof route that preserves the event.
FailureRefusal, timeout, unpaid, stale, duplicate, invalid, quarantine, or recovery path.
BoundaryWhat the journey does not prove.

Journey Matrix

These paths are public acceptance targets. The owning subdomain still carries current route state.

Tooling can read the static journey standard at data/acceptance-journeys.json. The file is an acceptance register, not proof that a route is open or complete.

JourneyEvidence neededBoundary
Core transactionCore chain state, wallet metadata, fee label, transaction result, receipt or block link, refusal/quarantine label where relevant, and current status.A Core transaction is not sale access, allocation, liquidity, Treasury admission, or economic activation by itself.
Infra upload / verify / retrieveBIGHT quote or funding state, upload acceptance, receipt id, verification route, retrieval route, failure label, and service boundary.Infra service proof is not payload truth, Core value, Bridge finality, Liquid settlement, or fixed-value redemption.
Infra contract workQuote, accepted contract state, account or contract label, receipt, balance/ledger label, reissue path, and cancellation or expiry behavior.Contract state is not private payload disclosure, provider entitlement, or external custody.
Provider settlementProvider posture, accepted work, escrow or payable label, proof/challenge window, settlement/refusal result, and public metadata update where available.Provider settlement evidence is not a node-earning promise, reward program, or special allocation.
Bridge route / refund / refusalIntent, quote, route label, source pool or owner-vault posture, gate result, host evidence, receipt, refund/surplus/refusal label, and destination boundary.Bridge passage does not force destination admission, wrapper minting, redemption, swap access, or native ownership.
Liquid position lifecycleQuote, order or motion record, position state, risk label, wrapper label where relevant, settlement owner, refusal/liquidation path, and state freshness.Liquid motion is not final settlement, Core worth, public market activity, or balance truth by itself.
Support / reissueSurface, action, public id, current state, expected next step, receipt search, reissue path, evidence bundle, and what changed.Support can explain and reissue bounded evidence; it cannot expand what the original receipt proved.
Fee / finality reviewOwner, quote id, expected denom, expected amount, fee components, expiry, actual charge, finality label, receipt id, and difference reason.Fee labels do not prove custody, yield, admission, destination acceptance, or final settlement outside the owner surface.
Action lifecycleOwner, request, quote, payment/signature, execution, waiting, receipt, stop state, holding state, and closure label.A lifecycle label does not open a route or strengthen what the owner has published.

Accepted Outcomes

A real product path needs terminal states, not just green checks.

Completed

The owning surface shows the action, result, receipt, fee, and finality or delay label.

Refused

The route says no with a named reason and a next public check.

Pending

The route names what it waits for: payment, proof, finality, sibling state, review, or recovery.

Recovered

A timeout, retry, reissue, refund, repair, or restore path produces its own receipt or status.

Quarantined

Boundary-crossing material is held for classification instead of being admitted as clean state.

Downgraded

Stale or partial evidence stays useful, but the public claim becomes smaller.

What Does Not Count

These can be useful evidence, but they are not enough to claim product readiness.

One happy transaction

It proves one path was possible, not that failures, refunds, stale data, or support are ready.

Local-only proof

It can guide development, but public readers need a public route or a clear local-only label.

Static snapshot

It is not current telemetry unless the owning surface publishes freshness and current-state evidence.

Sibling success

Core, Infra, Bridge, and Liquid do not inherit each other's acceptance state.

Interface button

A visible button does not mean the action is allowed, funded, live, or safe to attempt.

Community report

Useful for triage, but not a replacement for owner-surface receipts or status.