AIRCHOR FOR FOUNDERS
Keep the software project understandable without becoming the operator of every technical system.
Airchor helps founders turn ideas, incomplete products and scattered decisions into one structured project, a reviewable plan and a visible path forward.
- 01Project understanding
- 02Bounded plan
- 03Evidence review
- 04Continue
Speed is useful only when the project can still explain itself.
AI tools can produce screens and code quickly, but founders still have to decide what the product is, what should be built next, which assumptions are risky and whether reported progress is real.
Airchor is designed to preserve those decisions and connect them to the work, evidence and next action.
Start with a new idea or continue what already exists.
Describe a new product from its problem, users and intended outcome, or bring the context of an incomplete prototype or existing application. Both paths converge into one Project Model that can continue across planning, implementation and later releases.
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
Known facts
Accepted and supported
Claims
Attributed, not silently accepted
Assumptions
Visible and reviewable
Missing information
Kept open
Risk
Qualified by evidence
BUILD SPECIFICATION · VERSIONED
Approved scope for one Build
- 1Objective
- 2Scope and exclusions
- 3Acceptance criteria
- 4Constraints
- 5Evidence requirements
- 6Human approvals
- 7Provider boundary
- AI agentPerform bounded approved workTask evidence
- HumanApprove, review or provide evidenceRecorded decision
- External systemPerform provider-controlled operationCorrelated result
Human confirmation, provider completion and independently verified completion remain separate states.
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
Separate facts, assumptions, decisions and missing information.
A founder should be able to see which claims are supported, which decisions remain open and which missing information could change scope, cost or delivery.
Airchor’s established foundation already makes readiness, confidence, evidence, risk, assumptions and missing information visible in structured project outputs. The Control Plane extends this into a durable project state.
Move from ambition to a Build Specification that can be reviewed.
The plan should define the intended outcome, scope, exclusions, acceptance criteria, dependencies, ownership and evidence required from the work.
Airchor is being designed to recommend the next-best action and turn approved work into a versioned Build Specification before execution begins.
Keep builders, agents, approvals and provider steps in one visible workflow.
A founder should not have to reconstruct progress from separate chats, developer updates and provider dashboards. Control Plane Work Items make the actor, current step, dependency and required decision visible.
When a human action or approval is required, the workflow should explain what to do, what not to change and what evidence is needed before work can resume.
See the difference between work reported complete and a result ready to approve.
Airchor is designed to connect plans, task progress, changed files, tests, previews and approvals while keeping deeper technical detail optional.
Independent verification and Tested Preview are roadmap capabilities. They are intended to let a founder review the result and its evidence before approving a launch decision.
Keep the project portable when the builder or provider changes.
Airchor’s product direction is built around customer-controlled code, repositories, domains, provider accounts, deployments and project assets. The Project Model preserves the decisions and evidence needed to continue with another developer, agency, model or provider.