From live planning to governed agentic orchestration

Repository connections

Connect an approved repository and preserve the selected provider, repository, branch, and exact source state.

User value: Project conclusions can be tied to the real repository rather than only reported context.

Boundary: Private repository connection and content analysis are not current MVP features.

Immutable repository snapshots

Preserve the exact commit, tree, manifests, selected files, and retrieval state used by a project assessment or task.

User value: Plans and findings remain linked to a specific source state even when the repository changes later.

Source-linked project intelligence

Turn repository facts, project documents, evidence, and findings into reviewable source-linked project context.

User value: Users can distinguish observed facts from assumptions, user reports, and generated interpretation.

Grounded AI synthesis

Use approved source evidence to support structured synthesis, planning, and recommendations.

User value: AI-assisted outputs can cite the project evidence they rely on and expose uncertainty.

Boundary: Grounded Production AI is not a primary live MVP capability.

Approved AgentTasks

Convert a finding, roadmap item, or handoff into a bounded unit of work with objective, scope, exclusions, acceptance criteria, and dependencies.

User value: Execution begins from reviewed project context rather than an empty prompt.

Immutable AgentPlans

Freeze the approved task plan, expected files, commands, checks, risks, and stop conditions before execution begins.

User value: Scope changes become visible and require a new review rather than silently modifying the approved plan.

Capabilities and approvals

Define exactly what an agent may do, where, for how long, and with whose approval.

User value: Repository, file, terminal, network, secret, pull-request, deployment, and database actions remain bounded and inspectable.

Boundary: The planned model is default deny and task scoped.

Execution console

Show the approved objective, current phase, agent permissions, events, changed files, tests, verification, artefacts, cost, and recommended next action.

User value: Users can understand what is happening without relying only on provider-specific logs.

Boundary: This will be a project-attached experience, not a separate generic developer console.

Registered local runner

Run approved tasks inside a registered local environment with short-lived leases, bounded capabilities, event reporting, cancellation, and cleanup.

User value: Source can remain within the user's environment during the first execution phase.

Boundary: Production credentials and unrestricted system access are excluded.

Coding-agent adapter

Connect the Airchor task, permission, event, and verification model to a first coding-agent provider through a provider-neutral interface.

User value: The underlying agent can change without rewriting the Airchor product model.

Isolated branches and worktrees

Create an exact-base branch or worktree for bounded changes without modifying the user's active branch.

User value: Implementation can be inspected, cancelled, retried, or discarded without contaminating the primary checkout.

Approved command execution

Run allowlisted inspection, test, typecheck, lint, and build commands within the approved environment and budget.

User value: Task progress is supported by observed command results rather than model claims.

Boundary: Dependency installation, network access, destructive actions, and Production operations require separate controls.

Independent verification

Check the final diff, approved scope, tests, build, artefacts, and delivery state outside the coding-agent session.

User value: A coding agent cannot mark its own work complete without separate evidence.

Execution artefacts and evidence

Preserve task plans, approvals, events, command results, diffs, test reports, verification results, and completion records.

User value: The project keeps a durable history of what was approved, attempted, observed, and delivered.

Draft pull requests

Deliver a verified result through a reviewable branch and draft pull request after separate approval.

User value: External delivery remains visible and reversible.

Boundary: Merge and protected-branch actions remain outside the initial workflow.

Preview deployments

Create or recognise a preview linked to the exact verified commit and persist its status in Airchor.

User value: Reviewers can inspect a bounded result without promoting it to Production.

Boundary: Production promotion is excluded from the initial roadmap.

Work on Existing Project: bounded repair

Extend a reviewed finding into an approved task, isolated change, independent verification, and draft pull request or preview.

User value: Move from assessment into a reviewable repair without losing the evidence and reasoning behind it.

Create New Project: governed implementation

Extend an approved Project Blueprint into bounded repository creation, scaffolding, verification, and reviewable delivery.

User value: Carry the original project scope, assumptions, and acceptance criteria into implementation.

Boundary: This follows the first complete WOEP repair workflow.