Mirror Operations

Inspect and synchronize governed mirrors without promoting compatibility copies into a second source of truth.

A mirror exists for compatibility, distribution, or consumer access. Its authority always points back to the canonical source and versioned mirror contract.

npx workspai mirror status --json

Status reports direction, source, destination, version, and drift. Synchronize only through the declared boundary:

npx workspai mirror sync --json

Consumers must reject missing, stale, incompatible, or checksum-mismatched mirrors. They must not edit the mirror and then infer that the canonical source changed.

This is the same principle used by the Workspai contract mirrors in consuming websites and extensions: the CLI owns the contracts; consumers verify and project them.

Command reference: mirror, mirror status, and mirror sync.

Product Factory

Build and validate private product manifests and generation plans through the CLI-owned product boundary.

Machine Integrations

Expose bounded Workspace Intelligence to MCP, automation, sharing, export, and hydration consumers without creating another authority.