Resolution Protocol (RP)

RP is one of the four entry points of the VCDesign ecosystem. It is a pre-decision promotion gate that prevents accidental elevation of Meaning into the Responsible Domain.

RP is not governance and not a workflow. RP does not automate judgment or authorize decisions. It only enforces promotion conditions before responsibility is assigned.

What RP is

RP is a promotion interlock. It is evaluated before any Meaning is promoted into Responsibility, especially when:

  • AI-generated candidates exist
  • evidence is incomplete or implicit
  • ownership or accountability is unclear

If RP conditions are not satisfied, the system must fail safe.

What RP is not

RP defines constraints, not steps. It is not:

  • a runbook or operational procedure
  • a mechanism that delegates judgment
  • a way for AI to finalize decisions
  • a replacement for human responsibility

Where RP sits in BOA

BOA separates artifacts into:

  • Fact — immutable observations
  • Meaning — interpretation / hypothesis
  • Responsibility — actions and commitments
Meaning → Responsibility (promotion)

RP governs this promotion boundary.
It makes the boundary explicit and enforceable.

Fail-safe by design

RP defaults to fail-safe:

  • Default outcome: deny promotion
  • If conditions are not met: quarantine or reject
  • AI may propose candidates, but cannot finalize resolution

Specification

RP is defined in the VCDesign Core:

→ vcdesign_core.yaml

If you implement VCDesign, treat RP as a mandatory gate for any promotion into the Responsible Domain.

Position in the ecosystem

IDG blocks ambiguity before it enters. RP governs promotion. BOA constructs boundaries. VCD defines why boundaries matter.