FOR AGENCIES
Airchor helps agencies organise supplied client context into assessment, recovery, roadmap, sprint, and handoff documents.
The current product provides a structured manual assessment workflow. It does not yet inspect repositories, reproduce failures, or verify technical conclusions automatically.
THE AUDIENCE PROBLEM
Inherited projects often arrive with incomplete documentation, uncertain repository access, unverified technical claims, unclear deployment history, and pressure to estimate repair work before the real project state is understood.
Use this route when software already exists and the main task is understanding, assessing, repairing, recovering, or rebuilding it.
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.
Intake → evidence → decision → handoff
LIVE ROUTE MAPPING
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.
Use this route when software already exists and the main task is understanding, assessing, repairing, recovering, or rebuilding it.
A 10-document Assessment & Recovery Plan.
Current boundary: 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.
Explore Work on Existing ProjectUse this route when the main task is defining what should be built.
A 14-document Project Blueprint.
CURRENT WORKFLOW
Record the reported repository and project state.
Identify the current sources of truth.
Add bounded evidence and mark uncertainty.
Complete the eight manual assessment categories.
Record findings, risk, blockers, and actions.
Generate the Assessment & Recovery Plan.
Review the repair-versus-rebuild direction.
Prepare the next implementation sprints and handoffs.
CURRENT OUTPUTS
The package includes repository intake, source-of-truth review, an audit execution plan, manual findings, a qualitative health scorecard, repair-versus-rebuild direction, a recovery roadmap, implementation sprints, and handoff drafts.
Reviewable Markdown drafts based on saved inputs and deterministic rules.
SYNTHETIC EXAMPLE
An inherited Next.js, Node, and PostgreSQL booking application. The deployed sign-in flow redirects to an error, while local sign-in reportedly works. A README and sanitised deployment summary are available. Test coverage and migration state are unknown. The immediate goal is to determine whether the authentication path can be repaired safely without replacing the booking workflow.
Synthetic supplied-context scenario. Northstar Booking Portal is not a customer, repository, audit, or delivered repair.
Airchor can help make reported evidence, assumptions, gaps, and risk more visible. It does not provide formal technical due diligence, independent code verification, security certification, or a professional guarantee.
The planned platform extends a reviewed finding into an approved AgentTask, isolated execution, independent verification, and a reviewable pull request or preview.
This workflow is planned and is not available in MVP v1.0.
Airchor helps agencies organise supplied client context into assessment, recovery, roadmap, sprint, and handoff documents.
