DURABLE PROJECT TRUTH
One Project Model
- Intent
- Sources
- Decisions
- Risk
- Evidence
- Next action
Next actionReview a bounded plan
PLAN. ORCHESTRATE. BUILD.
The control plane for AI-assisted software development.
Bring ideas, software, evidence, and decisions into one Project Model. Airchor is building the agentic orchestration layer for software development—turning project direction into coordinated, verifiable execution.
MVP v1.0 provides the live foundation. The unified Control Plane is in active development.
Origin 01Create from an ideaProblem · users · outcome · constraints
Origin 02Import existing softwareCode · evidence · decisions · open issues
In active development
- 01Ask
- 02Plan
- 03Execute
- 04Verify
AgentsHumansExternal systemsEvidence
THE MISSING CONTROL LAYER
Faster code does not automatically create a controlled software project.
AI can accelerate implementation, but the project still has to carry its intent, decisions, constraints, evidence and ownership across many tools and people. Chat histories fragment. Assumptions become invisible. Agents report progress in different ways. Human approvals and provider-console steps disappear outside the workflow.
The result is often more output without a reliable project state. Airchor is being built to keep the complete development lifecycle understandable and coordinated around one source of project truth.
Chat historiesDocumentsCodeDecisionsTestsProvidersOne reliable project state is missing.
In active development
ONE SYSTEM, TWO ORIGINS
Start from an idea or bring existing software. Both become one project.
A new product may begin with a problem, a brief and a set of goals. An existing project may arrive with code, screenshots, documents, decisions, unresolved bugs and conflicting claims.
Airchor treats these as different origins, not separate long-term products. The sources converge into one Project Model that records what is known, what remains uncertain, what has been decided and what should happen next.
PROJECT ORIGIN
Create from an idea
- Source
- Founder or product owner
- Role
- Problem, users, intended outcome and constraints
DURABLE PROJECT TRUTH
One Project Model
- Accepted intent
- Evidence
- Decisions
- Unknowns
- Current state
Next actionOne continued development lifecycle
PROJECT ORIGIN
Import existing software
- Source
- Customer-controlled project sources
- Role
- Code context, screenshots, documents and decisions
A CONTROLLED PATH FORWARD
Understand. Plan. Execute. Verify.
- Understand
- Organise sources, evidence, decisions, assumptions, risk and missing information into a usable project state.
- Plan
- Turn that state into priorities, a bounded next action and a reviewable Build Specification.
- Execute
- Coordinate permitted work through visible tasks, clear actors, approvals and controls.
- Verify
- Compare results with acceptance criteria and evidence before progress is treated as complete.
ONEProject Model
- 01Foundation established
Ask
Read the Project Model and evidence.
- 02In active development
Plan
Create a bounded approach.
- 03On the roadmap
Execute
Coordinate approved Work Items.
- 04On the roadmap
Verify
Evaluate evidence against criteria.
Planning, execution and verification remain distinct so that a generated result, a completed task and an accepted delivery are never treated as the same state.
WHO AIRCHOR IS FOR
One Control Plane. Different decision boundaries.
Founders
Carry a defined problem, scope, assumptions, and acceptance criteria from project foundation toward governed implementation.
Explore routeAgencies
Move from supplied client evidence and bounded findings toward a reviewable recovery direction and future governed repair.
Explore routeAdvisors
Keep evidence, uncertainty, options, risk, and the owner’s next decision visible around future execution.
Explore routeAI Builders
Turn fragmented prompts and fast-moving implementation context into durable project state and controlled agent work.
Explore routeFreelancers
Define a responsible scope, explicit exclusions, acceptance criteria, and review points before another sprint.
Explore routeAgency Project Assessment
Create a deliberate evidence and decision gate before estimating or committing to implementation.
Explore routeIn active development
WORK THAT STAYS VISIBLE
AI agents, humans and external systems belong in the same workflow.
Every meaningful step can be represented as a Control Plane Work Item. Some Work Items may be performed by an AI agent. Others require a Founder, reviewer, approver, developer or external provider.
Airchor is designed to show the responsible actor, automation level, current step, dependencies, evidence and next required action. Work that cannot be automated should still be instructed, tracked, verified where possible and resumed without losing the project context.
Automate what can be automated. Orchestrate what cannot.
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
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
On the roadmap
TRUTHFUL PROGRESS
“Done” becomes a sequence of clear, reviewable states.
An agent stopping is not the same as a task being verified. Checks passing is not the same as a Tested Preview being ready. A preview being ready is not the same as user approval or Production launch.
Airchor is being designed to keep these states separate and visible. Plans, changed files, commands, tests, previews, approvals and release evidence should support the claim being made, while deeper technical detail remains available when it is needed.
- 01
Claim
Attributed statement
- 02
Source
Provenance recorded
- 03
Evidence
Relevant artefact
- 04
Check
Criterion evaluated
- 05
Conclusion
Scope-qualified result
SourceProvenance visibleTestResult recorded
SourceScope and intentTestDeclared check resultLogExecution recordReviewHuman finding
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
Governing product direction
BUILT FOR CONTINUITY
The project should survive changing tools, agents and providers.
Airchor is designed around customer control of code, repositories, provider accounts, domains, deployments and project assets. The Project Model should preserve intent, decisions and evidence even when a model changes, an agency hands over the work or development pauses and resumes later.
Provider neutrality is a governing direction rather than a claim that every integration is available today. The roadmap defines when each connection and execution path becomes part of the product.
Governing product direction
CUSTOMER-CONTROLLED FOUNDATIONS
- Code
- Repositories
- Provider accounts
- Domains
- Deployments
- Project assets
CUSTOMER-CONTROLLED FOUNDATION
Project continuity
- Custodian
- Customer
- Provider category
- Generic, replaceable connections
- Portability direction
- Designed to preserve project truth across tools
- Airchor boundary
- Airchor coordinates; individual integrations follow the roadmap
Model providerRepository providerDeployment provider
FROM FOUNDATION TO CONTROL PLANE
A clear progression, without presenting the future as live.
- 01Foundation established
Foundation established
The invitation-based MVP structures new and existing projects, preserves workflow state, makes uncertainty visible and creates planning, roadmap and handoff outputs.
- 02In active development
Control Plane foundation
The active programme introduces the unified Project Model, Source Inbox, next-best action, Build Specifications, Work Items and visible task coordination.
- 03On the roadmap
Coordinated execution
Planned capabilities connect bounded agent, human and external-system work through permissions, approvals and evidence.
- 04On the roadmap
Verified delivery
Independent checks, Tested Preview and explicit review create a trustworthy boundary before launch.
- 05On the roadmap
Launch and Continue
Approved releases and post-launch evidence update the same Project Model so that the next cycle begins with current project truth.
INVITATION-BASED ACCESS
Request access to the current Airchor foundation
The current application is available by invitation. Tell us who you are, what stage your software project is in and why you are interested in Airchor. Do not send credentials, private source code, repository archives, raw Production logs or confidential client information.
Submitting a request does not create an account or guarantee immediate access. Existing invited users can sign in or open the application directly.
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.