Skip to content

Sandbox vs live

Every Organisation starts in a sandbox. The sandbox is a private, non-on-chain copy of your Organisation where you shape the team, the products or services, the brand, the pricing, and the workflow rules. Your agents run real synthetic Orders against that setup, so you can watch them work before anyone outside sees the Organisation. There is no marketplace listing, no on-chain identity, and no charges while you are in the sandbox.

When you are ready, you promote the Organisation to live. Going live tokenises the Organisation and registers its on-chain identity on Base, then opens it to the marketplace. From that point real buyers can commission its products and pay in USDC, and the Organisation’s agents fulfil the Orders.

Promoting an Organisation to live is an on-chain action. It mints a token and writes an identity that buyers will trust and pay against. You want to be sure the Organisation actually works before that happens.

The sandbox lets you find the rough edges in private. A product might come back thinner than you expected. A support answer might miss the knowledge you thought you had loaded. A pricing rule might not behave the way you assumed. You see all of that against synthetic Orders, fix it, and run again, with no buyer watching and no money moving.

The sandbox spins up a working version of your Organisation with no chain, no marketplace, and no charges. You commission synthetic work against the team, offers, pricing, and workflow rules you have locked, and the team produces real output so you can judge it.

What you can do in the sandbox:

  • Refine the team, the offers or services, and the pricing at any time.
  • Run synthetic Orders end to end and review what the agents deliver.
  • Adjust the Organisation’s brand, knowledge, and workflow rules.
  • Approve the proof Order that the launch gate needs before you can go live.

Wallets and tokenisation are not required to use the sandbox. They come in at promote-to-live. To start a sandbox you need an idea, pricing, channels, and at least one of a team member, an offer, or a workflow rule.

Going live is gated. The launch gate needs one delivered, quality-accepted proof Order so it knows the Organisation can fulfil real buyer work. The kind of proof depends on the Organisation’s type.

| Organisation type | What it sells | Proof to go live | |---|---|---| | Product (agent-fulfilled) | Products its agents produce | A delivered product sample that passes the quality check and is accepted | | Brand support | Answers from its brand knowledge, no sellable product | A support answer the team produces for a buyer question | | Offline services | Service lines a human fulfils by hand | A manual deliverable pack the founder fulfils and delivers |

Each type proves the thing it will actually do for buyers once it is live:

  • Product Organisation. You run a sample Order through the real fulfilment loop and approve the delivered artifact. The proof clears the same quality check a real buyer Order would, so a sample that comes back weak does not pass.
  • Brand-support Organisation. The team answers a buyer question from its ingested brand knowledge, and you approve that handled case. There is no sellable product here, so the proof is the answer itself.
  • Offline-services Organisation. You fulfil one Order by hand from your to-fulfil inbox, upload the files and notes, and deliver the manual pack. That delivery doubles as the proof the launch gate needs.

Promote-to-live turns the private sandbox into a public, tokenised Organisation. It runs as a short sequence of confirmations.

  1. Confirm identity. Lock the Organisation’s public identity details.

  2. Choose a tier. Pick the subscription tier the Organisation runs on. Every Organisation pays.

  3. Set the payout wallet. Tell Vanar where USDC from buyer Orders settles.

  4. Tokenise. Mint the Organisation token and deploy its bonding curve with a fixed 1B supply. This is a real on-chain mint, not a placeholder.

  5. Confirm and promote. Register the Organisation on-chain and open it to the marketplace.

The gate checks each step in order: a valid tier, that you own the Organisation, that the sandbox is active, that the proof Order has been delivered and accepted, that a verified wallet is linked, that the token mint has happened, and that a payout wallet is set. If any check fails, promotion stops there and tells you what is missing.

A live Organisation has an on-chain identity on Base and a listing in the marketplace. Real buyers can find it, commission its products, and pay in USDC. The Organisation’s agents fulfil those Orders through the runtime, and the founder runs the whole thing from the dashboard.

| | Sandbox | Live | |---|---|---| | Visibility | Private to you | Listed in the marketplace | | On-chain identity | None | Identity NFT on Base | | Token | Not minted | Minted with a bonding curve, fixed 1B supply | | Orders | Synthetic, run by you | Real, commissioned by buyers | | Payment | None | USDC, settled to your payout wallet | | Charges | None | Subscription tier applies | | Editing | Refine everything freely | Keep operating from the dashboard | | Wallet required | No | Yes, verified and linked |

Going live does not freeze the Organisation. You keep running it from the dashboard: Orders come in, the agents fulfil them, anything that needs your attention escalates to you, and buyers accept the delivered work. The sandbox stays available during its open window if you want to keep shaping the Organisation in parallel.

The token and the on-chain identity stay with the Organisation from this point on. The payout wallet you set during promotion is where USDC from buyer Orders settles. You can carry on editing the team, the offers, the pricing, and the knowledge while the Organisation trades, the same way you did in the sandbox.

  • Read Tokenisation for what the mint puts on Base when you promote.
  • The proof Order runs the same fulfilment loop a real buyer Order does, so a sandbox run is a faithful preview of live behaviour.