kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/.opencode/rules/preserve-bespoke-slots-until-refactoring.md
kempersc 80eb3d969c Add new slots for heritage custodian ontology 
- Introduced `has_api_version`, `has_appellation_language`, `has_appellation_type`, `has_appellation_value`, `has_applicable_country`, `has_application_deadline`, `has_application_opening_date`, `has_appraisal_note`, `has_approval_date`, `has_archdiocese_name`, `has_architectural_style`, `has_archival_reference`, `has_archive_description`, `has_archive_memento_uri`, `has_archive_name`, `has_archive_path`, `has_archive_search_score`, `has_arrangement`, `has_arrangement_level`, `has_arrangement_note`, `has_articles_archival_stage`, `has_articles_document_format`, `has_articles_document_url`, `has_articles_of_association`, `has_or_had_altitude`, `has_or_had_annotation`, `has_or_had_arrangement`, `has_or_had_document`, `has_or_had_reason`, `has_or_had_style`, `is_or_was_amended_through`, `is_or_was_approved_on`, `is_or_was_archived_as`, `is_or_was_due_on`, `is_or_was_opened_on`, and `is_or_was_used_in` slots.
- Each slot includes detailed descriptions, range specifications, and appropriate mappings to existing ontologies.
2026-01-27 10:07:16 +01:00

1.5 KiB
Raw Permalink Blame History

Rule: Preserve Bespoke Slots Until Refactoring

Identifier: preserve-bespoke-slots-until-refactoring Severity: CRITICAL

Core Directive

DO NOT remove or migrate "additional" bespoke slots during generic migration passes unless they are the specific target of the current task.

Context

When migrating a specific slot (e.g., has_approval_date), you may encounter other bespoke or legacy slots in the same class file (e.g., innovation_budget, operating_budget).

YOU MUST:

  • ✅ Migrate ONLY the specific slot you were instructed to work on.
  • ✅ Leave other bespoke slots exactly as they are.
  • ✅ Focus strictly on the current migration target.

YOU MUST NOT:

  • ❌ Proactively migrate "nearby" slots just because they look like they need refactoring.
  • ❌ Remove slots that seem unused or redundant without specific instruction.
  • ❌ "Clean up" the class file by removing legacy attributes.

Rationale

Refactoring is a separate, planned phase. Mixing opportunistic refactoring with systematic slot migration increases the risk of regression and makes changes harder to review. "We will refactor those later."

Workflow

  1. Identify Target: Identify the specific slot(s) assigned for migration (from slot_fixes.yaml or user prompt).
  2. Execute Migration: Apply changes ONLY for those slots.
  3. Ignore Others: Do not touch other slots in the file, even if they violate other rules (like Rule 39 or Rule 53). Those will be handled in their own dedicated tasks.