Self-defense doctrine · c/o OpenOS
Infrastructure that holds power accountable must be more durable than the power it holds accountable.
The platform's survival is itself a constitutional issue. No single legal attack, deplatforming event, data poisoning campaign, or funding disruption can take it offline.
Legal structure
“Three entities. One mission.”
Three separate legal entities by design — so a successful attack on one does not destroy the others:
- 501(c)(3) nonprofit runs platform operations, the Intelligence Layer, and the public accountability database. Protected as public-interest journalism and civic education.
- 501(c)(4) advocacy arm runs the Legislative Push Engine, Offensive Doctrine tools, and FOIA campaigns. Political activity is legally separated, separately funded, separately governed.
- Open-source foundation holds the codebase, API documentation, and self-hosting guides. Anyone can fork and operate their own instance.
Legal positioning
All Intelligence Layer data comes from public government sources — same legal basis as Westlaw, LexisNexis, OpenSecrets, and ProPublica. Aggregating public records is not defamation. Constitutional grades are documented analysis — same legal protection as law review articles. Offensive tools are legal filings and formal government channels — protected First Amendment petitioning activity under the Noerr-Pennington doctrine.
Data integrity
“No finding ships without provenance”
Every claim the platform publishes is traceable to a primary source document. AI inference without a primary source never ships as a confirmed finding.
Cross-source verification
No finding publishes as "confirmed" without two independent primary sources corroborating. Single-source findings are labeled "unverified — pending confirmation" until corroborated.
Source provenance fingerprinting
Every ingested document receives a cryptographic hash at ingest time. Any subsequent modification to the source document is detected automatically and flagged for human review.
Velocity anomaly detection
Sudden spikes in findings against a single actor, floods of correction requests on established findings, and coordinated submission patterns all trigger automatic review holds.
Adversarial audit
Quarterly red-team exercise where a designated team attempts to manufacture a false finding through the platform's normal intake. Every successful attack is patched before the next quarter.
Infrastructure resilience
“No single point of failure”
No single cloud provider, no single datacenter, no single legal jurisdiction can take the platform offline.
- Federated architecture: any news outlet, civil liberties org, or state agency can run their own instance federated to the main network
- Multi-cloud deployment: AWS, GCP, and Railway instances with automatic failover
- Monthly data mirroring: public accountability database mirrored to the Internet Archive, academic repositories, and partner organizations
- Open API: all public data available to third-party developers, creating a distributed ecosystem that outlives any single instance
Correction protocol
“Permanence + correction”
The platform publishes confirmed findings immediately and permanently. Permanence is a feature — it prevents accountability records from being quietly scrubbed. But permanence without a correction mechanism creates a different problem.
Governing principle: corrections are as visible as the original finding.
A retracted finding is not deleted — it is marked as retracted, the reason is published, and the correction becomes part of the permanent record. The actor's accountability score is recalculated. Citizens who received the original alert receive a correction alert. Nothing disappears. Everything is documented.
Anti-retaliation monitoring
“Retaliation becomes evidence”
When an official with an active accountability finding files a lawsuit against the platform, initiates regulatory action, or attempts to pressure a cloud provider or payment processor, that action is itself published as a finding on the official's accountability profile.
Heading: "Attempted suppression of public accountability record." Stonewalling the platform makes the platform's record stronger, not weaker.
Operator protection
“No operator stands alone”
Platform operators, moderators, and reviewers are personally exposed when officials file retaliatory lawsuits. The self-defense doctrine addresses this directly:
- Legal defense fund covers all operators facing personal suits arising from good-faith platform operations — fixed line item in the 501(c)(3) budget
- Anti-SLAPP protections invoked in every jurisdiction where available
- Amicus support from aligned civil-liberties organizations (EFF, ACLU, Knight First Amendment Institute)
- Personal indemnification for directors, officers, and principal contributors
Constitutional consistency
“The same standard, applied to all”
The Constitutional Grading Engine applies the same standard regardless of party, administration, or political alignment. This is constitutional consistency, not political neutrality.
- The platform does not endorse candidates, parties, or movements
- Any proposed change to the grading algorithm is itself publicly logged and constitutionally evaluated
- Officials who score well are not endorsed — their record is documented
- Officials who score poorly are not condemned — their record is documented
The platform presents. The citizen decides.
Mandate
This is not a product. It is infrastructure.
Apps get shut down. Infrastructure outlasts the people running it. The goal is not to be the best accountability platform on the market today. The goal is to build the accountability platform that exists when our grandchildren need it. Every durability decision flows from that mandate.