Introduction
Developers: the Build pack (Claude Code) contains the
CLAUDE.mdto place in the repository and 34 ordered tickets with steps and verifiable completion criteria. The rest of this GitBook is the authoritative product specification.
Vivra V1 is designed to perform community takeovers (CTOs) of dead tokens on Robinhood Chain using AI agents. This document defines what needs to be built to launch cycle 1.
The product at a glance#
- At launch, the team publishes 5 candidates: Pons tech projects abandoned by their developers (previously above $500k, now between $15k and $50k, X account still online but silent, accessible docs), each with a dossier. A new vote and CTO follow every week.
- Users vote for 48 h, signed in by email, without a wallet.
- The winner becomes the “CTO token.” Six AI agents take it over for 72 h: analysis, identity, website, X, Telegram, and utility. Everything is recorded in a public log.
- Over 7 days, the Buyback Bot (a script, not AI) buys the CTO token in slices and burns every token: buyback & burn.
- Vivra submits an official CTO application to Pons. If accepted, 100% of the CTO token's future creator fees are allocated to buying back and burning $VIVRA.
- On Day 30, the CTO token's accounts are handed back to its community.
The specification launches $VIVRA on Pons with a total 4% trading fee: 1.7% team, 1.5% buyback, 0.5% AI, 0.3% Pons.
V1 scope#
| Component | Role | Section |
|---|---|---|
| Project analysis | On-demand analysis of team-submitted addresses: target, safety, recovery score | 4 |
| Cycle back-office | Create cycles, choose the five candidates, write dossiers | 5 |
| Voting | Email sign-in, one vote per email, public tally | 5 |
| Orchestrator and 6 agents | Run the CTO in 72 h with a public log | 6 |
| Buyback Bot | CTO token buyback and $VIVRA buyback & burn | 7 |
| Treasury | Claim Pons escrow, allocate funds, top up Surplus, maintain ledger | 3 |
| Pons CTO | Submit CTO application and receive CTO token fees | 8 |
| Dapp and landing | Landing and 4 dapp screens: vote, dossiers, war room, revived & ledger | 9 |
| X bot and Telegram | Vivra and CTO token accounts, automated posts | 10 |
User journeys and edge cases are described in section 14; they are the reference for tests.
Outside V1 scope#
- Vivra Scout (planned update): infrastructure that monitors the whole chain and automatically finds dead projects matching the target. In V1, the team finds projects and submits addresses manually.
- $VIVRA/TOKEN pools routing buybacks through $VIVRA (phase 5, early 2027 in the source roadmap).
- Open community nominations, life insurance, guest agents, and other chains.
- $VIVRA staking.
- An on-chain splitter for $VIVRA's 3% creator tax: V1 uses separate wallets and a public ledger.
References#
- Vivra V2 dossier (concept, economics, decisions).
- Landing and dapp mockups, and X page (creative assets, threads, bot templates).
- Technical appendices: database, API, agents (prompts and tools), contracts, recovery score, and setup.
- Visual identity: Inter Tight and Fragment Mono, ink #0B0B0C, orange #FF5A1F, background #FFFFFF.
Vocabulary#
- Candidate: one of the 5 tokens on a cycle's ballot.
- CTO token: the elected candidate during its takeover and follow-up.
- Cycle: vote (48 h), operation (72 h), buyback and verdict (7 days), follow-up (30 days). A new cycle starts every week, so cycles overlap. Day 0 = voting closes; T+x = hours after Day 0; Day +x = days after Day 0. The source uses J0 and J+x for these day markers.
- Token dossier: the agents' shared memory for a CTO token.
- Amounts are in USD unless otherwise specified; times are UTC.