Requested field change
- Account field
- changed
- Evidence
- attached to request
- Decision
- named review required
Governance and review
Put policy at the artifact boundary.
Route material document changes to named decisions, prevent stale approvals from outrunning exact versions, and retain the evidence behind release.
exact artifact versionHow this surface works
A release decision belongs to exact bytes—not a filename or a chat message.
Version-bound policy
Evaluate rules against the exact document version proposed for release.
Named review
Send material exceptions to an identified role or host-product workflow.
Decision evidence
Retain the policy result, reviewer decision, and released artifact relationship.
Operational sequence
State advances only with evidence.
Every step has an observable input, result, and release consequence.
- 01
Detect the changed boundary
Identify the field, object, page, cell, or package state that requires control.
change - 02
Evaluate policy
Apply the pinned rule set and stop automatic release when a named decision is required.
policy - 03
Record and release
Bind the decision to the version that was actually approved and delivered.
receipt
Availability
Claims follow the registry.
Governance capabilities are disclosed per registered extension; embedded review remains capability-gated.
Inspect current capability evidence