PÓLYAGuides

Guide 01 · CASE BOUNDARY

CONTRACT REVIEW · TEST_ONLYReview-candidate contract and local fixture evidence only · no distributed SDK, operational API, publisher parity, or decision authority

Define the question and the case owner.

A DecisionCase records the review of one question. Set its tenant, scope, version, and owner, and retain a history of changes.

01

What a DecisionCase records

  • Schema and case ID
  • tenantId and exact scope
  • version and prior version
  • owner and current mutation actor
  • createdAt, updatedAt, and current status
02

Scope is the review boundary, not the conclusion

Scope states the subject, time, organization, policy boundary, and decision question under review. If the boundary changes, create a new version or separate case instead of silently reusing the old one.

  1. 01
    State one review question

    Write a question for human review, not an action command.

  2. 02
    Record inclusion and exclusion

    Name the subject, period, approved evidence, and explicit exclusions.

  3. 03
    Assign accountability

    Keep the case owner separate from the actor recording each mutation.

  4. 04
    Define the next-version trigger

    State which evidence, dissent, or assumption change reopens review.

03

Stop before persistence when bindings differ

  • BINDING_CASE_VERSION_MISMATCH
  • REFERENCE_SCOPE_MISMATCH
  • UNKNOWN_FIELD
  • SCHEMA_VERSION_UNSUPPORTED