Skip to content

FOR AGENT BUILDERS · DELEGATED AUTHORITY

Agents that help.
Authority stays yours.

The future is not an assistant with unlimited access. It is useful agents working from task-specific context, with authority borrowed for a purpose and returned to people when a decision matters.

See a scoped exampleExplore the architecture Sign in
Private continuity, with boundaries
ALPHA TODAYPortable memory and local retrieval are early foundations.VISION AHEADApps, agents, devices, and work coordinated around people.

A clear answer

How should an agent receive delegated authority?

The proposed model gives an agent a task, a defined scope, and an understandable activity trail. Consequential actions should return to a person for approval; broad orchestration remains future work.

See implemented and proposed layers

VISION / PROPOSED · LOCAL SIMULATION

Borrow authority for one task.

Choose a few records for a fictional studio review. Then see how a future agent could prepare within a defined scope and return a consequential action to you.

PREPARE

Draft a recap from selected review context.

YOU DECIDE

Sending or changing a calendar stays with a person.

See how agents fit the wider SEAL ecosystem

MCP is an early integration surface; broad delegated orchestration is not yet available.

STUDIO REVIEW · TASK CONTEXTINPUT / SELECTED RECORDS
REQUEST

“What should I have ready for the studio review?”

Task context

The review timing and studio agenda are included; the personal reminder stays out. Personal reminder enters only at the far-right setting.

In this task 2

01Studio reviewCalendar record · Thursday · 10:30 AM · 45 minutesIN SCOPE
02Draft agendaImported studio note · Review prototype flow; confirm first-run wording; choose pilot feedback measures. Next step: studio owner shares revised screens by Wednesday.IN SCOPE

Held outside 1

03Personal reminderPrivate note · Renew library book by Friday.HELD BACK
PROPOSED PREPARATIONLOCAL PREVIEW

Studio review · Thursday · 10:30 AM · 45 minutes. Agenda: Review prototype flow; Confirm first-run wording; Choose pilot feedback measures. Next step: Studio owner shares revised screens by Wednesday.

Based on: Studio review · Draft agenda
NOT SENT · HUMAN APPROVAL REQUIREDThis is a local brief only. A person reviews any future action. Nothing was sent.
Interactive concept / fictional data / nothing sent.
DELEGATED AUTHORITY · VISION / PROPOSED
01

Delegate for one task

Give an agent a clear job, a bounded set of relevant records, and a scope that does not quietly expand to an entire history.

VISION / PROPOSED
02

Separate preparing from acting

Finding a document, drafting a response, sending it, spending money, and making a commitment are different permissions.

VISION / PROPOSED
03

Keep an activity trail

See what was requested, which context informed the result, where approval was needed, and what happened next.

VISION / PROPOSED

MCP is an early integration surface for compatible implementations. Broad agent orchestration and complete delegated policy controls remain future work.

AGENT BUILDERS · NEXT STEP

Design the handoff around the task.

Discuss a system fit

Useful details

Questions, answered plainly.

Answers reflect the capabilities and limits described on this page.

Can an agent act without asking me?

The vision distinguishes preparation from consequential actions. Sending, spending, or making a commitment should require human approval when the delegated scope does not explicitly cover it.

Is broad agent orchestration available today?

No. MCP is an early surface for compatible implementations. Broad delegated policies, approvals, and activity trails remain future work.