ss-bs-auditing-project

You can detect drift by running a project auditing workflow that re-evaluates bootstrap artifacts for incoherence, performs cross-file coherence checks, and uses stage-by-stage discovery audits to identify stale documentation after refactors.

Spec-driven drift detection is an auditing process that re-evaluates bootstrapped project artifacts like architecture, domain models, and glossaries to find inconsistencies, enforcing guardrail-driven workflows with prescriptive suggestions for evidence-based updates.

Audit stale artifacts by running stage-by-stage discovery audits across constitution, architecture, testing, glossary, domain model, design, and memory files, updating each artifact with a dedicated commit so changes remain selective and reviewable.

Yes, quarterly health checks audit documentation per stage with SUGGEST enabled, generating prescriptive recommendations you can accept or decline, while per-stage commits ensure changes remain selective and reviewable rather than forcing full rewrites.

The best approach is running a pre-audit coherence pass to triage issues by severity, followed by stage-by-stage discovery audits, and a post-audit coherence re-check to verify what was resolved, what remains, and what new findings were introduced.

You should avoid stage-by-stage project auditing on newly bootstrapped projects with no prior artifacts, as this workflow requires existing constitution, architecture, and domain model files to evaluate drift, incoherence, and improvement opportunities.