Verified AI Repair

An AI model can propose a convincing patch and still leave the workspace broken. Workspai treats repair as a transaction with a goal, scope, allowed actions, and completion evidence.

Examples of user goals include:

• prepare this workspace for release;
• repair dependency vulnerabilities without a breaking change;
• raise test coverage to 75% and keep the build passing.

Plan a bounded goal

npx workspai workspace goal plan dependency-security \
  --scope project:api \
  --json

Or define a measurable coverage target:

npx workspai workspace goal plan test-coverage \
  --scope project:web \
  --target 75 \
  --json

The plan records the project boundary, required stages, approval points, and evidence needed for completion. The VS Code Studio can execute that contract while the CLI remains the source of diagnostic and verification truth.

The repair transaction

For a dependency blocker, Workspai first audits and classifies the finding. It then applies the approved repair, reconciles the manifest, lockfile, and installed tree, runs the focused audit and declared test/build checks, refreshes workspace intelligence, and finally verifies the goal.

Changing package.json alone is not completion. Workspai waits for the lockfile and installed tree to agree before evaluating the result.

Check the result

npx workspai workspace goal status --json
npx workspai workspace verify --strict --json

A goal completes only when its declared evidence is current and its gate accepts the result. A blocker that remains unresolved stays visible; the model does not get to mark its own work as successful.

Where the model decides

Workspai executes deterministic repair capabilities directly when the contract permits them. The model is used where a source-level decision is genuinely needed. Every change still returns to Doctor, the intelligence loop, and verification.

Start with Workspace Doctor to understand how the original finding and repair capability are produced.