-3 to +3
policy vote range
PARA turns plural identity, policy votes, RAQ flows, collective agents, and protected participation into a civic product people can actually use.
Read it product-first or protocol-first. The public site now ties the thesis, the visible app surface, and the schema reference into one path.
-3 to +3
policy vote range
#POLICY||
structured political flairs
2nd layer
cross-network civic context
Structured speech
Policies and matters stop dissolving into generic posting and become comparable civic objects.
Guided positioning
Users can locate themselves, refine their stance, and contribute structured political context.
Protected participation
Anonymity, validation, and moderation are treated like infrastructure, not an afterthought.
About
Understand why PARA exists, how democratic friction shapes the product, and why the site is organized around a second political layer.
Open pathTry app
Launch the live PARA experience, request a build link when needed, or use the local runbook when you want full control.
Open pathSchemas
Browse the `com.para.*` reference pages and see how the technical layer maps to the app surface.
Open pathPARA starts from democratic frustration in Mexico, but the product argument is broader: people need a civic layer where disagreement, political identity, and policy preference are more expressive than party labels and more actionable than generic feeds.
Most people can tell you what feels wrong in politics, but very little of that opinion becomes material. PARA starts from the idea that democracy fails when making yourself heard is too slow, too expensive, too opaque, or too socially risky.
PARA began with political-compass memes and Democracy 4 because they make ideology legible. The product thesis is that people should be able to locate themselves, disagree selectively, and vote on policies without buying an entire partisan package.
Collective and individual agents, political search, AI-assisted writing, and anonymity tooling sit on top of Bluesky-derived infrastructure so the differentiated investment can go into cryptography, data, and political intelligence.
Each feature card ties a user-facing behavior to the friction it reduces, so the site feels closer to the actual product and less like a generic social platform pitch.
Problem
Makes political positions visible, comparable, and easier to act on.
PARA starts from a simple premise: democracy stays thin when public opinion is hard to express clearly and hard to turn into civic consequence.
Second layer
Lowers the cost of participation without asking users to abandon their audience.
PARA can link identities, publish across networks, and carry political context wherever public discussion is already happening.
Flairs + voting
Turns generic posting into structured political input.
PARA introduces #POLICY|| and #MATTER| so users can separate policy design from issue attention, then vote with both direction and intensity.
RAQ + communities
Helps people locate themselves politically instead of posting into one undifferentiated crowd.
The RAQ helps users question themselves, place themselves politically, and generate structured data that communities can organize around.
AI + search
Makes the network useful for reading, comparison, moderation, and external tools.
PARA is meant to power more than a feed. Search, clustering, classification, and generation turn civic data into usable product utilities.
Trust + infra
Balances protected participation with public trust.
PARA combines anonymity where freedom of thought needs protection with validation where civic participation needs grounding.
PARA should make sense in both directions. Someone learning the product should find the thesis, surfaces, and trust model fast. Someone evaluating the stack should be able to jump straight into contracts, services, and schema docs without losing the product context.
Browse schema referenceProduct layer
The app exposes communities, participation routes, trust settings, and communication tools that should be legible before anyone opens the schema browser.
Protocol layer
Lexicons, records, xrpc methods, service boundaries, and repository semantics describe how those surfaces are stored and moved through the stack.
Reference layer
The public site should bridge product language and protocol language so the docs read like a coherent system rather than disconnected notes.
Policies and matters can be encoded as dedicated flairs, then voted on quantitatively instead of being reduced to generic posting.
RAQ, intergroup antagonism, and community voting can build a political dataset that keeps personal and collective agents evolving.
Bluesky-derived infrastructure keeps distribution costs lower while cryptographic anonymity and civic intelligence remain the main differentiated investments.
Product framing, code, and backend contracts all stay visible from the homepage, so people can move from narrative to implementation without hitting a dead end.
Website
App
Backend