PARA

Schemas

Schema reference

Use this section when you want the technical shape behind PARA's public surfaces. These pages curate the `com.para.*` lexicons in watx so the records and views are easier to read in the context of the product.

com.para.post

stable

Primary Para post record with rich text, replies, embeds, flairs, and post type metadata.

recordspostsfeeds

com.para.social.postMeta

experimental

Metadata overlay for Para posts including post type, vote score, and civic classification tags.

postssocialmetadata

com.para.community.defs

experimental

Shared community governance views for moderators, officials, deputies, summaries, and history.

communitiesgovernanceviews

com.para.community.getGovernance

experimental

Governance query for community rosters, summaries, metadata, and edit history.

communitiesgovernancequeries

com.para.actor.defs

experimental

Actor-facing status and profile-stat definitions for influence, contributions, community activity, and public status.

actorsstatusprofiles

com.para.actor.getProfileStats

experimental

Actor query for Para-specific profile statistics and current public status.

actorsqueriesprofiles

com.para.civic.defs

experimental

Indexed civic views for cabildeos, positions, vote totals, and viewer context.

civicgovernanceviews

com.para.civic.getCabildeo

experimental

Detail query for a single indexed cabildeo with aggregate and viewer context fields.

civicqueriescabildeo

com.para.civic.listCabildeos

experimental

List query for indexed cabildeos with filters and pagination.

civicquerieslists

com.para.highlight.defs

experimental

Indexed highlight annotation views for public and private political reading layers.

highlightsreadingviews

com.para.highlight.listHighlights

experimental

List query for indexed highlight annotations with filters and pagination.

highlightsquerieslists

com.para.status

stable

Literal-self status record for the current public status, party, and community label of a Para account.

actorsstatusrecords

Implementation appendix

How the schemas fit the backend

Schema reference is where the technical layer becomes concrete. The notes below connect the records and views to the product surfaces they support.

Product layer

Visible civic product surfaces

The app exposes communities, participation routes, trust settings, and communication tools that should be legible before anyone opens the schema browser.

Protocol layer

watx contracts underneath

Lexicons, records, xrpc methods, service boundaries, and repository semantics describe how those surfaces are stored and moved through the stack.

Reference layer

Docs that connect both views

The public site should bridge product language and protocol language so the docs read like a coherent system rather than disconnected notes.