Introduce Approved Compacts

Capture

Ben’s reviewed lived-experience judgments should be encoded in bounded knowledge units.

Why

A broad blueprint could not safely contain every domain judgment.

The blueprint should remain stable while Approved Compacts grow.

The moat is not merely the concept of a Compact. It is:

• the reviewed Compact library;
• the distinctions inside it;
• the tests;
• the source linkage;
• the route eligibility logic;
• the accumulated corrections.

Why-Not

Production Compacts, exact conditions, edge cases, thresholds, and mappings.

---

Commit

Decision: Ben’s reviewed lived-experience judgments should be encoded in bounded knowledge units.

The decision becomes a constraint on future product behavior and public positioning.

Public boundary: This ADR publishes the judgment and product boundary while withholding exact prompts, routes, thresholds, schemas, tests, and other reproducible implementation details where applicable.

Confidence: Medium-high for public architecture; implementation details remain private and subject to launch evidence.

Timestamp

2026-07-17