What Can You Do is a trust-based social and hookup platform where users build reputation through real-life connections and vouching. The product's intent is to build a community in which trust is earned, not assumed: new users join, verify themselves with a selfie, and then must be vouched for by already vouched and verified users before they can text or post anything. Every profile carries a public ledger of how many people vouched for that user and how many people that user vouched for, so reputation is visible at a glance.
The audience is adults in Nigeria (and comparable markets) seeking to chat, meet, and hook up with people whose real-world connections have been attested by others. The platform is deliberately warm and human rather than slick: trust comes from real vouches and real in-person meetings, and the interface should read like a printed community ledger, not a growth-hacked social feed.
This document is the System Requirements Document for the project named What Can You Do (the requester also selected the working name "retro-what" during intake; the product name used throughout is What Can You Do).
What Can You Do is delivered as a first-party web application with application-owned identity. The public entry is the Landing page, which explains the trust-based community before any identity step. New users create an account and complete selfie verification on Sign Up; returning users verify identity on Login. Once inside, the working surfaces are Profile (vouch counts, profile pictures, in-person experience comments), Vouch (a verified vouching user vouches for a friend), Messages (text messaging between vouched users), Chat Rooms (rooms with a live count of people online), and Calls (in-app voice and video calls).
Access is layered by trust state, not by a general role system. Anyone can reach Landing, Sign Up, and Login anonymously. Profile, Messages, Chat Rooms, and Calls require a logged-in session. Vouch, Messages, Chat Rooms, and Calls are restricted to users who are verified and vouched for; an unvouched user who reaches those surfaces sees a blocked state explaining that they must be vouched for first, with a pointer back to their profile and the vouch counts that show their standing. Selfie verification is completed at Sign Up as part of account creation; it establishes the verified state but does not by itself grant posting or texting rights — the vouch is what unlocks those.
The current delivery is the web application plus a shared backend, a relational database, and Redis for live presence and coordination. Voice and video calling are delivered inside the app as first-party call surfaces; the underlying media transport is an implementation concern of the Calls surface and does not create a separate product destination. Nothing in this document commits to native mobile apps, payments, moderation tooling beyond the stated constraints, or any capability not named in the accepted requirements.
Removed from scope
Not applicable — no reference directive with content_source was supplied.
Each requirement is stated as a user story with provenance, lifecycle facts, and observable acceptance.
FR-1 — Account creation with selfie verification (explicit; required_inference for the Sign Up placement) As a New user I should create an account and complete selfie verification so that I am a verified member of the community.
FR-2 — Returning identity verification (required_inference) As a returning user I should verify my identity at Login so that I can reach my protected work.
FR-3 — Verified, already-vouched users vouch for friends (explicit) As a Verified vouching user I should vouch for a friend I know and trust so that the friend becomes a trusted member of the community.
FR-4 — Profile shows people who vouched for the user (explicit) As a user I should see on my profile the number of people who vouched for me so that my trust standing is visible.
FR-5 — Profile shows people the user vouched for (explicit) As a user I should see on my profile the number of people I vouched for so that my contribution to the community is visible.
FR-6 — Text messaging between vouched users (explicit) As a Verified vouching user I should chat with other users so that I can build connections before and after meeting.
FR-7 — In-app voice and video calls (explicit) As a Verified vouching user I should make voice calls and video calls inside the app so that I can talk face to face with people I trust.
FR-8 — Chat rooms with online counts (explicit) As a Verified vouching user I should join chat rooms that show how many people are online so that I can find an active community.
FR-9 — Posting pictures to one's own profile (explicit) As a Verified vouching user I should post pictures on my own profile so that people can see who I am.
FR-10 — In-person experience comments (explicit) As a Met-in-person user I should comment my experience on another user's profile after we met in person so that others can see real-world feedback.
FR-11 — Unvouched users cannot text or post (explicit) As an unvouched user I should be prevented from texting or posting until I am vouched for so that the community's trust gate is enforced.
FR-12 — Trust-based community identity (explicit) As a user I should experience a trust-based social and hookup community so that connections are grounded in real vouches and real meetings.
Muse and headline: Frank Chimero — warm editorial trust. The page should feel like a printed community ledger: cream ground, ink text, rust marks for primary actions and vouch counts, mustard for online counts and rules.
Mode: Light mode only.
Colour tokens (exact hex by role):
#F4EDE1 (cream ground, covers most of the page)#FBF6EC (panels and reading surfaces)#211D1A (ink)#8C3B2B (rust — primary action, vouch counts)#C9A227 (mustard — online counts, rules)#6B6357 (secondary text, labels)Typography:
clamp().Shape language: Flat panels with 2px ink rules. Small 6px radii. Hand-drawn underline marks in rust. No glass, no soft shadow stacks.
Layout: One centred reading column of 680px. Section openers use a small illustrated mark and a rule. Profile counts sit as ruled label and value pairs.
Imagery: Warm flat spot illustrations of two people, a handshake, and a phone. Hand-drawn diagrams of the vouch chain. No stock photos.
Accessibility: Readable text and controls stay whole at 375px, 768px, and 1280px, wrapping or scaling to fit; decoration may bleed but never covers text or controls. With prefers-reduced-motion, a usable static arrangement is provided.
The public entry (Landing) is a cream page with a wide ink rule at the top. A large Fraunces headline — "Trust starts with one real vouch." — spans nine columns on the left at up to 96px. A rust panel on the right holds a flat illustration of a vouch chain: a hand-drawn diagram of one verified user vouching for a new user, with ruled label/value rows showing "people who vouched for me" and "people I vouched for". The CTA sits under the headline as a rust block button reading "Get vouched". The subline "Meet people, vouch for friends you trust, and build a profile that shows your real connections." sits beneath the headline in Literata. Section openers below the hero use a hand-drawn rust mark and a full-width ink rule to introduce how vouching works. The concept recomposes only accepted content and controls — it adds no new behaviour or destination.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief

retro-what
Meet people, vouch for friends you trust, and build a profile that shows your real connections.
The vouch chain
Nobody is trusted by default. A new member becomes verified with a selfie, then a friend who is verified and already vouched for vouches for them. That single vouch opens up texting and posting.
You create an account and submit a selfie. It confirms you are a real person.
Someone who is verified and already vouched for vouches for you, because they know and trust you.
With one vouch on record, you can text, post pictures to your profile, and join the community.
Vouches come from people who know you in real life. They are meant to mean something.
Every profile keeps two figures in plain view — how many people vouched for you, and how many people you vouched for. They are ruled rows, not badges, so your standing is read at a glance by anyone who meets you here.

retro-what
Meet people, vouch for friends you trust, and build a profile that shows your real connections.
The vouch chain
Nobody is trusted by default. A new member becomes verified with a selfie, then a friend who is verified and already vouched for vouches for them. That single vouch opens up texting and posting.
You create an account and submit a selfie. It confirms you are a real person.
Someone who is verified and already vouched for vouches for you, because they know and trust you.
With one vouch on record, you can text, post pictures to your profile, and join the community.
Vouches come from people who know you in real life. They are meant to mean something.
Every profile keeps two figures in plain view — how many people vouched for you, and how many people you vouched for. They are ruled rows, not badges, so your standing is read at a glance by anyone who meets you here.
No comments yet. Be the first!