glam/.opencode/rules/slot-fixes-authoritative-rule.md
kempersc 6e63465196 Add ImageTilingServiceEndpoint class and archive ID class
- Introduced the ImageTilingServiceEndpoint class for tiled high-resolution image delivery, including deep-zoom and transformation capabilities, with multilingual descriptions and structured aliases.
- Archived the ID class as a backwards-compatible alias for Identifier, marking it as deprecated to enforce the use of the canonical Identifier model.
2026-02-15 21:40:13 +01:00

1.3 KiB

Rule: Slot Fixes File is Authoritative

Scope: Schema Migration / Slot Fixes

Description: The file slot_fixes.yaml is the single authoritative source for tracking slot migrations and fixes.

Directives:

  1. Authoritative Source: Always read and update slot_fixes.yaml.
  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.