Product proof
Review the homepage, Passport preview, Governed Workflow, Create a Scaled Agent, and Passport Studio preview to understand the control-plane loop.
Enterprise Evaluation Pack
Current capability status for enterprise AI worker governance.
Use this page to evaluate what Scaled Agents provides today, what remains a preview, what requires customer integration, and what must be reviewed before customer-specific or production use.
Capability Status
Separate live public MVP, preview, customer integration, and future work.
The public website and Passport previews are suitable for readiness conversations and guided enterprise evaluation. Customer-specific operation requires approved scope, access controls, contracts, privacy/security review, and implementation evidence.
| Capability | Status | What it means | Boundary |
|---|---|---|---|
| Public website and resources | Available now | Public pages, library, use cases, Advisor paths, training catalog, and readiness content. | Informational only; no customer-specific approval. |
| Create a Scaled Agent | Available now | Draft Blueprint path for shaping a worker idea, classifying risk, and preparing next steps. | Blueprints are recommendations, not approval records. |
| Passport record preview | Available now | Static example showing owner, purpose, scope, risk, evidence posture, Toll Gates, and lifecycle context. | Sample only; no live customer artifact. |
| Passport Studio Control Plan | Noindex preview | Control-plane preview for Worker creation, Passport, Registry, Human Review, Runtime Permit, Action Broker, evidence, and oversight views. | Local/mock proof; no live customer access or live connectors. |
| Customer workspace | Requires approval | Customer-specific workspace, access controls, evidence storage, and support model. | Requires written agreement, security/privacy review, and customer owner authorization. |
| Runtime enforcement and connectors | Future integration | Customer IAM, model runtime, tools, APIs, MCP-compatible transports, logs, and system-of-record actions. | Requires implementation, testing, customer authorization, and controlled rollout. |
Buyer Evaluation Pack
What an enterprise evaluator should review first.
Trust proof
Review Security, Privacy, Terms, Shared Responsibility, Governance Assurance, and framework readiness pages for boundaries and evidence posture.
Delivery proof
Review the Public Library, Forward-Deployed AI, Procurement Accelerator, and first-30-day path to understand guided evaluation and implementation support.
First 30 Days
A practical first-month evaluation path.
| Week | Focus | Expected output |
|---|---|---|
| 1 | Define buyer goals, AI worker candidates, data boundaries, owners, and review constraints. | Evaluation scope and initial AI worker shortlist. |
| 2 | Create draft Blueprints and map each worker to owner, scope, risk tier, review path, and evidence needs. | Draft Blueprint set and Passport readiness gaps. |
| 3 | Review Passport, Toll Gate, Human Review, Runtime Permit, and Action Broker fit against one mock workflow. | Control-plane walkthrough with blockers and assumptions. |
| 4 | Decide whether to continue with advisory support, licensed workspace planning, partner-led implementation, or backlog deferment. | Owner decision record and next-slice plan. |
MVP To GA Criteria
What must be true before broader customer operation.
Access and workspace
Authentication, workspace separation, least-privilege roles, account recovery, and customer-owner administration must be approved and tested.
Evidence and export
Passport, Registry, Toll Gate, Human Review, Runtime Permit, Action Broker, Evidence Record, and Audit Export packages need customer-safe storage and retrieval rules.
Support and incident path
Support tiers, security intake, incident routing, notification expectations, and escalation contacts must be governed by written agreement.
Security, Privacy, And Regulated Data
Use public forms for planning context only.
Security or incident intake
Use the readiness intake for non-sensitive security concerns and state that the request is security-related. Do not submit secrets, credentials, regulated records, customer evidence, source code, or sensitive architecture in public forms.
Regulated data FAQ
Public paths are not a HIPAA, GDPR, CCPA, employee-record, payment-card, or regulated-data intake channel. Customer-specific regulated data requires a reviewed private path and written terms.
Data handling boundary
Customer workspace data, Passport records, evidence records, retention, deletion, subprocessors, cross-border transfers, and audit access must be controlled by the applicable agreement.
Evidence Standard
Evidence should reconstruct why an AI worker action was allowed, blocked, escalated, or deferred.
Minimum evidence set
Worker, Passport, owner, purpose, risk tier, scope, tool/data boundary, policy version, review state, requested action, decision, missing inputs, and lifecycle outcome.
Human review
Material or unclear actions should link to a Human Review item with reviewer role, decision, evidence considered, conditions, and next review date.
Export boundary
Exports should use redacted summaries, non-secret identifiers, related record IDs, hashes where appropriate, and explicit limitations. They are readiness support, not audit opinions.
Delivery Model
Choose the engagement path that matches the buyer's maturity.
Guided evaluation
Best for teams validating AI worker governance needs before platform commitment.
Forward-deployed support
Best for workflow discovery, operating-model design, implementation planning, and governed rollout support.
Partner-led enablement
Best for advisory firms, GRC consultants, security advisors, and implementation partners supporting multiple clients.
Portability And Accessibility
Customer records and accessible review paths must remain practical.
Data portability
Customer-specific Passport records, evidence summaries, decisions, and exports should be available in reviewable formats defined by the applicable agreement.
Exit plan
Customer exit should define export format, retention, deletion, archival evidence, revocation state, and final owner acknowledgement.
Accessibility statement
The public site targets keyboard-operable navigation, readable contrast, descriptive alt text, labeled forms, and accessible tabs. Accessibility gaps should be routed through readiness intake with page, device, browser, and assistive-technology context.
Current Release Notes
June 2026 public MVP review posture.
- Website and Passport Studio audit reviewed 70 HTML surfaces with 70 high-confidence pages, 0 medium-confidence pages, and 0 unsafe claim findings.
- Website release audit, static website validation, source governance validation, and website test suite passed in the latest local evidence run.
- Passport Studio public wording uses renewal review, completion status, draft-only records, and explicit no-production-authorization boundaries.
- legacy legacy delivery-specific training planning has been retired from active training direction and should remain archived unless separately reapproved.
Release notes are local review evidence. They do not prove live deployment, production access, customer data processing, legal approval, compliance approval, security authorization, certification, or audit opinion.