Protective Computing Canon (Zenodo)
Theory → operations → measurement
A layered canon for systems built under instability: foundational theory, operational translation, and measurement & audit.
Use this dossier as supporting evidence for the service work on this site: problem, constraints, proof surface, and outputs.
Disambiguation: this is a protective computing framework, not the political science Overton Window concept.
Teams building for real-world vulnerability (coercion risk, low trust, degraded operations) often inherit security language that is compliance-shaped or too abstract to implement.
The canon exists to make protective system-building legible and testable: define the theory, translate it into operator reality, then measure outcomes with an audit-ready rubric.
- •Layered design: each layer stands alone, but composes cleanly.
- •Falsifiability: claims must be testable (not narrative-only).
- •Operational realism: the guidance must survive degraded conditions and incident pressure.
- •Citation-first: primary artifacts are DOI-backed records; links are stable and reviewable.
Layer 1 (Overton Framework): defines protective computing as an engineered discipline, with explicit threat boundaries and legitimacy requirements.
Layer 2 (Field Guide): translates the theory into field-usable practices and decision patterns under constraint.
Layer 3 (PLS rubric): turns the discipline into audit-ready measurement so systems can be assessed without hand-waving.
- •3 DOI-pinned layers published and citable (framework, field guide, PLS rubric).
- •A single, layered citation surface suitable for external review and reference.
- •A defensible path from principles → practices → measurement, reducing security theater.
- •A reusable audit rubric (PLS) that makes protective claims verifiable.