Changing governance policies is admin-only. Members can view them.
Policies
Policies come in two types:- Approval policies — “When approval is needed.” Decide which kinds of work require a human to approve before Corunner acts.
- Compliance policies — “Safety requirements.” Decide which kinds of work Corunner must never do, regardless of confidence.
Confidence bands
bands uses three percentage thresholds:
recommendMin— below this, Corunner blocks (does not act, does not ask).approvalMin— betweenrecommendMinand this value, Corunner asks for approval.autoMin— betweenapprovalMinand this value, Corunner approves the action itself (still visible in the audit trail). At or aboveautoMin, Corunner acts automatically.
block below 40%; ask 40-70%; approve 70-90%; auto at 90%+ from these values.
Governed Decisions
A history of every decision that passed through a policy: what Corunner considered, which rule matched, and what it did. Use this tab to audit specific decisions and to spot categories where policies are firing more than expected.Calibration
Tuning tools for the confidence bands. If Corunner is asking for approval too often on high-confidence work, or acting too aggressively at the edges, calibrate the thresholds here.Related
Approvals in chat
Where the “ask” side of policies plays out.
Approvals history
Read-only history of every approval request.