Draft Passport record
Capture purpose, business outcome, owner, sponsor, reviewer roles, lifecycle status, risk tier, reviewed scope, data classes, and prohibited actions.
Passport Studio Preview
Define AI Worker ownership, scope, authority, and lifecycle state.
Passport Studio is the customer-managed operating-record builder for turning an AI worker idea into a reviewable Passport record: owner, purpose, reviewed scope, risk tier, evidence needs, Behavioral Envelope, review state, lifecycle posture, and handoff boundaries. Actual workspace access requires login.
Use this preview to see how governance, security, architecture, data, technology, and business stakeholders can review accountable AI Worker records before broader use, runtime-adjacent action, or production planning.
Use this page when you need the workspace preview: how draft Passport records are created, reviewed, and handed off without granting production authority.
Context
Passport Studio helps teams structure AI Worker identity, ownership, scope, and review posture.
A Passport is a governed planning and operating record. It should make the AI Worker purpose, accountable owner, reviewed boundaries, lifecycle state, evidence requirements, authority limits, and open risks clear before broader use.
Review handoff
Identify missing evidence, required Human Review, Toll Gate posture, escalation route, and next owner decision before the worker moves forward.
Operating evidence
Connect Passport posture to evidence records, Stamps, workflow events, Runtime Permit decisions, and lifecycle changes that support accountable oversight.
Persuasion risk
Capture when persuasive, impersonation-like, voice/video-confirmed, BEC-style, or multi-channel requests require process verification before payment, access, external send, or workflow change.
Passport To Permit
Passport Studio is where governance compilation starts.
The Passport record should make the AI Worker identity, purpose, owner, approved tools, prohibited actions, evidence requirements, and lifecycle posture explicit before Runtime Permit or Action Broker review can evaluate a requested action.
Identity and context
Passport and Purpose Binding records establish who or what is acting, for which business purpose, under which owner and lifecycle state.
Action semantics
Allowed actions, prohibited actions, data classes, tool/API scope, and connector boundaries create the canonical action model the Control Plane can evaluate.
Admissibility evidence
Evidence Records, Human Review items, Toll Gate Decisions, Runtime Permit state, and Stamps show whether current authority still has enough standing to proceed.
Passport Studio supports governance compilation and review preparation. It does not issue credentials, approve production use, operate live connectors, provide legal conclusions, provide compliance conclusions, validate security posture, or replace accountable customer review.
Assessment readiness
Passport review examples
Draft review examples show how Passport records preserve owner, purpose, scope, prohibited actions, evidence references, and human review state before any production action is considered.
Owner and scope
Each example Passport keeps the accountable role, approved scope, and prohibited actions visible for review.
Evidence linkage
Each example Passport links to Evidence Records that support the current review posture without exposing customer data.
Review state
Example records remain draft, in review, ready for human review, or blocked until accountable reviewers decide the next step.
Same worked example: Procurement Intake AI Worker
Passport Studio would show the worker owner, purpose, approved supplier-update scope, prohibited external-send action, missing evidence, and Human Review route in one reviewable record.
PassportOwner and purpose found
ScopeDestination outside approved boundary
Toll GateBlocked until evidence exists
EvidenceHuman Review item and Stamp recorded
These examples are local-first static preview data. They do not indicate production authorization, live enforcement, compliance approval, security authorization, or legal conclusions.
Behavioral Envelope
Passport Studio is where agent boundaries become reviewable.
Board and executive oversight depends on Passport-level source records. Passport Studio should make each AI Worker's Behavioral Envelope visible: purpose, use case, data, tool, system, workflow, decision, financial, customer impact, autonomy, jurisdiction, regulatory, safety, escalation, human review, monitoring, evidence, expiration, and renewal boundaries.
Boundary fields
Operating limits should be captured as Passport fields or linked profiles, not as dashboard-only labels.
Evidence linkage
Each material boundary should link to Evidence Records, Stamps, Human Review items, Toll Gate decisions, or renewal records where applicable.
Board signal
Executive Lens and Board AI Governance should summarize Passport and evidence posture without becoming a second source of authority.
Passport Studio supports readiness and review preparation. It does not certify, legally approve, authorize, or guarantee AI Worker use by itself.
Access Boundary
Passport Studio records belong behind customer-controlled access.
Passport records can include operational context, system boundaries, reviewer notes, evidence references, tool posture, and lifecycle signals. Those records should be handled inside an authorized workspace, not exposed as public website content.
Login required
Authorized users should access Passport Studio through the login path for the applicable customer-managed workspace.
Customer accountability
Customer owners and reviewers make formal legal, security, privacy, compliance, audit, and production-readiness decisions for their own environment.
Planning material
Passport Studio supports readiness and review preparation. It does not certify, authorize, approve, or guarantee AI Worker use by itself.
Assurance profiles
Passport planning can summarize framework references, evidence availability, reviewer dependency status, and remediation needs without implying independent approval.
Evidence linkage
Passport assurance views should point to Human Review, Toll Gate, Runtime Permit, and evidence records so later reviewers can trace decisions back to the source record.
Next trust pages
Use this public page as product context only. Workspace access, customer records, and review workflows require login.