Governs canonical subjects, aliases, and relationship vocabulary. Use when deciding whether knowledge belongs in an entity or concept page and when modeling durable identities across sources.
Use the ontology contract to keep canonical subjects stable across edits, sources, and page moves. This skill decides what the subject is, what it should be called, and how it should relate to other canonical pages.
Identify the subject independent of any one source heading or temporary query. If the subject is not durable, it may not warrant its own canonical page.
Use the contract to determine:
entity_id when applicable)Do not encode dates, workflow status, or confidence labels in the canonical title.
Use only the current controlled vocabulary from
schema/ontology-entity-contract.md.
Prefer the narrowest justified relation; fall back to related_to when needed.
Check whether the case is really:
If canonical identity cannot be chosen safely, escalate.
Return: