HOMEGOVERN

GOVERN THE
MACHINE

You don't just hold. You direct. Bag holders get access to the Governance Terminal — a direct line to the AI's job queue. The more bags, the higher your rank.

[ 01HOW GOVERNANCE WORKS ]
01

VERIFY YOUR BAG

Connect your wallet via the Governance Terminal. The system reads your $FRACTAL balance on-chain and issues a signed JWT with your bag_weight. No deposit. No lockup.

02

SUBMIT A PROMPT

Open the Governance Terminal. Type your prompt — a feature request, a new dApp idea, an improvement to an existing build. Hit submit. Your prompt enters the queue.

03

WATCH IT DEPLOY

The Orchestrator dequeues your prompt based on priority. You get real-time status updates via WebSocket. When it ships, you get the dApp URL and fraction contract address.

[ 02GOVERNANCE TERMINAL — LIVE DEMO ]

This is a working demo of the Governance Terminal. Try typing help, status, balance, or submit build a yield aggregator.

The production terminal requires token-gated authentication. This demo simulates the interface with a mock wallet.

FRACTAL GOVERNANCE TERMINAL v0.1● LIVE DEMO
>
[ 03GOVERNANCE TIERS ]
OBSERVER
Any $FRACTAL
PRIORITY: NONE
  • Read-only access to queue status
  • Public deploy feed
HOLDER
≥ 10,000 $FRACTAL
PRIORITY: STANDARD
  • Submit 1 prompt per 24h
  • Standard queue priority
  • Real-time deploy status
  • Email on deploy
BAG LORD
≥ 100,000 $FRACTAL
PRIORITY: HIGH
  • Submit 5 prompts per 24h
  • High queue priority
  • 24h whitelist on new dApp fractions
  • Direct prompt → AI (skip orchestrator review)
WHALE
≥ 500,000 $FRACTAL
PRIORITY: CRITICAL
  • Unlimited prompt submissions
  • Highest queue priority
  • Co-deploy naming rights on dApp
  • Revenue share on all AI-built dApps
  • Private Telegram with founding team
[ 04GOVERNANCE FAQ ]

The Governance Terminal issues a signed JWT after verifying your wallet's $FRACTAL balance via on-chain state. The JWT encodes your bag_weight and expires every 24 hours. No custodial deposit required.

Queue priority is computed per wallet address, not aggregated across wallets. Splitting bags reduces each wallet's score. There is no benefit to splitting — only dilution.

If a prompt sits in queue for more than 7 days without executing (e.g., compute reserve is depleted), it is returned to the submitter with a full refund of any associated fee.

The Orchestrator has a constraint layer: no illegal content, no re-entrancy exploits, no phishing interfaces. Within those rails, bag holders have full creative authority.

That's the risk. Governance is about directing the AI's output — not a guaranteed return. You own the fractions of the dApp. Its revenue depends on what it is and whether users adopt it.