| status | updated | |||
|---|---|---|---|---|
| version | 1.0 | |||
| author | AnathemaOfficial | |||
| last_updated | 2026-04-15 | |||
| tags |
|
Version: 1.0
Last Updated: 2026-01-24
Status: Updated
This is the central index for all Systemic Fire Law (SYF) and Anathema documentation.
The documents are organized by topic and numbered for recommended reading order.
docs/
├── 1_foundational/ # Core concepts (Start here)
├── 2_security/ # Security model and analysis
├── 3_implementation/ # Implementation guidelines
├── 4_product-and-operational/ # Product specifications
├── 5_legal/ # Legal documents and boundaries
├── 6_audit-and-status/ # Audit status and verification
├── 7_education/ # Educational materials
└── templates/ # Document templates
- SYF Foundation — The problem and solution
- R Invariant — What R is and isn't
- SYF-Anathema Bridge — From law to body (stub)
- Security Model — Threat model and guarantees
- Comparison with Classic Approaches — SYF vs traditional security (stub)
- Why Detection Fails — Why SYF doesn't detect (stub)
- Breaker Q&A — Anathema Breaker questions (stub)
- R Spec Template — How to apply R
- R FAQ — Common developer questions (stub)
- R Failure Modes — Failure analysis (stub)
- SLIME/SAFA Implementation Stack — Full stack from SLIME-Core to SAFA production adapter
- SYF Gate Product Spec — Flagship product (stub)
- SYF Shield Product Spec — Shield product (stub)
- Anathema Breaker Spec — Central organ (stub)
- Client Pilot Template — Pilot engagement (stub)
- Compliance Checklist — Self-audit tool (stub)
- Manifest — Archive manifest
- Boundary of Liability — Liability separation (reference to PDF)
- Terms of Non-Use — Forbidden uses (reference to PDF)
- Invariants — Complete invariant list I-1 to I-10 (reference to PDF)
- Audit Status — Document completion status
- Hashes — Cryptographic verification hashes
- Tordeur Audit Report — Full adversarial security audit results (2026-04-15)
- Anathema Soft Explained — Human explanation for CTOs/Engineers
| Principle | Description |
|---|---|
| Safety by Impossibility | Actions are limited, not monitored |
| R is a Sensor | Read-only, non-accumulative, present-only |
| Fail-Closed | Unknown state → no action |
| No Detection | Assumes breach, limits damage |
| No Governance | No admin, no override, no bypass |
SYF does not try to stop attackers from entering.
It makes damage physically impossible, even if they are already inside.
See DOCS_CONTRIBUTING.md for guidelines on contributing to this documentation.
- SEALED: Canonical, hash-verified, immutable
- CANONICAL: Official but may receive non-substantive updates
- UPDATED: Recently modified
- DRAFT: Work in progress
For root README and quick links, see /README.md