launch-project-audit

Production readiness audits classify features as not-started, stubbed, built-disconnected, built-wired, or built-tested. They determine whether code is actually connected and estimate deployment progress from in-progress to in-production.

Map pipeline staging to deployment evidence by tracking feature progress from idea through PR-open and merged to in-production. The audit assesses how far each feature has traveled through the deployment pipeline.

Yes, you can check if code is wired and tested by scanning repository signals. The audit classifies features as stubbed, built-disconnected, built-wired, or built-tested based on concrete evidence.

No, the codebase audit stays strictly read-only and safety-bound. It analyzes the repository and saves the resulting build-state map and logged curator proposals to a local .harness/audits directory.

The best way to handle ambiguous feature states is a frontier escalation with cost control. The audit runs a cheap bulk pass first and escalates only ambiguous cases to a frontier model.

Generate an evidence-based report by scanning the codebase to produce a build-state map. It identifies finished, wired, tested, and built-disconnected features with evidence and suggested next steps saved to .harness/audits.