Open Airchor
LIVE · INVITATION ACCESS

Airchor MVP v1.0

A planning and assessment workspace for new and existing software projects

Airchor turns user-provided project context into persistent, readiness-labelled planning documents, assessments, roadmaps, and developer-handoff drafts.

The current product organises and processes supplied context. It does not yet inspect repositories autonomously, execute code, repair software, run user-project tests, create pull requests, or deploy user projects.

Open Airchorapp.airchor.comHow It WorksSign inapp.airchor.com

Access is currently invitation-based.

LIVE FOUNDATION

The live project-intelligence foundation

ROUTE 01Create New Project
ROUTE 02Work on Existing Project
Project context
  • Evidence
  • Readiness
  • Roadmaps
  • Handoffs
Create New Project and Work on Existing Project feed persistent context, evidence, readiness, roadmaps, and handoff documents.
Read visual as text
  1. Create New Project
  2. Work on Existing Project
  3. Project context
  4. Evidence
  5. Readiness
  6. Roadmaps
  7. Handoffs

This is live MVP v1.0 functionality. It does not execute or verify code.

CURRENT PRODUCT

One workspace. Two starting points.

Use Create New Project when the software does not yet exist or still needs to be defined. Use Work on Existing Project when an application, prototype, inherited repository, or deployed product already exists and requires structured assessment or continuation planning.

ROUTE 01LIVE

Create New Project

Use this route when the main task is defining what should be built.

Output package

A deterministic 14-document Project Blueprint generated from user-provided context.

Explore Create New Project
ROUTE 02LIVE

Work on Existing Project

Use this route when software already exists and requires structured assessment or continuation planning.

Output package

A deterministic 10-document Assessment & Recovery Plan based on supplied and manually reviewed context.

Current boundary: Airchor does not currently inspect or verify repository code automatically.

Explore Work on Existing Project

DETERMINISTIC WORKFLOW

How Airchor works today

  1. Input

    Provide structured project context.

  2. Structure

    Separate known information, assumptions, evidence, gaps, and risks.

  3. Assess

    Apply deterministic rules to readiness, confidence, evidence strength, and next actions.

  4. Generate

    Create the relevant persistent Markdown document package.

  5. Review

    Inspect the documents, limitations, warnings, and staleness.

  6. Download

    Download eligible documents for developer, agency, advisor, or coding-tool review.

LIVE

Create New Project

Use this route when the main task is defining what should be built.

What you provide

Capture the problem, target users, proposed solution, scope, exclusions, features, architecture assumptions, risks, roadmap, evidence context, assumptions, and missing information.

Open Airchorapp.airchor.comSee the 14-document Blueprint
LIVE · 14 DOCUMENTS

Project Blueprint document atlas

  1. Foundation
  2. Scope
  3. Features
  4. Architecture
  5. Execution
  6. Validation
  7. Handoff
Fourteen deterministic documents connect product definition, scope, architecture assumptions, execution planning, validation, and the first builder handoff.
Read visual as text
  1. Foundation
  2. Scope
  3. Features
  4. Architecture
  5. Execution
  6. Validation
  7. Handoff

Generated from saved user-provided context and deterministic templates.

DETERMINISTIC OUTPUT PACKAGE

A 14-document Project Blueprint

Generated from saved user-provided context and deterministic templates for review, refinement, and handoff.

Create New Project

Project Blueprint

14 documents
  1. Idea Foundation
  2. Project Evolution
  3. Market / Context
  4. Product Concept
  5. Project Definition
  6. Project Scope and Output Boundary
  7. Feature Prioritisation
  8. Technical Architecture
  9. Code Development Plan
  10. Project Execution Plan
  11. Testing and Validation Plan
  12. Pricing / Package Recommendation
  13. Documentation Sync Rules
  14. Sprint 001 Builder Handoff

The Blueprint is generated from user-provided context and deterministic templates. Architecture, pricing, market, testing, and implementation statements remain advisory drafts until reviewed.

LIVE

Work on Existing Project

Use this route when software already exists and the main task is understanding, assessing, repairing, recovering, or rebuilding it.

What you provide

Record reported repository context, access state, technology summary, known issues, deployment and testing status, source-of-truth records, evidence, assumptions, manual findings, risks, recovery goals, and constraints.

Open Airchorapp.airchor.comSee the 10-document Assessment & Recovery Plan
LIVE · 10 DOCUMENTS

Assessment & Recovery document atlas

  1. Intake
  2. Source review
  3. Manual findings
  4. Health
  5. Decision
  6. Recovery
  7. Handoffs
Ten deterministic documents connect repository intake, source review, manual findings, health, repair-versus-rebuild direction, recovery, sprints, and handoffs.
Read visual as text
  1. Intake
  2. Source review
  3. Manual findings
  4. Health
  5. Decision
  6. Recovery
  7. Handoffs

Based on supplied and manually reviewed context; not autonomous repository analysis.

DETERMINISTIC OUTPUT PACKAGE

A 10-document Assessment & Recovery Plan

Structured from supplied project context, evidence, manual findings, risks, goals, and constraints.

Work on Existing Project

Assessment & Recovery Plan

10 documents
  1. Repository Intake
  2. Source of Truth Review
  3. Audit Execution Plan
  4. Client Repository Audit Report
  5. Repository Health Scorecard
  6. Repair vs Rebuild Decision Memo
  7. Client Repair Roadmap
  8. Next Implementation Sprints
  9. Builder Handoff
  10. Developer Handoff

The assessment is based on supplied and manually reviewed context. Airchor does not currently inspect repository code, reproduce failures, run tests, or verify deployment state.

SAVED PROJECTS

Leave, return, and continue

Successful project creation, submitted workflow stages, evidence records, findings, and generated documents are saved to the authorised workspace. Returning users can open Saved Projects, Open Latest Project, or Continue Project.

LIVE

Persistent project-state loop

  1. Submit stage
  2. Persist context
  3. Generate documents
  4. Review
  5. Return
  6. Continue
Successful workflow stages update the authorised workspace so users can leave, return, review, regenerate, and continue from durable project state.
Read visual as text
  1. Submit stage
  2. Persist context
  3. Generate documents
  4. Review
  5. Return
  6. Continue

Saved state, not a disposable chat transcript.

Persistence boundary: Text entered into a form is not saved until the relevant action succeeds. Continue Project opens the project overview rather than restoring the exact last page visited.

ADVISORY METADATA

A document is not the same as proof

Airchor makes the limits of the current project context visible through readiness, confidence, evidence strength, risk, assumptions, missing information, blockers, and recommended next actions.

Readiness
Whether the saved project context supports the intended next use.
Confidence
Rule-based support from the current saved information.
Evidence strength
The quality, freshness, and conflict state of user-provided sources.
Risk
Warnings, blockers, conflicts, and declared project risks.
Assumptions
Beliefs that still require confirmation.
Missing information
Absent records, decisions, evidence, or access needed for stronger reliance.
Recommended next action
The first useful step selected from the current project state.

These indicators are advisory and do not independently prove technical, security, or production readiness.

LIVE · ADVISORY

Readiness and uncertainty model

PROJECT STATEVisible uncertainty
  • Readiness
  • Confidence
  • Evidence
  • Risk
  • Assumptions
  • Missing information
  • Next action
Readiness, confidence, evidence strength, risk, assumptions, missing information, and recommended next action remain visible together.
Read visual as text
  1. Readiness
  2. Confidence
  3. Evidence
  4. Risk
  5. Assumptions
  6. Missing information
  7. Next action

Advisory metadata does not certify technical, security, legal, or Production readiness.

Advisory only: These labels are advisory and rule-based. They do not certify architecture, security, legal compliance, code quality, deployment readiness, or implementation feasibility.

AUTHENTICATED EXPORT

Private, authenticated Markdown downloads

Eligible generated documents can be downloaded individually as the exact persisted Markdown saved by Airchor. Authentication and project authorisation are required.

Download formats in Airchor MVP v1.0
FormatStatusCurrent behaviour
Individual Markdown (.md)SupportedAuthenticated, project-authorised download of exact persisted Markdown.
Combined hosted packageNot supportedNot currently available in MVP v1.0.
PDFNot supportedNot currently available in MVP v1.0.
DOCXNot supportedNot currently available in MVP v1.0.
ZIPNot supportedNot currently available in MVP v1.0.
Public share linkNot supportedNot currently available in MVP v1.0.
Client portalNot supportedNot currently available in MVP v1.0.
LIVE OUTPUT

Reviewable Markdown output

  1. 01# Project state
  2. 02## Evidence
  3. 03## Assumptions
  4. 04## Risks
  5. 05## Next action
Authenticated individual download
Eligible generated documents can be downloaded individually as exact persisted Markdown after authentication and project authorisation.
Read visual as text
  1. # Project state
  2. ## Evidence
  3. ## Assumptions
  4. ## Risks
  5. ## Next action

Markdown is supported. PDF, DOCX, ZIP, public shares, and combined hosted packages are not.

CURRENT LIMITATION

What is not included in MVP v1.0

Airchor is a planning and assessment workspace. These boundaries keep current product behaviour separate from the planned orchestration platform.

  • No autonomous repository or source-code inspection.
  • No branch, commit, diff, issue, pull-request, or CI analysis.
  • No dependency, vulnerability, or security scanning.
  • No user-project test or build execution.
  • No code repair or code generation.
  • No user-project deployment.
  • No Production AI repository analysis.
  • No private GitHub repository ingestion.
  • No public self-sign-up.
  • No billing or team collaboration.
  • No PDF, DOCX, ZIP, or public-share export.
  • No technical, security, legal, or production-readiness certification.
LIVE · INVITATION ACCESS

Open the live product

Airchor is available at app.airchor.com. Existing invited users can sign in.

Open Airchorapp.airchor.comSign inapp.airchor.com
PLATFORM VISION

The planning foundation for governed execution

The current project, evidence, readiness, roadmap, and handoff models provide the foundation for a future platform spanning repository intelligence, approved AgentTasks, capability controls, isolated execution, independent verification, pull requests, previews, and updated project state.

Current Airchor foundation and planned platform direction
LIVE IN MVP v1.0

Structured project state

  1. Planning and assessment workspace
  2. Create New Project
  3. Work on Existing Project
  4. Persistent projects and Saved Projects
  5. 14-document Project Blueprint
  6. 10-document Assessment & Recovery Plan
  7. Readiness, confidence, evidence, risk, assumptions, and next actions
  8. Authenticated Markdown downloads
PLANNED / VISION

Governed agentic execution

  1. Repository intelligence and immutable snapshots
  2. Grounded AI and source citations
  3. Approved AgentTasks and AgentPlans
  4. Capability and permission gates
  5. Local and managed execution environments
  6. Coding-agent adapters
  7. Independent verification
  8. Pull requests and previews
  9. Recurring monitoring
  10. Enterprise and multi-agent controls

This is the planned platform direction, not current MVP functionality.

PLATFORM VISION

The Airchor orchestration field

  1. Project context
  2. Airchor control layer
  3. AgentTasks
  4. Execution
  5. Verification
  6. Delivery
Project intelligence passes through a governed control layer before bounded execution, independent verification, and reviewable delivery.
Read visual as text
  1. Project context
  2. Airchor control layer
  3. AgentTasks
  4. Execution
  5. Verification
  6. Delivery

Context → control layer → AgentTasks → execution → verification → delivery

Explore the Agentic VisionView the Roadmap