c-02-memory-quality-control

To validate memory quality before a code commit, run a pre-commit workflow that applies task-start drift checks, verifies onboarding completeness for new sources, and generates a closeout integrity report to gate releases.

Memory drift assessment evaluates repo-wide memory trust before planning work. You need it during task-start phases to prevent relying on stale or incomplete memory when coordinating development and release workflows.

Verify onboarding completeness by running a pre-code-commit check that catches new sources lacking sidecars. This missing-onboarding verification ensures all new context is properly registered before memory commits.

Yes, you can gate releases using a closeout memory-quality report that validates integrity and style. If memory quality is not clean, the workflow provides explicit next actions to guide remediation before releasing.

When memory quality checks fail during pre-commit verification, the workflow provides explicit next actions to guide remediation. This prevents stale or incomplete memory from gating your code commit and release process.

Yes, memory quality control works without external dependencies to perform integrity checks. It autonomously assesses drift, verifies onboarding completeness, and enforces closeout reports across the repository context.