A digital twin of American governance
A federated network whose architecture mirrors the hierarchical structure of American democratic governance — federal, state, county, municipal. The data lives where the governance lives.
Structural isomorphism, not a design choice
Centralized civic platforms try to model fifty states, three thousand counties, and tens of thousands of municipalities from a single remote team. The data heterogeneity defeats them. Local civic records are not standardized across jurisdictions — ordinances, council minutes, local filings, and ballot measure records vary in format, schedule, and publication discipline.
Maintaining quality coverage without local operators is the same problem that defeated centralized encyclopedias before Wikipedia. Opus Populi's answer is structural: the architecture mirrors the governance. Local knowledge does not need to scale through a remote team — it scales through the operators who already live in the jurisdictions they serve.
The four-tier hierarchy
Federal edge
Shared infrastructure
FEC, Congress.gov
A single shared layer no one owns. One ingestion job, one auditable source of truth, fifty redundant pipelines eliminated.
State node
State operator
State legislature, state campaign finance (e.g., Cal-Access)
Owns the state's legislative and campaign finance corpus. Scrapes county data until a county operator delegates.
County node
County operator
County supervisors, ordinances, local committees
Registers with the parent state node, receives certification, and progressively takes over county data ingestion.
Municipal node
Municipal operator
City council, city codes, local meetings
Optional fourth tier for high-density cities. Lowest entry cost; highest local-market specificity.
The federal edge cache is not a node anyone owns. A single shared infrastructure layer ingests Congress.gov and FEC data, and all state nodes draw from it — eliminating fifty redundant federal pipelines and creating a single auditable source of truth for federal data.
Progressive decentralization
The architecture is designed to start centralized and decentralize progressively — solving the cold-start problem that defeats most federated network designs. Every node is useful from day one because it has access to federal and state data regardless of whether any lower-tier nodes exist. Network effects are additive, not prerequisite.
Phase 1
State node bootstraps
The state operator scrapes all state legislative, campaign finance, and county data. Every county in the state is covered from day one — no county operator required.
Phase 2
County operator onboards
A county operator registers with the parent state node, completes certification, and receives a delegation handshake. The state node maintains a warm cache for graceful fallback.
Phase 3
State node delegates
The state node stops actively scraping that county's data and routes county FIPS queries to the new county node. User experience is uninterrupted — degraded county coverage shows stale cached data, not errors.
FIPS-aware routing at the state node detects each user's county and routes accordingly. If no county node exists for a given FIPS code, the state node serves county data from its warm cache. The handoff is invisible to the user.
Network effects that align with the mission
Most platforms build network effects through surveillance capitalism. The civic mission rules that out. Opus Populi's network effects are stronger because they align with the mission: collective action produces public goods that benefit everyone, including newcomers.
Jurisdictional coverage
More certified operators means more of the country covered, which makes the platform more useful to more people. Each new node adds local document ingestion, local RAG context, and geographic resilience.
Civic intelligence compounding
Every petition, ordinance, ballot measure, and legislative record added to a regional node improves the analysis layer for all users of that node — without any individual being tracked. A pure public-goods network effect.
Operator reputation
Cryptographic provenance, certified-only subdomains, and signed node registration create a reputation network where trust is earned at the operator level — not surveilled at the user level. Certification becomes a meaningful civic credential as the network grows.
Cross-jurisdictional pattern intelligence
With sufficient geographic coverage, the network can identify when model legislation appears in multiple states simultaneously, when a petition campaign follows known astroturfing patterns, or when donor networks span jurisdictions in ways invisible to local observers. This intelligence only exists at scale — and no centralized competitor can replicate it.
Benefits for operators
Shared identity
Optional *.opuspopuli.org subdomain for your community
Collective improvements
What one community builds, all communities gain
Mutual support
Learn from and help other communities doing the same work
Complete sovereignty
Full control over your data, infrastructure, and governance
How the network stays honest
A federated network is only as trustworthy as its weakest node. Here's how we solve the 'one bad apple' problem.
Regions control which facts are available — their local data sources, their civic records, their meeting schedules. But no region can control how facts are interpreted. The analysis methodology is uniform across every node in the network. We continuously test analysis quality across the network — if a node's output diverges from the expected baseline, it's flagged for investigation. See the full trust architecture for how each layer works, or read about how privacy is built into the architecture.
Prompt lock
Every node receives analysis prompts from a dedicated prompt service with HMAC-authenticated requests. Nodes cannot modify, override, or inject their own prompts — ensuring identical analytical methodology across the entire network.
Cryptographic verification
Every prompt is hashed at the source. Nodes verify authenticity on receipt. Auditors can verify any analysis was produced with a certified, unmodified prompt. Replay protection prevents request manipulation.
Canary documents
Reference civic documents with known-correct baselines are processed through all nodes on a regular schedule. Output is compared for drift, bias, and manipulation. Divergent nodes are quarantined for investigation.
Node certification
Nodes register, receive expiring credentials, and maintain certification through ongoing compliance. The prompt service tracks node status, supports key rotation, and maintains a complete audit log. Non-compliant nodes can be suspended and re-certified after remediation.
The trust equation
Open source code (verifiable) + Consistent prompts (uniform) + Cryptographic attestation (tamper-proof) + Public-domain data (auditable) = Trustworthy analysis at scale
Network rules are published in NETWORK.md and NETWORK-TERMS.md. Member requirements, data ownership, and termination rights are all documented and enforceable.
Nodes
california.opuspopuli.org Community sovereignty
Being part of the network means gaining support — not giving up control.
Your data
Stays where you decide, always
Your customizations
Shape it for your community's needs
Your infrastructure
Run it where you want
Your governance
Your community makes the decisions