FOR FREELANCERS
Airchor helps freelancers and independent builders turn supplied client context into visible scope, assumptions, risk, recovery direction, sprint planning, and handoff material.
Airchor supports planning and manual assessment. It does not inspect client repositories automatically, certify project quality, or guarantee estimates or delivery outcomes.
THE AUDIENCE PROBLEM
A client request can arrive with code but without a reliable project record, current source of truth, accepted scope, or verified implementation state. Estimating or continuing too early can make hidden uncertainty part of the freelancer’s delivery responsibility.
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.
Request → boundary → sprint → review
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
Capture the requested outcome, supplied context, and known history.
Separate supported facts from assumptions and client-reported state.
Identify missing information, dependencies, and delivery risk.
Define the next safe sprint with explicit exclusions.
Record observable acceptance criteria and review points.
Prepare the context for client and developer review.
CURRENT OUTPUTS
The Assessment & Recovery Plan can support a clearer client conversation and bounded next sprint. It does not guarantee an estimate, timeline, repair path, or outcome.
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 freelancers and independent builders turn supplied client context into visible scope, assumptions, risk, recovery direction, sprint planning, and handoff material.
