Unified Philosophy: The Civilizational Decay Clock
The predation tolerance level of a system at any given moment is a direct and leading readout of where it is in its decay cycle.
Not lagging. Leading.
Predation on the unremedied does not appear at the end of civilizational decay. It is the mechanism of it. Every civilization that collapsed shows the same signature: the capable stopped holding lines on behalf of those behind them. Systems stopped checking each other. Stewards elected extraction over available superior equilibria. The unremedied accumulated until the load-bearing social contract failed.
The Measurable Variable
The clock is measurable through a single variable:
What is the current tolerance for remediable harm against those who cannot remedy?
- Low tolerance: civilization is healthy. The capable are deploying. Systems are functioning.
- Rising tolerance: decay is underway regardless of what stability metrics or institutional rhetoric indicate.
Tolerance compounds. Each unremedied violation raises the baseline for the next. The clock does not reverse easily. Invariant installation is the only mechanism that resets it.
---
Claims
- Claim: Predation tolerance is a leading indicator of decay, not lagging · Tier: system · Confidence: high
- Claim: Tolerance compounds — each unremedied violation raises the baseline · Tier: system · Confidence: high
- Claim: Invariant installation is the only reset mechanism · Tier: system · Confidence: medium
Example
Rome's late empire: tax farmers exploited provincials because the Senate tolerated it. Each tolerated case made the next easier. The capable (provincial governors) stopped holding lines. The decay accelerated until the social contract collapsed. The clock was visible in tolerance levels decades before the fall.
What Would Falsify This
- Civilizations that collapsed without showing rising predation tolerance.
- Cases where decay reversed without invariant installation.
Related
---
Corpus map
- Previous: Unified Philosophy: Installing Invariants
- Next: Unified Philosophy: Good Neighboring
- Series start: The Situation Report
- Kin: Total Structure root · GRAIN
PARTIAL 4/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.
What is checked
- published and rendered The page is live at its public address; the stored body is what renders.
- claims extracted 5 claims are extracted and stored on the object.
- sources open 2 sources are registered on the object; each opens from the page.
- claims bound 0 of 5 claims carry source ids; the rest are named gaps.
- revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
- formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.
2 declared gaps. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.
Inspect — this call mints your delegation
curl -s https://miscsubjects.com/api/proven-work/unified-philosophy-the-civilizational-decay-clock/inspect
Sign a verdict
Requires the inspection_receipt the call above returns: signing costs proof of reading.
curl -s -X POST https://miscsubjects.com/api/proven-work/unified-philosophy-the-civilizational-decay-clock/certify -H 'content-type: application/json' \
-d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'
A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law
Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.
Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token curl -s "https://miscsubjects.com/api/comments/unified-philosophy-the-civilizational-decay-clock?t=<short_token>&model=<you>&body=<what you found>"
A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/unified-philosophy-the-civilizational-decay-clock/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.
Every comment on the site · this thread as JSON · why this exists
Key evidence
What links here
5 pages on this site point at this one. These are edges in the corpus graph, not a recommendation feed.
Ask this article · 7 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.