Q markQUADEconomic Activation

Economic Activation

Activation means permission to attempt an action, not a promise that an action will happen. QUAD Core can wake, check, act, refuse, or sleep depending on truth, timing, worthiness, safety, and supply posture.

Activation rule

Economic activation is local and conditional. A live chain, a funded account, or a visible balance does not force a module to act.

Wake

A module may wake on its cadence or when a public transaction reaches its keeper.

Check

The module checks committed truth, market state, NAV posture, timing, supply law, asset class, dust, and module-specific worthiness.

Act

If the gate passes, the action must preserve provenance and use the correct routing surface.

Sleep or refuse

If truth is stale, unsupported, unsafe, dusty, underfunded, over cap, or out of cadence, doing nothing is valid behavior.

Economic surfaces

These surfaces can activate only inside their own boundaries. This page does not expose private thresholds or operator runbooks.

Current activation observations

These figures are public testnet observations. They are not proof of mainnet economics, production readiness, reward eligibility, or future entitlement.

QUAD supplychecking
Admitted backingchecking
Sink pendingchecking
Total burnedchecking
Tx gatechecking
Metrics updatedchecking

Financial posture

Accounting labels keep activation from becoming a spending claim.

Labelchecking
Statuschecking
Refusalschecking
Exceptionschecking
Admitted NAVchecking
Feed updatedchecking
Loading financial posture...

What activation refuses

Refusal is part of the product. It is how Core avoids pretending unknown state is healthy state.

  • No launch claim. Economic activation on testnet is not mainnet launch, production economics, or a freeze declaration.
  • No reward promise. Activated surfaces do not create reward eligibility, allocations, ownership, governance rights, leverage, or future entitlement.
  • No forced routing. Treasury cannot route, trade, split, pay invoices, or decide behavior; Alloc remains the value-routing surface.
  • No stale truth. Unknown, stale, unsupported, unsafe, dusty, or over-cap state should reduce authority or cause sleep/refusal.
  • No hidden swap claim. Bridge, exchange, provider, or adjacent-chain activity does not force Core admission or create value by itself.