glam/.opencode/rules/linkml/no-autonomous-alias-assignment.md
kempersc 554fe520ea Add comprehensive rules for LinkML schema management and ontology mapping
- Introduced Rule 42: No Ontology Prefixes in Slot Names to enforce clean naming conventions.
- Established Rule: No Rough Edits in Schema Files to ensure structural integrity during modifications.
- Implemented Rule: No Version Indicators in Names to maintain stable semantic naming.
- Created Rule: Ontology Detection vs Heuristics to emphasize the importance of verifying ontology definitions.
- Defined Rule 50: Ontology-to-LinkML Mapping Convention to standardize mapping practices.
- Added Rule: Polished Slot Storage Location to specify directory structure for polished slot files.
- Enforced Rule: Preserve Bespoke Slots Until Refactoring to prevent unintended migrations during slot updates.
- Instituted Rule 56: Semantic Consistency Over Simplicity to mandate execution of revisions in slot_fixes.yaml.
- Added new Genealogy Archives Registry Enrichment class with multilingual support and structured aliases.
2026-02-15 19:20:09 +01:00

1.2 KiB

Rule: No Autonomous Alias Assignment

Status: ACTIVE Created: 2026-02-10

Rule

The agent MUST NOT assign aliases to canonical slot files on its own. Only the user decides which new/ slot files are absorbed as aliases into which canonical slots.

Rationale

Alias assignment is a semantic decision that determines the conceptual scope of a canonical slot. Incorrect alias assignment conflates distinct concepts. For example, membership_criteria (eligibility rules for joining) is not an alias of has_mission (organizational purpose), even though both relate to organizational governance.

What the agent MUST do

  1. When creating or polishing a canonical slot file, leave the aliases field empty unless the user has explicitly specified which aliases to include.
  2. When processing new/ files, present candidates to the user and wait for their alias assignment decisions.
  3. Do NOT delete new/ files until the user confirms the alias mapping.

What the agent MUST NOT do

  • Autonomously decide that a new/ file should become an alias of a canonical slot.
  • Add alias entries without explicit user instruction.
  • Delete new/ files based on self-determined alias assignments.