atoi-project-work

Atoi Project Work

Use Atoi as the authority for project identity, Workspace source truth, and durable Task outcomes. Keep the sequence intact: Project → Workspace → Task → Result · Changes · Checks · Proof.

Preconditions

1. Confirm the product CLI is connected:

   atoi account status --json
   atoi mcp status --probe --json
   

2. If the account is disconnected, ask the user to run:

   atoi account login
   

3. Never request, copy, print, or place an Atoi token in a plugin configuration. The local atoi mcp serve bridge owns credentials.

Choose the Surface

• Prefer the atoi_projects, atoi_workspace, and atoi_tasks MCP tools when they are mounted in the current agent.
• Use the public atoi CLI when shell access is available or when the task requires local source inspection or local application.
• Use --json for machine-readable CLI calls.
• Do not invent a second project, workspace, task, or proof schema.

Workflow

1. Resolve the Project

List Projects before creating one:

atoi project list --json

With MCP, call atoi_projects with action: "list".

Reuse a Project when its identity and repository match. Create only when no matching Project exists:

atoi project create \
  --name "My project" \
  --repo owner/repository \
  --branch main \
  --profile workspace-write \
  --json

With MCP, call atoi_projects with action: "create", name, repo_url, repo_branch, and default_task_profile.

Capture the returned Project ID. Treat it as the stable identifier for every following step.

2. Establish Workspace Source Truth

Inspect the Project's one stable Workspace:

atoi workspace show --project <project-id> --json

Bind it only when the intended repository, branch, or directory is absent or wrong:

atoi workspace bind \
  --project <project-id> \
  --repo owner/repository \
  --branch main \
  --directory /absolute/repository/path \
  --json

From the bound repository, report current local source truth: