Community
The people layer of flove. This is a launcher with a content plan, not a feed: nine numbered rows, each with concrete options and one safe default per channel.
Content plan — what can live here
-
Community & channels framework
Give every community doc one navigation home and mark it live or historical.
A Live-doc mapB Authority line per docC Historical shelfSource: wiki index · Docs · ▸ diagram -
Moderated feedback flow
Each onboarding tour opens with welcome, states one idea, then walks the rows in order.
A Welcome → idea → rowsB Moderation queueC Feedback ledgerSource: wiki index · Feedback · ▸ diagram -
Language and audience policy
Name the audience and one default for es/en content, following §13.1.
A Audience cardB es/en default chipC Translation queueSource: wiki index · Language · ▸ diagram -
Contribution-channel model
Project standards fix the paths, rules and presets every generated plan follows.
A Channel presetsB Contribution pathsC Plan generator rulesSource: wiki index · Channels · ▸ diagram -
Community ladder
The risa v2 plan names Authy as the channel-agnostic identity layer and Telegram as one driver.
A Ladder levelsB Identity + driver mapC Risa status gatesSource: risaliberada/plan-v2.md · Levels · ▸ diagram -
Community documentation plan
Every live debate doc has one authority line in the community index.
A Authority linesB Doc indexC Owner linksSource: wiki index · Docs · ▸ diagram -
Community decision map
List each tension and its resolved destination — no orphan decisions.
A Tension → destinationB Decision logC Open questionsSource: plans/conflicts.md · Channels · ▸ diagram -
Direct vouch
One reputation facet visible in the community; the UI never implies a numeric score.
A Vouch explainerB Scope pickerC Reputation facet cardSource: authy levels · Authy · ▸ diagram -
Social-growth plan
Name one safe default per channel before growth is executed in Levels.
A Channel defaultsB Safety rulesC Growth checklistSource: the Plan · Levels, full stage · ▸ diagram