SERVAI · EXECUTION ENVELOPE v1

Reason freely.
Execute inside the boundary.

Execution Envelope is the governed contract between AI intent and real-world action. Every consequential execution is narrowed to the exact authority, systems, data, runtime, budget and evidence permitted for that piece of work—then tied to an authoritative receipt.

NARROWS · NEVER ENLARGESNO SELF-GRANTFAIL CLOSEDREVOCABLE
EXECUTION ENVELOPEExact authority.
Exact execution.
v1 · production accepted
IDENTITYprincipal + delegation
CAPABILITYtool + adapter + target
DATA + EGRESSrows · fields · destination
COMPUTEruntime + attestation
BUDGETtime + cost + resource
RECEIPTevidence + outcome
ONE ENVELOPE · ALL CONSEQUENTIAL WORK

The model can know more than it is allowed to do.

That distinction is the point. Execution Envelope turns broad intelligence into narrowly governed execution, preserving the authority of your identity, approval, system-of-record and infrastructure controls.

01 · IDENTITY

Who is acting?

Bind the authority principal, execution actor and delegated scope.

02 · CAPABILITY

What can run?

Exact canonical action, tool, connector, adapter, route and target.

03 · CREDENTIALS

Which governed access?

Opaque credential references and exact operation scope. Never raw secrets.

04 · DATA

What may be touched?

Record, field, classification, purpose, provenance and destination boundaries.

05 · NETWORK

Where may data go?

Exact egress destinations, protocols, routes and redirect policy.

06 · COMPUTE

Where may it run?

Placement, residency, runtime identity, sandbox and fresh attestation.

07 · TIME + BUDGET

How far may it go?

Runtime, attempts, actions, tokens, SWU, cost and resource ceilings.

08 · EVIDENCE + RECEIPT

What proves it happened?

Prerequisite evidence before execution; authoritative receipt afterward.

THE EXECUTION PATH

Every surface enters the same governed path.

Workflows, Missions, WorkChat, Voice, ServAI Work and ServAI Computer can originate work. None of them can mint execution authority or bypass the envelope.

INTENTAsk · voice · mission
AUTHORITYIdentity · risk · decision rights
BOUNDARYExecution Envelope
ADMISSIONExact current version
EXECUTIONAction Fabric
SYSTEMSAP · Oracle · CRM · apps
PROOFReceipt · reconciliation
FEDERATE · DON’T REPLACE

Execution Envelope does not become another system of authority.

It consumes and narrows existing authorities. Your identity platform, approvals, enterprise applications, network controls and systems of record keep their jobs.

ServAI owns the execution boundary.

Envelope issuance, narrowing, lifecycle, runtime admission and surface handoff enforcement stay explicit and inspectable.

Your systems keep their authority.

Identity and permissions, approval rights, canonical routing, external records, infrastructure placement, receipts and reconciliation remain with the established authorities behind them.

PRODUCTION ACCEPTED

Designed to fail closed when the boundary is attacked.

The v1 security acceptance covers envelope forgery, stale replay, child-scope escalation, route substitution, secret smuggling, data and egress escape, runtime substitution, budget bypass, evidence/receipt spoofing, orchestration bypass, local-computer escape and revocation bypass.

FORGERY BLOCKEDREPLAY BLOCKEDESCAPE BLOCKEDREVOCATION ENFORCED
EXECUTION ENVELOPEv1PRODUCTION ACCEPTED
ANTI-DRIFT PROTECTED

Give AI the work.
Keep authority bounded.

ServAI can operate above the systems you already trust—without turning intelligence into unlimited permission.

CORE PLATFORM · EXECUTION ENVELOPE v1

AI can reason broadly.
It should execute narrowly.

Before ServAI acts, an Execution Envelope binds the exact identity, capability, credential, data, network, compute, budget, evidence and receipt conditions allowed for that piece of work. It narrows existing authority; it never invents authority.

DENY BY DEFAULTHUMAN AUTHORITYFAIL CLOSEDRECEIPT BOUND
EXECUTION ENVELOPEAuthorized work,
exactly bounded.
before Action Fabric
IDENTITYwho may act
CAPABILITYwhat may run
DATA + NETWORKwhat may move
COMPUTEwhere it may run
BUDGEThow far it may go
EVIDENCEwhat must be proven
01Intent / Mission
02Decision rights
03Execution Envelope
04Action Fabric
05Receipt + reconciliation