Dapp and landing page
The landing page and 4 dapp screens follow the approved mockups, in English, with Vivra's visual identity. The dapp never requires a wallet: users sign in by email to vote and buy $VIVRA on Pons.
Screens#
| Screen | Content | Data | Real time |
|---|---|---|---|
| Landing | AI takeover hero, classic CTO vs Vivra CTO, agents, 72-hour CTO, flywheel, fees, rules | static plus /stats figures | no |
| Vote | 5 launchpad-style cards: project banner and picture, name, category, thesis, social buttons, recovery score, key figures, vote share; voting panel with email sign-in | cycle, candidates, votes | yes |
| Candidate dossier | one tab per candidate; all section 5 blocks, including the recovery score and breakdown | dossier, candidate tracking | market every 60 s |
| War room | CTO token, live chart, steps, 4 metrics, log, buyback (slices, cap), agent team, new links | operation, log, slices | yes, WebSocket |
| Revived & ledger | past CTO tokens and status, flywheel figures, weekly ledger, wallet addresses | ledger, operations | every 5 min |
Sign-in#
- Email with a magic link or six-digit code. A 30-day device session.
- No wallet requested anywhere. The Buy $VIVRA button links to the token's Pons page.
Real time#
- One WebSocket channel per operation: new log rows, executed slices, step changes.
- The live chart updates for each CTO token trade (pool or curve events).
- Vote shares update after every vote.
General requirements#
- Responsive: every screen usable at 390 px width.
- Accessibility: sufficient contrast, keyboard navigation, reduced-motion preferences respected (animations stop).
- Every displayed number links to its source: transaction, contract, or ledger row.
- Legal notice on every page (no promised returns, risks).
Acceptance criteria#
- All 4 screens match the mockups on desktop and mobile.
- A vote appears in the shares within 5 s.
- The war room follows a test CTO live without reloading.