Authy

Level L1 · self Publish locked IDs none Store pending
02

Sessions and grants

Apps get scoped tokens; the private key never leaves Browsy. Wizy asks Authy to sign bundles and grants. Peers verify with the public key.

Authy session and grant flow An app requests a scoped session from Browsy; Authy unlocks and returns a capability. Wizy asks Authy to sign a bundle grant; the peer verifies the signature and the grant paths before reading. APP / WIZY App asks for a session scope · purpose · app id scoped capability read · share · derive expiry · no private key BROWSY · AUTHY unlock + root key Ed25519 · passphrase/WebAuthn sign bundle + grant paths · capability · expiry request PEER / APP verify + read signature · key · expiry only granted paths signed no grant → no plaintext

Session flow. Authy signs; the app only holds the capability.

03

Data to Telegram to Authy

Data to Telegram to Authy claim thread The app asks Authy for a claim, Authy mints a one-shot nonce, the user opens the bot deep link, confirms in DM, and the verified level is stored locally. WEB · APP claim request clip / profile L3 → L4 persisted in localhost AUTHY nonce one-shot · TTL verify id == id store L4 ask TELEGRAM deep link t.me/bot?start=claim DM confirmation same id link user opens STORE flove:authy L4 · verified save level resolved

Data → Telegram → Authy. L3 is presence; L4 is the verified claim. The real bot replaces the simulated deep link.

03b

Authy → Appy

Model A: one-tap handoff from risa to AuthyTgBot Risa shows a Link Telegram button; the user starts AuthyTgBot with start=risa_key; the verifier stores presence; Appy polls and gets L3. RISA clip / profileTelegram auth in risa Link Telegramone button AUTHY BOT @AuthyTgBotstart=risa_key private DMTelegram presence open VERIFIER /claim?risapresence + atno id exposed store 5 min pollAppy APPY poll /claimL3 presenceMyNet read
Model A: sequence Five steps: risa auth, link Telegram, AuthyTgBot DM, verifier presence, Appy L3. 1risa authclip / risa key 2Link Telegramstart=risa_key 3AuthyTgBotDM verified 4verifierpresence claim 5AppyL3 + MyNet L4 / publishing still requires the separate Authy claim (nonce + DM).
Model B: signed risa claim through Browsy Risa bot signs a flove-auth/1 claim; Browsy peers pull it; Wizy derives on the peer; Appy verifies and grants L3. L4 remains Authy. RISA BOT sign claimflove-auth/1telegram presence BROWSY · WEB OF TRUST publish signed edgesubject · level · signature peers pull locallyWizy derives on the peer signed APPY verifyL3 presenceMyNet import AuthyL4 claimpublishing
Model B: sequence Six steps: sign, publish, pull, derive, import, L3; L4 remains separate. 1signrisa bot 2publishBrowsy edge 3pullpeers locally 4deriveWizy peer 5importAppy verifies 6L3MyNet L4 / publishing is always the AuthyTgBot claim, never the risa signature.
04

MyNet — enabled by Telegram, simplified from MyFamily

Authenticating Telegram (L3 presence) enables the MyNet features: people, circles, feed and local sharing. Appy shows two lock cards: MyNet local at L3 (people, circles, local feed, invites) and Social publishing at L4 (public posts, public groups).

Telegram enables MyNet, MyNet simplifies MyFamily Authenticating Telegram gives Authy L3 presence, which enables MyNet. MyNet uses a simplified MyFamily record, kept as L in Browsy. MODEL Authenticate Telegram · L3 presence claim → L4 verified MyNet enabled by Telegram people · circles · feed MyFamily · simplified person + relation 2–3 traits one affinity one L record per contact Browsy class L local federation L4 only adds public publishing

Diagram 1 · the model. Telegram is the switch; MyNet is the simplified MyFamily surface; Browsy keeps the record as L.

MyNet thread: Telegram to local data The appy-basic Authenticate card links Telegram, Authy enables MyNet, MyNet creates a simplified MyFamily record, and Browsy stores it as L for local peers. Appy Auth Authy MyNet MyFamily Browsy link Telegram · L3 enable MyNet create simplified record store as L · local peers presence grant features relation + traits + affinity P/L/S gate

Diagram 2 · the thread. Appy Auth → Authy → MyNet → simplified MyFamily record → Browsy L.

07

Bridge API (proposed)

What apps call from the page, and what Browsy exposes. Names are proposals; the capability shape is the important part.

CallReturnsNotes
flove.authy.status(){locked, level, identities[], publish}No handles or proofs.
flove.authy.unlock(factor){ok}Passphrase or WebAuthn; never returns the key.
flove.authy.session(scope){token, expires, caps[]}Scoped capability for one app/purpose.
flove.authy.link(channel, proof){ok, level}Verifies and stores the proof as P.
flove.authy.sign(payload){signature, keyId}Bundle/grant/revocation; asks once per session.
flove.authy.rotate(attestation){ok, newKeyId}Self-backup or quorum path.
flove.authy.recover(quorum){ok, probation}Social fallback; enters probation.
08

Migration from appy-basic

Today in appy-basicBecomesKept in the app?
IDENTITY_STEPS five-bar ladderAuthy level table + the same visual entry pointYes, as UI
state.linkedIdentities[]Signed channel proofs in the vault; a boolean summary for the pageYes, as cached summary
linkIdentity()flove.authy.link(channel, proof) + Personal pointsYes, calls Authy
publishUnlockedCapability from verified L4 (Telegram claim)Yes, reads Authy
Export identities[]Public summary only; proofs stay PYes, redacted
“Self” editor on profile cardProfile fields, not a channelYes
From now on this index is the reference for Authy; the appy card is the entry point. The plan links here from §12.5.