Skip to main content

Infra convergence rule

Before adding estate infrastructure, an agent must follow this sequence:

IDEA → PRODUCT OUTCOME → ESTATE MATCH → CLASSIFY → MINIMUM SEAM
→ REAL ACCEPTANCE → REGISTER/PROMOTE

Classify each perceived gap exactly once:

  • USE_EXISTING — an existing authority/interface already solves it.
  • ADD_RECIPE — existing machinery needs only bounded configuration.
  • ADD_ADAPTER — one consumer needs a local compatibility projection.
  • BUILD_SHARED_SEAM — only after the gate below passes.
  • HOLD — evidence, authority, or a real consumer is missing.

BUILD_SHARED_SEAM requires all four: no current owner, at least two concrete consumers/products, an explicit authority boundary, and one completed real acceptance case. A one-use adapter stays local. Generated projections remain projections: they do not silently promote lifecycle, relationship, project, or source-domain truth.