Purpose
Discover semantic overlaps and conflicts between documents, establish canonical sources and repair actions, and reduce the risk of duplication and inconsistency.
Core Objective
Primary Objective: Output an executable SSOT audit report (Intent Registry + Conflict Matrix + Repair Plan).
Success Criteria：
- ✅ Intent modeling completed (path_layer/artifact_type/ownership/granularity/section_intents)
- ✅ Candidate pair screening and conflict determination completed
- ✅ Conflict matrix with priorities produced
- ✅ Every P0/P1/P2 conflict has a canonical source and repair action
- ✅ Written to
docs/calibration/ssot-integrity-audit.md
Scope Boundaries
This skill is responsible for: SSOT semantic conflict auditing. This skill is not responsible for: core compliance scoring, link graph checking, code documentation alignment.
Use Cases
- full governance audit
- Conflict investigation before multi-directory document refactoring
Behavior
Phase 0: Norms Resolution (new in v1.1)
Implemented according to specs/artifact-contract.md §8 Runtime Norms Resolution Protocol §8.2 / §8.3 / §8.5: if the project specification declares ssot-integrity-audit for artifact_type path_pattern, use the project value; otherwise fall through to the skill default (docs/calibration/ssot-integrity-audit.md). This skill isfixed-path governance output, and only uses the path_pattern override mechanism.
Phase 1: SSOT Assessment
- Intent Registry
- Candidate pair screening (intent overlap + similar granularity)
- Layered similarity analysis (section/doc/entity)
- Conflict grading (P0/P1/P2/Info)
- Output canonical mapping and repair checklist
Input & Output
Input
- docs scope
- Optional conflict threshold
- Optional focus layer
Output
docs/calibration/ssot-integrity-audit.md
Restrictions
- Only output audit reports; do not automatically merge documents
- Do not automatically delete or move files
Self-Check
- Intent Registry complete
- Conflict Matrix complete
- Every conflict includes canonical source + repair action
- Report has been written to disk
Examples
- Milestone dates conflict in two roadmap documents -> P0
Appendix: Output Contract
This skill produces an SSOT Integrity Audit:
| Element | Format | Required Fields | Path Pattern |
|---|---|---|---|
| Report body | Markdown | front-matter; sections: intent classification / conflict matrix / authoritative source mapping / repair recommendations | docs/calibration/ssot-integrity-audit.md |
| Conflict matrix | Table | concept / canonical_source / divergent_sources / conflict_kind（duplicate / contradiction / drift） | "Conflict Matrix" section |
| Authoritative source mapping | Table | concept / canonical_path / superseded_paths / handoff_skill | "Authoritative Source Mapping" section |
| Machine-readable block | YAML fenced yaml ssot_conflicts: |
Each concepts[] item includes name/canonical/divergents/severity | End of report |