Manage workspaces and applications

Workspaces contain applications and have their own Administrator grants. A platform operator provisions a workspace. A workspace Administrator uses a listener bound to that workspace to create applications. Application access is checked in its own scope.

Provision and confirm the exact target

1. Create a workspace uses platform.workspace.create through execute_v2_platform_program. Record the stable workspace ID and verify Active. The creation and first workspace Administrator grant commit together.
2. Confirm the bound listener's workspaceId, then use Create an application through execute_v2_workspace_program. multidimensional starts with the eight empty role axes described in the object model. Keep each create request's original key for exact replay.
3. Inspect the structure from a scoped application session. Verify the exact stable IDs and use a single metadata revision while paging dimensions. Application discovery confirms visibility for the account using the router.

Review maintenance separately

Assess a reset without applying to check the signed workspace inventory and blockers. Then review an already authorized exact reset against the target, manifest digest and expiry. Apply is a separate destructive operation on the dedicated maintenance endpoint. Keep signatures in the authorized operator workflow.

Lifecycle prompt templates · Lifecycle tools

Shared application decisions

Application administrators and their authorized clients use decision operations to record accepted meaning, rationale and provenance beside the application description. Read current decisions when starting work. Use UserDecision only for an explicit administrator decision and AgentInterpretation for an inference. Editing requires the current version and preserves earlier revisions. Withdrawing removes a decision from active context while preserving its deliberate history. Client-local learning remains separate and optional.

Purge one application

The application purge tool offers Prepare, Quiesce and Apply under current workspace-administrator authority. Prepare is read-only; inspect its exact target, creation identity and live work. Quiesce uses the returned identity and digest to close admission. After live leases drain, Apply deletes the application and its content. Each mutating phase uses its own stable request key, retained for response reconciliation. Another application with a reused ID is a different incarnation. The operation retains only a minimal actor/target/outcome receipt and preserves workspace identity and other applications.