intake-audit

To normalize an existing project state without restarting, audit current baselines, results, and drafts to classify assets as trusted, reusable, or requiring review. This intake audit identifies durable gaps and produces clear next-anchor recommendations for subsequent workflow steps.

You need to audit existing baselines and drafts before a handoff when a project root contains meaningful state that should be normalized. Auditing reconciles trusted assets and identifies gaps, ensuring durable route decisions and handoff readiness for the next workflow phase.

The best way to evaluate trust in existing project artifacts is to audit them against current baselines and drafts. This process classifies each artifact as trusted, reusable with verification, or requiring review, ensuring only reliable assets inform downstream decisions.

Yes, you can use an intake audit to identify gaps in current research results. By verifying and aligning non-blank states against existing baselines and drafts, the audit highlights trusted assets and exposes gaps needing rework before the next anchor is chosen.

State normalization works effectively for a project root with mixed draft and baseline states. The intake audit assesses all existing experiments and analyses, aligning them to determine what can be trusted and what requires rework before choosing the next anchor.

A project handoff fails without reconciling existing state upfront because unverified baselines and drafts lead to duplicated work or ignored assets. An intake audit prevents this by normalizing state, classifying trust levels, and documenting durable decisions for subsequent skills.