Run product updates without manual repair

Workspace applies every safe, product-owned transition for a supported update. You do not need to inspect database columns, system artifacts, Taskstream sources, or revision anchors separately.

Run an update

  1. Create the backup required by your deployment.
  2. Stop the old Workspace version.
  3. Install or start the new official Workspace version.
  4. Wait on the protected server contract:
bash
   nucli --tenant system system product-release status --watch
  1. Confirm that /health/ready returns HTTP 200.

/health/live remains available while Workspace reconciles the release contract. /health/ready returns HTTP 503 until verification succeeds. /health/product-release exposes the limited maintenance state. Workers, analytics, SFTP and SMTP runtimes, and business routes start only after verification.

A routine update does not require numin ... --apply, system-init apply, direct database access, or an operator guessing an ordered maintenance procedure from release notes.

What Workspace verifies automatically

The build-bound contract covers the supported schema and contract window, global system artifacts, workflow library, Taskstream catalog, executors, schedulers, producer sources, and positive tenant and IAM revision anchors. It also compiles every pinned workflow version for every non-deleted tenant. Skipped intermediate releases do not matter while the last completely verified state remains inside the supported window.

Workspace completes the full preflight before it changes product state. It then applies only operations declared as automatic_safe. Persistent checkpoints, leases, and fence tokens make the process idempotent across concurrent instances. Every component uses the same tenant snapshot. Incompatible old nodes stop accepting work, wait for active Taskstream and workflow artifact attempts, and enter drained before mutation starts.

Inspect a blocked update

Existing invalid revisions, inactive producer sources, unknown persisted Taskstream types, uncompilable workflows, and incompatible customer overlays remain unchanged.

bash
nucli --tenant system system product-release status --json

The protected status endpoint remains available through the product release gate. It reports the run, retry time, tenant snapshot, components, runtime evidence, blockers, owning area, and next action without exposing SQL, driver, path, or secret details. numin remains the local read-only diagnostic for a privileged operating environment; use nucli whenever the server is reachable.

Resolve the reported product conflict through its supported contract, then restart the same binary. Reconciliation resumes from verified checkpoints.

New tenants

New tenants automatically use standard.v1 with iam, workflows, crm, localization, commerce, pim, and forum. Workspace creates positive authority anchors before the first producer or job artifact. Business routes remain unavailable until every profile step has been verified.

POST /api/v1/system/tenants creates the tenant, owner binding, and durable provisioning run atomically. Automation must send an Idempotency-Key. Workspace returns HTTP 202, Location, Retry-After, the tenant, the run, and a status URL. Reusing the key with the same normalized request returns the same run; reusing it for another request returns HTTP 409.

System administrators can inspect a tenant with nucli --tenant system system tenant-provisioning status <tenant-id> or GET /api/v1/system/tenants/{tenant-id}/provisioning. Interrupted runs resume in bounded pages with persistent backoff and retain the same run. GET /api/v1/system/tenants?include=provisioning adds each latest status to a paginated tenant list with one batch query. Business routes remain unavailable until the run reaches succeeded.