sensemaking-docs-reconciler

To detect documentation drift, you can run a reconciliation audit that cross-checks your CONTEXT.md glossary, skill-registry.yaml, and README.md against artifact contracts to flag renamed skills, stale terms, and schema mismatches.

Yes, you can update glossary terms in CONTEXT.md without altering skill logic, because the reconciliation process restricts casual edits to glossary-only changes and requires explicit user approval for any registry or contract schema mutations.

Schema validation for artifact contracts involves comparing declared PRDs against templates to identify section-count inconsistencies and schema mismatches, presenting concrete evidence for your review before applying any registry mutations.

The best way to resolve vocabulary mismatches is to run a documentation reconciliation audit that challenges drift with concrete evidence, prompting ADR creation for significant architectural changes after resolving the outdated terms.

Yes, user approval is required to change skill-registry.yaml schemas during an architecture audit, as the process enforces explicit approval gates for registry and contract schema mutations to avoid side effects on execution behavior.