> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/governance/human-boundaries-and-operational-ownership.md).

# Human boundaries and operational ownership

Decide where people remain accountable in an automated operation and who owns recurring exceptions.

Automation does not remove process ownership.

The process owner remains responsible for deciding what Lleverage may handle routinely, what requires human judgement and what evidence is needed when a person is called in.

## Define the human boundaries deliberately

A configured Workflow can create a Request when it needs a decision or missing input. Those boundaries should reflect real authority or judgement, not uncertainty that nobody has resolved.

For each recurring handoff, know:

* why a person is needed;
* who is allowed to decide;
* what context they need;
* what happens after they respond;
* whether repeated handoffs indicate a missing rule, data source or system capability.

Agent questions inside a foreground session are separate from Workflow-created Request Inbox items.

## Own the exceptions, not only the happy path

A process owner should periodically review what reaches people, what fails and what operators correct manually. The goal is not necessarily to eliminate every exception. It is to know which exceptions are intentional and which ones reveal work that should be improved.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lleverage.ai/administer-and-govern/governance/human-boundaries-and-operational-ownership.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.