glam/.opencode/rules/slot-fixes-authoritative-rule.md

Rule: Slot Fixes File is Authoritative

Scope: Schema Migration / Slot Fixes

Description: The file /Users/kempersc/apps/glam/data/fixes/slot_fixes.yaml is the single authoritative source for tracking slot migrations and fixes.

Directives:

1. Authoritative Source: Always read and update /Users/kempersc/apps/glam/data/fixes/slot_fixes.yaml. Do NOT use schemas/.../slot_fixes.yaml as the master list (though you may need to sync them if they diverge, the data/fixes version takes precedence).
2. Processed Status: When a slot migration is completed (schema updated, data migrated), you MUST update the entry in slot_fixes.yaml with a processed block containing:
   • status: true
   • date: 'YYYY-MM-DD'
   • notes: Brief description of what was done.
3. NEVER DELETE: You MUST NOT delete entries from slot_fixes.yaml. Even if a slot is removed from the schema, the record of its fix MUST remain in this file with status: true.
4. Format Compliance: New slots added during migration must follow proper LinkML format conventions and use slot_uri and mappings (exact_mappings, close_mappings) that reference legitimate predicates and classes found in /Users/kempersc/apps/glam/data/ontology/.

Example of Processed Entry:

- original_slot_id: https://nde.nl/ontology/hc/slot/has_old_slot
  revision:
  - label: has_new_slot
    type: slot
  - label: NewClass
    type: class
  processed:
    status: true
    date: '2026-01-27'
    notes: Migrated to has_new_slot + NewClass. Old slot archived.