Safety and Control

April 2, 2026 · View on GitHub

Placeholder — This document will contain the full safety and control reference. For now, see the relevant sections in architecture-reference.md.

Overview

AF is designed with safety as a structural property, not an afterthought. Every operation is auditable, reversible, and opt-in by default.

Safety Properties

PropertyImplementation
Dry-run by defaultReconciliation reports drift without writing unless --write is specified
Echo suppressionAST writes trigger file saves that re-trigger the watcher; the echo guard cache suppresses duplicate operations
Rollback previewsDestructive changes show a preview before execution
Audit trailEvery operation produces artifacts in design-materializations/; the server persists audit logs
CI gatesDrift thresholds are enforced in CI via af ci --strict
Read-only adaptersExternal integrations use default-deny tool policies; AF is the only mutation authority
Deterministic precedenceoverride > marker > ast > code — same inputs always produce the same outputs

Control Surfaces

  • Policy profilesdesigner-first, code-first, balanced, strict-review control how conflicts are resolved
  • af.config.json — Central configuration with env var overrides
  • design-overrides.json — Captured design overrides that take highest precedence
  • CI integration — GitHub Actions matrix workflows for automated drift checks

Detailed Reference

The full safety model, including echo suppression mechanics, rollback preview semantics, and CI gate configuration, is documented in architecture-reference.md.