AI execution evidence / Bounded evidence pilots

Show what your AI did.
And who authorised it.

Durable orchestration. Explicit authority. A portable execution record a reviewer can verify offline.

Preserve the recorded history of an AI undertaking across contexts: authenticated actors, state changes, model and tool activity, approvals and interventions.

Try the live demonstration Start a paid evidence check

Start with a $100 seven-day synthetic evidence check. The first five eligible signed pilots remain $500 each for four weeks. Public naming is optional and may be requested separately after successful technical acceptance.

Built for continuity and control

Keep the state. Bound the authority.

01 / IDENTITY

Roles that persist

Create and coordinate roles through the API. Untransferred obligations constrain role closure and merging.

02 / EVIDENCE

A history you can inspect

Keep source records and attributed actions. Review proposed changes and export a verifiable record. A summary is not a replacement for raw history.

03 / BOUNDARIES

Explicit access and limits

Authenticated principals, scoped authority, revocation and usage ceilings keep permissions explicit. Your application controls how models contribute.

Your application. Your model.

Establish identity.
Keep authority explicit.

Protected actions require an enrolled human or dedicated machine principal and current execution permissions. A tenant key alone is not identity. The agentgateway path is qualified for one reference echo tool; calls bypassing CarryFrame are outside its recording boundary.

Read the identity and integration guide

Authorization: Bearer <short-lived token>
X-CarryFrame-Tenant: <authorised tenant UUID>

# Machines additionally use the reviewed
# signed companion and service enrollment.
# Never put credentials in URLs or logs.

A durable layer beneath your application

Contexts are temporary.
Identity and history aren’t.

Successor contexts work within persistent roles. Accepted records, obligations and inbox messages belong to the orchestration, not to a chat window.

Context 01Context 02Context 03

Persistent role Other roles

RecordsObligationsInbox

One undertaking. A continuing record.