---
title: Framed Autonomy
type: concept
tags: [apm, autonomy, framing, deontic, normative]
sources: ["[[sources/2026-calvanese-agentic-bpm-manifesto]]", "[[sources/2025-calvanese-autonomy-business-process-execution]]"]
created: 2026-04-13
updated: 2026-04-15
---

# Framed Autonomy

The primary mechanism by which an [[concepts/agentic-bpm|APM system]] reconciles agent autonomy with organisational control. A **frame** is a set of rules, restrictions, and regulations that establish boundaries within which one or more agents operate with maximal flexibility.

**Definition 2.4** ([[sources/2026-calvanese-agentic-bpm-manifesto]]): *Framing is a primary mechanism for ensuring process-awareness and goal alignment in an APM system, imposing restrictions on the autonomy of agents through their knowledge and goals.*

## Normative vs operational frames

| Aspect | Normative frame | Operational frame |
|---|---|---|
| Specifies | *What* the agent must / must not do | *How* to act |
| Nature | Deontic (obligations, permissions, prohibitions) | Procedural |
| Example languages | Deontic logic, DECLARE (partially) | BPMN, DECLARE |
| Example | "Do not delete a rejected assignment without notifying the student" | "Retrieve ID → record in DB → send email" |

Classical process specification languages (BPMN, DECLARE) are **operational** — APM-frames focus on the **normative**. A goal is usually implicit in operational specifications; in APM it becomes explicit.

## Levels at which frames may exist
- **Agent type** level
- **Process** level
- **Organisation** level
- Potentially across organisations

## Three blueprint scenarios for framed autonomy
1. One decision-maker, frame on the process.
2. Multiple decision-makers, frames on individual decision-makers.
3. Multiple decision-makers, frame(s) on process behaviour or parts thereof.

## Two aspects of framing
- **Process-Awareness** — agents' actions aim at collective process goals. See [[concepts/process-awareness]].
- **Goal-Alignment** — rules of engagement, hierarchies/coalitions, role assignment, segregation of duties.

## Deepening in Calvanese et al. 2025
[[sources/2025-calvanese-autonomy-business-process-execution]] sharpens the framing argument by calling for **first-class goal + [[concepts/normative-frame|normative-frame]] abstractions** in BPM — arguing that BPMN (imperative) and DECLARE (declarative but still operational) both lack native deontic expressivity. The paper details the three blueprint scenarios with centralized vs distributed intelligence implications and lists three practical challenges (agent notion, frame elicitation/specification, real-data operationalization).

## As a redesign heuristic
Framed autonomy is the **B1 "Frame-first design"** entry in the agentic-era reinterpretation of the Reijers & Liman Mansar (2005) catalogue — see [[syntheses/ai-agent-redesign-heuristics-2026]]. It is the meta-heuristic that subsumes empowerment (#22) and control addition (#23): both become "what does the frame oblige? what does the frame permit?".

## Related
[[concepts/agentic-bpm]] · [[concepts/normative-frame]] · [[concepts/process-awareness]] · [[concepts/self-modification]] · [[frameworks/bdi-agents]] · [[concepts/bpr-heuristics]] · [[syntheses/ai-agent-redesign-heuristics-2026]]