Workspai.dev

Capability Learning Coverage

The enforced map from important Workspai capabilities to learning guides, command reference pages, and published contracts.

Every important Workspai capability needs four connected surfaces:

  1. a learning guide that explains the mental model and authority boundary,
  2. contract-derived command reference pages,
  3. versioned schemas or capability contracts, and
  4. a build gate that prevents silent drift.
27 domains · 144 documented invocations · 106 catalog contracts
CapabilityLearning pathRepresentative commandsPrimary contracts
Create, adopt, and importOpen guidecreate, adopt, import2
Workspace ModelOpen guideworkspace model1
Workspace GraphOpen guideworkspace graph1
Workspace DoctorOpen guidedoctor workspace2
Verified GoalsOpen guidegoal, workspace goal2
Verified AI RepairOpen guideworkspace repair2
Agent groundingOpen guideworkspace agent-sync1
Operational SkillsOpen guideworkspace agent-sync2
Polyglot lifecycle orchestrationOpen guideworkspace run1
Agent entry and bootstrapOpen guideagent bootstrap, project agent-entry, workspace context2
Analysis, readiness, and verificationOpen guideanalyze, readiness, workspace verify3
Change intelligenceOpen guideworkspace snapshot, workspace diff, workspace impact, workspace trace, workspace explain, workspace why4
Pipeline and release governanceOpen guidepipeline, workspace contract, workspace contract verify --strict --json3
Observation, feedback, and evaluationOpen guideworkspace watch, workspace feedback, workspace eval3
Machine integrationsOpen guideworkspace mcp, workspace export, workspace hydrate, workspace share3
Workspace and project portabilityOpen guideworkspace archive, project archive, project restore3
Modules and dependency lifecycleOpen guideadd, modules, upgrade, reconcile, rollback3
Infrastructure operationsOpen guideinfra, infra plan, infra status, infra up, infra down2
Product factoryOpen guideproduct, product manifest, product plan2
AI capabilitiesOpen guideai, ai info, ai recommend, ai generate-embeddings, ai update-embeddings1
Mirror operationsOpen guidemirror, mirror status, mirror sync1
Autopilot releaseOpen guideautopilot, autopilot release1
Workspace registry and operationsOpen guideworkspace, workspace connect, workspace list, workspace registry, workspace sync3
CLI platform operationsOpen guidecommands, config, frameworks, help, info, license, setup, shell, version3
Project lifecycleOpen guideproject, init, dev, start, build, test, lint, format, docs2
Governed state and recoveryOpen guidesnapshot, checkpoint, diff, merge, optimize, uninstall2
Core contracts and protocolsOpen guideworkspace intelligence, workspace intelligence run3

What the gate verifies

The portal rejects a capability mapping when:

  • its learning page is missing or absent from navigation,
  • a mapped command is not published by the runtime command surface,
  • a mapped contract is missing or absent from the public contract catalog,
  • a capability ID or learning route is duplicated, or
  • a required CLI or Workspace Intelligence domain disappears from the matrix,
  • a documented invocation has no capability classification, or
  • a catalog contract has no capability classification.

The complete command catalog remains one page per canonical command. The contract catalog remains the field-level source for every published schema. This matrix owns discoverability between those references and the editorial learning path; it does not redefine CLI behavior.

On this page