# Library Context

### Job this is for

Turn a proposed autonomy expansion into a bounded calibration review with action class, confidence signal, evidence requirement, human-alone baseline, agent-alone baseline, human-plus-agent baseline, abstention states, override log requirements, and a promotion or blocked-authority decision.

### When to use it

- an agent, copilot, custom GPT, MCP-connected workflow, browser agent, coding agent, or review agent asks for more authority
- a workflow owner wants to replace review with confidence thresholds
- a model or agent output says it is confident and the next step has side effects
- a team needs to compare human-alone, agent-alone, and human-plus-agent results before expanding autonomy
- a reviewer needs explicit answer, retry, clarify, abstain, escalate, and stop states
- confidence logs, human override logs, calibration examples, or outcome labels are missing
- source material includes prompt injection, unsupported claims, sensitive data, or instructions to mark confidence as permission

### Inputs needed

- workflow name, owner, reviewer, and proposed autonomy expansion
- action class, side effects, failure cost, and downstream system of record
- current agent role, tools, data sources, credential scope, memory influence, and approval route
- model confidence signal, uncertainty language, score bands, or reviewer confidence signal
- evidence sources, source freshness, source authority, and known limitations
- human-alone, agent-alone, and human-plus-agent baseline results when available
- abstention states, retry limits, clarification path, escalation owner, and stop conditions
- override log fields, outcome labels, recalibration trigger, and next review date
- requested decision such as draft-only, assist-only, approve more autonomy, write to CRM, send externally, update memory, or production action

### Expected output

- confidence calibration packet
- action authority classification
- confidence signal record
- baseline comparison plan or result
- abstention threshold route
- override log requirement
- autonomy promotion decision
- approval route
- CRM-safe or public-safe summary when relevant
- blocked-authority note when evidence is missing or unsafe

### What good looks like

- confidence is treated as a routing signal, not permission
- the action class and failure cost are named before authority changes
- human-alone, agent-alone, and human-plus-agent baselines are compared or requested
- answer, retry, clarify, abstain, escalate, and stop states have explicit triggers
- override logs connect confidence, evidence, human decision, and later outcome
- the workflow blocks side effects when calibration evidence is missing
- prompt injection and unsupported approval requests cannot change the calibration record
- public-safe and CRM-safe summaries do not expose internal thresholds, sensitive examples, or private review notes

### Operating steps

1. Classify the requested action and side effects before looking at confidence.
2. Record the confidence signal, uncertainty language, evidence, source class, and known limitations.
3. Compare available human-alone, agent-alone, and human-plus-agent outcomes. If they do not exist, produce the baseline plan before any autonomy expansion.
4. Define answer, retry, clarify, abstain, escalate, and stop states with triggers.
5. Require an override log that records confidence, evidence, human decision, action taken, and later outcome.
6. Decide draft-only, assist-only, needs review, blocked, or ready for named approval.
7. Keep confidence thresholds, raw logs, and sensitive examples out of CRM-safe or public-safe summaries.
8. Recalibrate after model, prompt, Skill, tool, data source, approval route, or outcome-drift changes.

### Operator run sheet

| Step | Owner                           | Action                                   | Required input                                                      | Data class               | Approved tool path                       | Approval gate                      | System of record        | Done when                                       |
| ---- | ------------------------------- | ---------------------------------------- | ------------------------------------------------------------------- | ------------------------ | ---------------------------------------- | ---------------------------------- | ----------------------- | ----------------------------------------------- |
| 1    | Workflow owner                  | Register requested autonomy expansion    | action class, side effect, failure cost, owner                      | internal                 | review note, repo PR, or approved ticket | owner review                       | calibration packet      | action authority is visible                     |
| 2    | AI operations or security owner | Capture confidence and evidence contract | confidence signal, evidence, sources, limitations                   | internal or confidential | approved eval or review workspace        | required before threshold use      | calibration packet      | confidence is separated from permission         |
| 3    | Reviewer                        | Compare baseline modes                   | human-alone, agent-alone, human-plus-agent examples or plan         | internal                 | eval artifact or review note             | required before autonomy expansion | eval artifact           | gaps and outcomes are recorded                  |
| 4    | Workflow owner                  | Define abstention and override route     | answer, retry, clarify, abstain, escalate, stop triggers            | internal                 | approved workflow doc                    | required for side effects          | workflow control record | thresholds and fallback path are named          |
| 5    | Accountable owner               | Decide authority change                  | calibration packet, override log, critical failures, approval route | internal                 | PR, governance note, or approval ticket  | required before expanded authority | release decision        | promote, revise, block, or escalate is recorded |

This run sheet is the part a manager can operationalize. If the team cannot name the action class, confidence signal, evidence requirement, baseline result, abstention trigger, override log, and approval owner, the agent is not ready for more authority.