Documentation
# PARA docsThe docs now work as an entry hub instead of a backlog dump. Start with the product story if you
want to understand the civic model, or jump straight into routes, status language, and com.para.* records if you are already evaluating the stack.
Choose your lane
## Start from the question you actually haveHow does the civic model work?
Open How it works for route families such as RAQ, cabildeo, communities, and representatives.
How mature is this?
Use Status to understand what is implemented, partial, experimental, or still thesis-only.
What are the contracts?
Jump into Schemas once you want records, queries, and backend framing.
How the docs are organized
## The reference is arranged around real product surfacesPARA is not one feed and not one profile. The docs reflect that by centering product surfaces, operational pages, and protocol reference separately, while keeping them close enough to read as one system.
Core civic surfaces
## The product already has a legible political shapeThe key documentation move is simple: PARA should read like a civic operating model with clear route families, not like a generic social app with political adjectives on top.
Operational pages
## Trust, access, and maturity are part of the docs experienceTrust and safety
Identity, moderation, verification, privacy, saved content, and account control are documented outside the core reference so they stay easy to find.
Try app
The current shared host, GitHub entry point, and local runbook are centralized in one place instead of being scattered across pages.
Status language
The docs explicitly distinguish implemented behavior from partial, experimental, and thesis-only areas.
Glossary
Key vocabulary such as RAQ, cabildeo, matters, flairs, and civic intelligence stays canonical across the site.
Read next
- Read the Getting started page
- Read How it works
- Read the Product page
- Read the Trust and safety page
- Read the Try app page
- Read the Status guide
- Browse the schema reference