Skip to content
Ricky Jones edited this page Mar 3, 2026 · 1 revision

constraint-workshop Wiki

Overview

Small, deterministic control primitives for software systems. Testable, auditable bricks.

LV/Tech Runtime Governance Geometry (v0.1)

The foundational geometry spec defines how systems bind authority prior to irreversible execution.

Key artefacts

Document Purpose
Canonical Spec State-space regions, gates, commit boundary
Mermaid Diagram Visual flow of the geometry
Test Matrix NON_EXEC verification rows
Builder Handoff AI assistant instructions

Core concepts

  • Regions A–E: State-space zones from unbounded to committed
  • Gates G1–G4: Deterministic transitions between regions
  • Commit boundary: One-way, irreversible crossing point
  • Fail-closed: Undefined states always resolve to safe default
  • Evidence trail: Every gate crossing must produce auditable evidence

Roadmap

See Milestone: v0.1 for tracked issues.

Working with AI assistants

  1. Point the assistant at the geometry spec
  2. Ask it to propose docs, diagrams, and test matrices first
  3. Only after HUMAN review, request executable code

See HANDOFF_PERPLEXITY.md for full builder instructions.