Stories are framed around who holds leverage, how it is used, and where the cost lands.
About the project
A public-interest reporting project built to make power easier to follow.
NOLIGARCHY.US tracks corruption, capture, manipulation, and public impact. The job is to make systems of influence legible without burying the reader in platform noise or route confusion.
Issue lenses keep coverage connected after the news cycle moves on.
The public site stays simple because follow and support paths stay visible and direct.
A professional publishing system wrapped in a public-interest newsroom.
The operating model is designed to keep the editorial signal accountable from intake to publication: broad source discovery, structured analysis, site-native article context, and disciplined distribution back to the canonical Noligarchy page.
01
Source intelligence
RSS, search monitors, state-level feeds, and targeted issue queries identify candidate stories.
02
Editorial scoring
Signals are screened for power, mechanism, public cost, source quality, and civic relevance.
03
Noligarchy article
Accepted stories become site-native coverage with lens routing, context, metadata, and source links.
04
Distribution layer
Platform-specific posts drive readers back to the Noligarchy article instead of leaking attention away.
15 minMonitor cadence
4Core social channels
1Canonical public article
The site should clarify the next move in three steps.
- 1Start with a live story or lens.
Use the homepage, coverage map, or search when you need the reporting itself first.
- 2Widen the frame through the parent issue.
The lens system groups recurring pressure points so a single story stays connected to a larger pattern.
- 3Use public routes for the next move.
Links, contact, follow, and support stay in the shell instead of hiding behind an admin layer.
Reader support keeps the public site cleaner.
Support and follow paths stay visible because the project is built around direct public trust rather than ad inventory or platform-shaped churn. That keeps the reporting and route hierarchy aligned.
Three routes, three jobs.
The about page should end by pointing back into the live system, not by extending the essay.
Browse the coverage map
Open the issue lanes and move directly into current reporting.
Browse coverageStay close on Substack
Use the newsletter and archive when the next step is continuity between site visits.
SubscribeUse the public handoff
Contact and links routes keep tips, corrections, and collaboration notes in the open public system.
Get in touch