Labs sandbox · audited gated release

Pay grants from revenue. Pause before the well runs dry.

A model of an on-chain escrow that streams discretionary Freedom Grants to recipients out of an operator's monthly revenue — and trips a circuit-breaker if the treasury falls below a runway floor. No employment, no promise of perpetuity, no claim on principal.

Open the simulator How the gate works
Mechanism
Revenue-gated escrow
Guardrail
Runway floor auto-pause
Status
Sandbox · no funds at stake

The idea

A grant that adapts to what the business can afford.

Fixed payroll breaks when revenue dips. A revenue-gated grant doesn't — it pays from what comes in, holds back what it must, and tells the recipient honestly when it can't.

  1. 01

    Revenue lands first

    Operator revenue flows into the escrow contract before any grant is paid. The recipient never has a claim on funds that didn't actually arrive.

  2. 02

    Grants stream monthly

    If the treasury is healthy, each recipient receives their configured monthly grant on the cadence date — no invoicing, no approval loop, no review meeting.

  3. 03

    Runway floor auto-pauses

    If the treasury falls below the configured pause threshold — expressed in months of runway — the contract halts payouts. No grant is paid below the floor.

  4. 04

    Auto-resume on recovery

    When revenue rebuilds the treasury past the resume threshold, payouts restart. Missed months are not retroactively paid — the grant is discretionary, not an accrued debt.

The standout feature

Stress-test the escrow before you trust it.

Run a single deterministic timeline, or fire 1,000 Monte Carlo paths with revenue volatility baked in. You'll see survival rate, pause frequency, and the distribution of dollars that actually reach recipients — not just the happy-path number on the contract.

Survival rate

—

Share of timelines that finish solvent.

Total paid to recipients

—

Median across all timelines.

Months paused

—

Median pause-months out of horizon.

Longest pause

—

Worst single pause stretch seen.

Treasury balance

Single deterministic path. Pause threshold and resume threshold shown as dashed runway floors.

Monthly cashflow

Revenue in, grants out, net retained.

Pause / active timeline

Green months pay grants. Red months are auto-paused.

What this run says

Run the simulator to populate this read-out.

Tighten or loosen?

If survival is below 90%, raise the pause threshold or lower the per-recipient grant. If you pause more than 20% of months, your revenue floor is too thin.

Plain-text summary of the latest run (screen-reader friendly)
Run the simulator to generate a summary.

The contract, in plain English

Six rules the escrow enforces every month.

  1. Revenue settles before payout.

    On each cadence date, all revenue received since the last cycle is credited to the treasury before any grant calculation runs.

  2. Runway is the gate, not balance.

    The gate measures treasury in months of total grant outflow. Twenty thousand in the bank means nothing on its own — the contract asks "how many months of grants does that cover?"

  3. Pause is automatic, not discretionary.

    The operator cannot vote to keep paying below the floor. Pausing is a property of the contract, not a judgement call.

  4. Resume requires a buffer, not just a touch.

    To prevent oscillation, the resume threshold sits above the pause threshold. Treasury must recover to a higher floor before payouts restart.

  5. Missed months do not accrue.

    Paused months are skipped, not deferred. The Freedom Grant is explicitly discretionary: a recipient is never owed a back-paid lump sum on resumption.

  6. Wind-down is graceful.

    If the operator chooses to end the program, the contract continues paying down to the pause threshold and then halts. No surprise drainage of the treasury, no clawbacks from recipients.

Honest fine print

What this is — and what it isn't.

What it is

  • A modelling sandbox for a revenue-gated grant escrow.
  • A discretionary giving mechanism designed to never overdraw the treasury.
  • An honest illustration of how auto-pause and auto-resume would behave under volatility.
  • A research artifact published by TIMxAI Labs.

What it isn't

  • Not employment, not salary, not an offer of work.
  • Not a promise of perpetuity. Grants pause when revenue dips and may never resume.
  • Not deployed: no live contract, no funds at stake, no audited release on this page.
  • Not financial advice. Numbers you enter never leave your browser.

A real deployment would require: third-party audit of the escrow contract, on-chain accounting transparency for recipients, clear written acknowledgement that participation is at-will on both sides, and a published wind-down policy. None of those are present here. This page is a sketch on paper.