MASON$MASON
FLOW ENGINE

HOLD is fail-closed

Neutral or unhealthy inputs route 100% to safety reserve and permit no automated market execution.

FLOW ENGINE · PRE-LAUNCH PREVIEW

How the live decision will read

Finalized market flow selects the mode. Only reconciled routed cashflow can fund the selected allocation.

NO LIVE VALUES
CURRENT DECISIONWAITING FOR FIRST FINALIZED EPOCH
NEXT EVALUATION—
FINALIZED NET FLOW—Curve + pool trades, deduplicated
NORMALIZED VOLUME—Minimum activity gate
POSITIVE CONFIRMATIONS— / 2Two epochs required for BUILD
POLICY HASH—Deterministic decision commitment
DECISION PIPELINE

One finalized path

  1. 01Observe tradesCurve + graduated pool
  2. 02Confirm flowFinality + deduplication
  3. 03Check riskEvery health gate must pass
  4. 04Publish policyMode + allocation + expiry
EXECUTION GATES

All required

  • INDEXERWAITING
  • FINALITYWAITING
  • RPCWAITING
  • SEQUENCERWAITING
  • ORACLEWAITING
  • LIQUIDITYWAITING
  • POLICY CURRENTWAITING

One failed gate selects HOLD. HOLD is an operating mode, not an error.

BUILDTwo healthy positive epochs

Build The Wall

70% WALL · 15% BUYBACK + BURN · 10% SAFETY · 5% OPS

DEFENDOne materially negative epoch

Activate defense

70% BUYBACK + BURN · 20% SAFETY · 5% LIQUIDITY · 5% OPS

HOLDNeutral flow or any failed gate

Stop market execution

100% SAFETY · 0% AUTOMATED MARKET EXECUTION

ROUTED CASHFLOW ONLYEvery decision includes epoch, sources, reasons, allocation, hash, and expiry.
PRE-LAUNCH

Live decisions begin after finalized MASON activity.

The live snapshot is incomplete. Flow Engine remains in HOLD until every required record is available. The chain head and pinned Pons V2 runtime are observable. Pons launch gate is OPEN at latest; recheck finalized state before signing.

Mode remains HOLD until live configuration, finality, oracle, liquidity, and policy-current gates all pass.