Docs navigation

User Docs

Region Proposals

How imported selection artifacts become ranked proposals and approved regions.

Region proposals help reviewers move from structured constraints to a reviewed, approved region. The public workflow imports selection artifacts, ranks candidate proposals, and records a human approval before any scope verdict is treated as authoritative.

Key terms: selection artifact is a precomputed JSON document; allowed and immutable are change classes that constrain what the approved region can modify. See the glossary for Candidate Proposal, Approved Region, Scope, and Verdict, or the full guide.

Workflow

  1. Confirm structured constraints such as allowed classes, immutable classes, and bounds using valence-domains validate-refinement-constraints.
  2. Import one or more precomputed selection artifacts using valence-domains propose-region.
  3. Review ranked candidate proposals with their warnings and evidence.
  4. Approve one proposal with a human actor and reason using valence-domains approve-region-proposal.
  5. Use the approved region for deterministic scope review.

What survives as authority

Candidate proposals are advisory. An approved region is the artifact that crosses the authority boundary and can be used for enforcement-grade scope verdicts.

Generation

For an offline, runnable walkthrough of the complete workflow, see intent_guided_region_proposal.ipynb on GitHub.

Diagram: structured constraints validated, selection artifacts imported, ranked candidate proposals generated with warnings and evidence, human approval gate (actor and reason required), approved region produced (authoritative), scope verdict computed; separate owner-only generation path branches off with 'fails closed when engine absent' label.

See Trust, Provenance & Authority Boundaries for the full authority model behind proposals and approved regions.