FOR ADVISORS

Make software evidence and uncertainty easier to review

Airchor helps fractional CTOs, consultants, and product advisors organise supplied project context into a reviewable assessment, recovery direction, roadmap, and handoff package.

The current product supports structured decision preparation. It does not independently inspect repositories, certify findings, or replace professional judgment.

Advisor route: organise supplied context into evidence, uncertainty, options, and a bounded next decision.
  1. Supplied context
  2. Evidence and uncertainty
  3. Options and risk
  4. Advisory handoff

THE AUDIENCE PROBLEM

Advice is only as clear as the project record beneath it

Advisors are often asked for direction while project history, source records, implementation state, and technical claims remain incomplete. A useful recommendation needs visible evidence, assumptions, gaps, and decision boundaries.

LIVE

Work on Existing Project

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.

DECISION SUPPORT

Advisor orchestration motif

  1. Evidence
  2. Unknowns
  3. Risk
  4. Options
  5. Bounded recommendation
Evidence, uncertainty, options, risk, and decision boundaries remain visible around the owner’s next decision.
Read visual as text
  1. Evidence
  2. Unknowns
  3. Risk
  4. Options
  5. Bounded recommendation

Evidence → uncertainty → options → decision

LIVE ROUTE MAPPING

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 02LIVE

Work on Existing Project

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

Output package

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 Project
ROUTE 01LIVE

Create New Project

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

Output package

A 14-document Project Blueprint.

Explore Create New Project

CURRENT WORKFLOW

A repeatable structure for advisory review

  1. Record the decision the owner needs to make.

  2. Identify supplied sources of truth and their current status.

  3. Separate supported evidence from reports, assumptions, and unknowns.

  4. Document manual findings, risk, blockers, and dependencies.

  5. Compare repair, refactor, rebuild, pause, or clarification paths.

  6. Prepare a bounded recommendation and implementation handoff for review.

CURRENT OUTPUTS

A reviewable advisory record

The Assessment & Recovery Plan preserves supplied context and manual judgments so the owner, advisor, and next builder can review the same evidence and limitations.

  • Repository Intake
  • Source of Truth Review
  • Audit Execution Plan
  • Client Repository Audit Report
  • Repository Health Scorecard
  • Repair vs Rebuild Decision Memo
  • Client Repair Roadmap
  • Next Implementation Sprints
  • Builder Handoff
  • Developer Handoff
Work on Existing Project10

Assessment & Recovery Plan

  • Client Repository Audit Report
  • Repair vs Rebuild Decision Memo
  • Client Repair Roadmap
  • Developer Handoff

Reviewable Markdown drafts based on saved inputs and deterministic rules.

SYNTHETIC EXAMPLE

Northstar Booking Portal

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.

Source records

  • README — reviewed, medium confidence
  • Sanitised deployment summary — reviewed, medium confidence
  • Owner-reported local sign-in behaviour — reported, low confidence
  • Migration state — unknown, insufficient confidence

Manual findings

  • Authentication failure is reported only in the deployed environment.
  • The active migration state is unknown.
  • No accepted regression test for the sign-in redirect is documented.
  • Deployment configuration requires developer verification.

Synthetic supplied-context scenario. Northstar Booking Portal is not a customer, repository, audit, or delivered repair.

CURRENT LIMITATION

Decision support, not certified diligence

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.

  • No automated repository audit
  • No independent implementation verification
  • No security certification
  • No code repair or implementation delivery
PLATFORM VISION

From advisory decision to governed execution

The planned platform is designed to carry an approved decision into bounded agent work, independent verification, and reviewable delivery while preserving permissions and evidence.

This workflow is planned and is not available in MVP v1.0.

MVP v1.0 · LIVE

Airchor helps fractional CTOs, consultants, and product advisors organise supplied project context into a reviewable assessment, recovery direction, roadmap, and handoff package.