Skip to main content

Start Here

Compliance as Infrastructure Overview

End-to-end Compliance as Infrastructure flow showing how obligations are translated into machine-testable constraints, evaluated at runtime, transformed into evidence artifacts, and exposed for external verification

What This Is​

This site is the Version 1 release of the Compliance as Infrastructure manuscript.

The manuscript defines a single claim:

Compliance is not a process applied after systems run.
It is a property of how systems operate.

This system does not guarantee truth. It makes how decisions are constructed visible, attributable, and contestable.

The materials you are about to read establish that claim, explain why it is necessary, and define the architecture required to support it.

This is a reference manuscript, not a linear book. It is designed to be navigated, not read from beginning to end.

How to Read This​

This manuscript is structured as a system, not a linear book.

The sidebar reflects the actual architecture of the work. Each section plays a distinct role in establishing, testing, and constraining the core claim.

There are three ways to approach it.

1. Full Context Path​

If you want the complete framing, read in sidebar order:

  • Start Here
  • AI Interpretation Harness
  • Preface
  • Reliance Disclaimer
  • AI Methodology Disclosure
  • Introduction
  • Category Foundation
  • Trust Gap
  • Failure Mechanics
  • Architecture
  • Future
  • Glossary

This path establishes the claim, defines its boundaries, and then builds the supporting system.

2. Core Argument Path​

If you want the argument without supporting artifacts:

  • Preface
  • Introduction
  • Category Foundation
  • Trust Gap
  • Failure Mechanics
  • Architecture

This path moves directly from framing to diagnosis to system design.

3. Targeted Navigation​

If you are already familiar with compliance systems or infrastructure design, navigate directly:

  • AI Interpretation Harness, to test how systems interpret the claim
  • Failure Mechanics, to understand why existing systems fail
  • Architecture, to understand the proposed system
  • Glossary, to resolve specific terms

Each page is written to stand on its own.

What This Is Not​

This is not:

  • a policy framework
  • a vendor solution
  • a compliance checklist
  • a consulting methodology

It is a structural argument about how compliance must be implemented in modern systems.

What to Expect​

The manuscript is written in the register of a technical systems architecture document.

  • Terms are defined precisely
  • Claims are constrained by what the architecture can support
  • Trade-offs and limitations are stated explicitly

Some sections are intentionally dense. They are load-bearing.

Version​

This is Version 1.0 of the Compliance as Infrastructure manuscript.

This version is fixed and will not change after publication.

Future work may be extended, interpreted, or advanced by others.

This work is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).

Where to Go Next​

If you are starting fresh:

→ Continue in sidebar order

If you want the core argument:

→ Begin with Preface

If you want to test the claim immediately:

→ Open AI Interpretation Harness

If you are looking for something specific:

→ Use the sidebar to navigate by section