Status: pre-launch. This page describes target design; this document does not establish a deployed service.

Flow-Axiom — Money Flows Only While the Condition Holds

Current reading — 2026-09-27

Conditional payment is a research proposal. An authorized schedule must identify its asset, recipients, limits, evidence source, pause/resume and dispute rules. Forecast prices are not observed service truth; SPECTRE transport is not settlement finality. Credit, liquidity, operational, legal and systemic risks remain. [I]

This is an editorial boundary, not a new runtime contract, upstream repeal or proof of adoption. See current status and the product roles. Original revision dates remain as recorded below.

Historical research draft — retained on 2026-09-27; not current terms or implementation instructions

This page describes the target Flow-Axiom settlement primitive. Read the mechanism, automation, and risk-elimination language below as target design unless a narrower runtime proof has explicitly closed the lane.

In the target design, FlowWallet streams are conditioned on AXIOM market states. This is the primitive intended to eliminate five categories of settlement risk simultaneously. It is the organism's answer to the question: how do you pay for something that might stop being true?

The Mechanism

A FLOW stream (1:1 continuous payment) is conditioned on an AXIOM (an N:1 recorded outcome from ReFu). In the target design, the stream auto-pauses when the AXIOM's confidence drops below a trigger threshold. The stream auto-resumes when confidence recovers.

FlowWallet.stream({
  from:      sender_pubkey,
  to:        receiver_pubkey,
  rate:      0.001 ZAI/second,
  condition: AXIOM("service_uptime > 99.9%"),
  trigger:   0.85,  // pause if AXIOM confidence < 85%
  grace:     3600   // 1 hour grace period before pause
})

How It Works

1. Sender creates a FLOW stream to receiver, conditioned on a specific AXIOM.
2. The AXIOM is a live ReFu prediction market. In the target design, its price = probability that the condition is true.
3. While AXIOM price > trigger: tokens would stream continuously from sender to receiver on SPECTRE.
4. When AXIOM price < trigger: the stream would enter grace period. Tokens would accumulate in Algorithmic TRO.
5. If AXIOM price recovers within grace: accumulated Algorithmic TRO would release to receiver. Stream resumes.
6. If AXIOM price stays below trigger past grace: the stream would pause. secured via Algorithmic TRO tokens would return to sender.
7. When AXIOM resolves definitively: final settlement. Receiver would keep all streamed tokens. Sender would keep unstreamed balance.

Five Settlement Risks Eliminated

Traditional finance has five categories of settlement risk. Flow-Axiom is designed to eliminate all of them:

Risk	Traditional	Flow-Axiom
Credit risk	Counterparty may not pay	In the target design, the stream is pre-funded. Tokens exist in the FlowWallet before streaming begins.
Liquidity risk	Payment may be delayed	Streaming is continuous. No batching, no settlement windows, no T+2.
Operational risk	Systems may fail	The target SPECTRE substrate is aBFT. No single point of failure.
Legal risk	Contract may be unenforceable	Condition is an AXIOM (a recorded market outcome under stated rules), not a legal clause. Code executes.
Systemic risk	The whole system may fail	Streams are bilateral (FLOW = 1:1). One stream's failure does not cascade.

The Condition-Gating Property

The critical innovation: in the target design, money flows only while the condition holds. This inverts traditional finance, where money flows first and the condition is checked later (audits, reconciliation, disputes, litigation).

In Flow-Axiom:

• In the target design, the condition (AXIOM) is checked continuously by the crowd (ReFu market participants with skin in the game)
• The money (FLOW) is conditioned on that continuously checked condition
• If the condition stops holding, the money would stop automatically
• No human intervention would be required for pause/resume
• No legal system would be required for enforcement

Use Cases

Service-level agreements: Target pattern: stream payment conditioned on uptime AXIOM. Service goes down, payment pauses. No invoice disputes.

Employment: Target pattern: stream salary conditioned on project-delivery AXIOMs. Milestones verified by prediction market, not by manager. No performance review politics.

Insurance payouts: Target pattern: stream insurance conditioned on no-claim AXIOM. Claim event occurs (AXIOM flips), stream redirects to claimant. No adjuster delays.

Supply chain: Target pattern: stream payment conditioned on delivery-confirmation AXIOM. Goods in transit, payment streaming. Goods lost, payment pauses. GPS + crowd verification feeds the AXIOM.

The Composability

Flow-Axiom composes with other primitives:

• RELAY + AXIOM + FLOW: Target pattern: Circle broadcasts alert (RELAY), ReFu market resolves (AXIOM), FlowWallet adjusts (FLOW). End-to-end: intelligence triggers financial action.
• Multiple AXIOMs: A single FLOW can be conditioned on AND/OR combinations of AXIOMs. "Pay while (uptime > 99.9% AND reputation > 0.8)."

---

Money follows the condition, and the condition is priced by skin in the game. A market price is a probability, not a certainty.

---