Wiki

The RIVR wiki documents every user-facing surface at click level. Each page follows the same five-slot template so behavior is described the same way everywhere:

What it is — a one-paragraph definition.
Where it lives — the route(s) and repo file anchors.
Every interaction — each button, menu, and form, and what it does.
Permissions / gating — who can see or do it, and what's hidden for whom.
Cross-links — related surfaces, API/MCP tools, and federation behavior.

Map, not final product-truth

These pages are drafted from the product-surface inventory, the user-capability matrix, and the code knowledge graphs, then verified against the live app. Where a slot is still thin it is marked TODO — treat those as leads to verify, not guarantees.

Surfaces

Core surfaces

Feeds & posts — home feed, post detail, composer, reactions, comments.
Explore & search — discovery surfaces (public).
Calendar & events — RSVP, ticketing, GCal.
Messages — DMs + Matrix group rooms.
Marketplace & gifts — listings, checkout, receipts, thanks-token gifting.
Wallet & treasury — balances, transactions, memberships, points.

Groups & coordination

Groups & subgroups — membership toggles, org tabs, lineage.
Projects & jobs — treasury, deliverables, job claims.
Governance — proposals and decisions.
Badges & stake — badge issuance, points-based stake.
Docs, filesystem & vault — the faceted-tag docs filesystem + ACLs.

Identity & extension

Federation & SSO identity — sovereign homes, verified principal.
Autobot & agents — personas, connectors, MCP act-as.
Builder — site builder → publish to custom domains.
Locales & regions — place-scoped surfaces.

Account & operator

Membership & capabilities — tiers, what each unlocks, Connect payout accounts.
Account & settings — profile, data export, notification prefs.
Admin — operator surfaces (admin-gated).