Agent workbench

​

What this example demonstrates

1. Creating an Agent also creates immutable AgentVersion 1.
2. A configuration-changing Agent update creates the next immutable AgentVersion automatically. There is no separate draft, publish, release, or deployment lifecycle.
3. A preview starts a new Session against the intended AgentVersion. An existing Session keeps the version and Environment frozen at its own admission.
4. PermissionAssignments constrain who may read, edit, or use the Agent. Actor identity comes from authenticated server context rather than a caller-selected attribution field, and Audit records structural control-plane decisions.
5. The browser talks only to the application backend. Workspace API credentials never enter browser code.

Workspace
├── Agent
│   ├── AgentVersion 1
│   ├── AgentVersion 2
│   └── AgentVersion 3
├── Environment
└── Session
    ├── frozen AgentVersion
    ├── frozen Environment authority
    └── durable event log

​

Trust, retention, and support boundaries

​

Pinned source boundary

export class PlatformDenied extends Error {
	constructor(readonly reason: string) {
		super(reason)
		this.name = "PlatformDenied"
	}
}

export class PlatformIsolationBreach extends Error {
	constructor(
		readonly sessionId: string | null,
		readonly cleanupCause?: unknown,
	) {
		super("platform_admitted_cross_user_session")
		this.name = "PlatformIsolationBreach"
	}
}

​

What this example omits