Reality Fit

Position

This page explains the current VCDesign authority. Authority remains core/core.yaml, core/policies.yaml, and core/metrics.yaml. This page is an explanatory guide, not a fourth authority.

Four Loops

• Physical Loop: execution, stability, continuous dynamics
• Semantic Loop: interpretation, delta-to-meaning conversion, discontinuous inference
• Value Loop: objectives, constraints, optimization direction
• Responsibility Loop: final decision, halt, accountability

VCDesign treats adaptation as coordination across these loops under explicit responsibility.

This is not an independent control model beside PDΔA. It is a decomposition of PDΔA across time scales and responsibilities.

Time Scale

The loops operate on different clocks. Fast execution loops must not silently rewrite slower value or responsibility loops.

LLM Placement

LLMs belong primarily in the Semantic Loop. They may interpret and recommend, but they must not directly control the Physical Loop, set value objectives autonomously, or hold final authority.

Boundary and Haltability

Any crossing between discontinuous inference and continuous control requires a safety gate, traceability, human override, and a halt path.

Boundaries are not only transformation layers. They are explicit points where responsibility must be reassigned or reaffirmed.

Growth

Growth is not defined as model capability increase alone. It is defined as improved operational fit under responsibility constraints.

Authority Mapping

• Core: loop separation, temporal separation, boundary mediation
• Policies: LLM placement constraints, safety gates, haltability
• Metrics: delta quality, alignment quality, consistency, halt readiness