Open Airchor

PUBLIC PRODUCT ROADMAP

From structured project foundation to coordinated, verified delivery.

The roadmap separates what is available, what has been established, what is in active development and what remains planned. It does not use speculative dates or decorative percentages.

Explore the Control PlaneGet Product Updates
  1. 01Foundation established

    Foundation established

    Turn an idea or existing project into structured, persistent project context and a clear preparation path.

  2. 02In active development

    Control Plane foundation

    Bring sources, project truth, next actions and all visible work into one Control Plane experience.

  3. 03On the roadmap

    Coordinated execution

    Coordinate authorised work across agents, humans, repositories and external systems.

  4. 04On the roadmap

    Verified delivery

    Distinguish generated output and task completion from a result that has been checked and is ready for review.

  5. 05On the roadmap

    Launch and continued development

    Release deliberately and continue from the updated project state.

  6. 06Long-term direction

    Platform expansion

    Extend the same Control Plane model across broader teams, providers and portfolios.

The progression is capability-based and publishes no dates or decorative completion percentages.

CONTROLLED STATE LEGEND

The roadmap separates what is available, what has been established, what is in active development and what remains planned.

It does not use speculative dates or decorative percentages.

Available now
Accessible in the current invitation-based product.
Foundation established
Present as the current base for broader Control Plane work.
In active development
Actively being developed but not represented as generally available.
On the roadmap
Planned direction subject to its implementation and release gates.
Long-term direction
A longer-horizon direction rather than a current capability.
Foundation established

Foundation established

Outcome: Turn an idea or existing project into structured, persistent project context and a clear preparation path.

Airchor MVP v1.0 provides invitation-based project creation and assessment, persistent workflow state, structured project outputs, readiness and uncertainty concepts, roadmaps, developer handoffs and individual Markdown downloads.

Representative capabilities

  • Invitation-based project creation and assessment
  • Persistent workflow state
  • Structured project outputs
  • Readiness and uncertainty concepts
  • Roadmaps
  • Developer handoffs
  • Individual Markdown downloads

What this enables next

A proven base of project context, decisions and outputs that can evolve into one Project Model.

In active development

Control Plane foundation

Outcome: Bring sources, project truth, next actions and all visible work into one Control Plane experience.

Representative capabilities

  • unified Source Inbox
  • one Canonical Project Model
  • provenance, evidence and conflict handling
  • Ask, Plan, Execute and Verify intents
  • next-best action
  • versioned Build Specifications
  • Control Plane Work Items
  • Agent Task experience
  • human actions, approvals, reviews and waiting states
  • progressive technical evidence

What this enables next

Bounded execution can begin from an approved project state and specification rather than from an isolated prompt.

In active development

DURABLE PROJECT TRUTH

One Project Model

  • Product intent
  • Scope
  • Requirements
  • Architecture
  • Sources and evidence
  • Decisions
  • Risk and unknowns
  • Ownership and connections
  • Current state
  • Next action

Next actionVisible, reviewable and version-aware

The Project Model is a conceptual durable record of accepted project intent, sources, decisions, evidence, current state and next action.
On the roadmap

Coordinated execution

Outcome: Coordinate authorised work across agents, humans, repositories and external systems.

Representative capabilities

  • policy-controlled provider tasks
  • repository-aware context and change work
  • declared permissions and execution boundaries
  • isolated execution environments
  • approval and review gates
  • external-system correlation
  • pause, retry, replacement and resumption
  • evidence returned to the Work Item

What this enables next

Completed work can enter an independent verification path with the correct technical and operational evidence.

In active development

CONTROL PLANE WORK ITEM

Deliver one approved change

Scope
One bounded result
Coordinator
Airchor Control Plane
State
Waiting for coordinated work
Dependency
Approved Build Specification
Evidence
Task, human and provider records
Next action
Verify the complete result

AGENT TASK · SPECIALISED EXECUTION OBJECT

Implement the approved technical scope

State
Awaiting verification
Current step
Evidence handoff
Completed
Plan followed · Change reported
Pending
Independent verification
Evidence
Changed files and command results
Human action

Review the exact result

Actor
Reviewer
Mode
Assisted
Instruction
Compare the result with the approved scope.
Evidence
Recorded review decision
Resumes
Verification and Preview path

EXTERNAL-SYSTEM STEP

External provider

Responsible actor
External provider
Required input
Exact approved operation
Returned evidence
Correlated provider result
State
Waiting
Boundary
Outside Airchor execution
A Work Item is the parent coordination envelope. Agent Tasks and their execution records remain distinct from human actions, external operations and verification.
On the roadmap

Verified delivery

Outcome: Distinguish generated output and task completion from a result that has been checked and is ready for review.

Representative capabilities

  • verification against acceptance criteria
  • independent checks
  • failure and retry states
  • evidence-linked results
  • preview creation and health evidence
  • Tested Preview Ready
  • user review and change requests

What this enables next

A user can make an informed release decision with the approved specification, result and evidence visible together.

SourceScope and intentTestDeclared check resultLogExecution recordReviewHuman finding
On the roadmap

INDEPENDENT VERIFICATION RECORD

Approved acceptance criteria

Method
Independent checks and review
Evidence
Linked, attributable records
Result
Passed, failed, incomplete or blocked
Limitations
Only the declared scope
Verifier
Separate verification path
Work evidence enters a separate verification boundary; the resulting conclusion remains linked to its exact criteria, evidence and limitations.
On the roadmap

TESTED PREVIEW · NOT PRODUCTION

Tested Preview

Environment
Preview · not Production
Checks
Approved checks passed · Evidence linked
Known limitations
Known limitations remain visible
Review status
Waiting for user review
  1. Task completion
  2. Checks passed
  3. Tested Preview ready
  4. User review
  5. Separate launch decision
Tested Preview is a planned review boundary. It is distinct from task completion, Build Complete and Production deployment.
On the roadmap

Launch and continued development

Outcome: Release deliberately and continue from the updated project state.

Representative capabilities

  • explicit release approval
  • controlled Production launch
  • deployment and post-launch evidence
  • release-state update in the Project Model
  • operational follow-up
  • continued planning from current project truth

What this enables next

Product development becomes a continuous, governed lifecycle instead of a sequence of disconnected handoffs.

On the roadmap
  1. 01Verified preview
  2. 02Explicit approval
  3. 03Launch operation
  4. 04Post-launch evidence
  5. 05Updated Project Model
  6. 06Continue
Production follows an explicit authorised release decision. Launch evidence updates the same Project Model so continued development begins from current truth.
Long-term direction

Platform expansion

Outcome: Extend the same Control Plane model across broader teams, providers and portfolios.

Representative capabilities

  • wider model and provider ecosystem
  • multi-agent coordination
  • agency and multi-client operation
  • portfolio visibility
  • enterprise roles, policies and audit history
  • private and controlled deployment options
  • ecosystem extensions

What this enables next

Extend the same Control Plane model across broader teams, providers and portfolios.

Same core Project ModelPreserved project truth
  • Broader provider categories
  • Multi-agent coordination
  • Portfolio operation
  • Enterprise governance
Provider neutrality is a governing direction, not a claim that every provider is connected.

Current availability

Available now

Create or assess a software project, organise supplied context, make evidence, assumptions, risk and missing information visible, and produce structured planning, roadmap and handoff outputs inside an invitation-based workspace.

Foundation established

Persistent projects, saved workflow state, generated project documents, readiness and uncertainty concepts, individual Markdown downloads, and two proven project origins provide the operational base for the Control Plane transition.

In active development

The unified Project Model, Source Inbox, next-best action, Build Specifications, Control Plane Work Items, visible task orchestration, human-action coordination and the new Control Plane experience.

On the roadmap

Bounded provider execution, repository-aware work, independent verification, Tested Preview, explicit launch control and continued development from the same Project Model.

Follow the programme without confusing progress with availability.

Explore the complete product model, request invitation-based access to the current foundation or subscribe to Product Updates for major programme milestones.

Explore the Control PlaneGet Product UpdatesRequest access

PRODUCT UPDATES

Follow the Control Plane programme

Receive occasional updates about the Airchor product, Control Plane development and major website or release milestones.

Product Updates use email confirmation through double opt-in. Subscribing does not create an Airchor account or grant application access.

Signup uses double opt-in. Airchor does not store your email in a local website database. Read the Privacy Policy.