asdlc-registry-core-contracts

Trace SkillMeat registry contract changes and validate migration safety gates.

Updated May 3, 2026
One-click install
npx skills add https://github.com/miethe/boxbrain-2 --skill asdlc-registry-core-contracts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asdlc-registry-core-contracts
Source: https://github.com/miethe/boxbrain-2/tree/main/.claude/skills/asdlc-registry-core-contracts
Command: npx skills add https://github.com/miethe/boxbrain-2 --skill asdlc-registry-core-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents regressions when modifying SkillMeat's artifact identity, versioning, repository, manifest, search, content-resolution, and database-routing contracts.

Core Features & Use Cases

  • Kernel Boundary Mapping: Identifies the real modules, interfaces, implementations, consumers, and tests behind the doctrine-level Registry Core concept.
  • Change Safety Gates: Guides additive versus breaking changes, local and enterprise repository parity, Alembic migration checks, schema-drift protection, and compatibility-registry updates.
  • Enterprise Routing Protection: Prevents services from bypassing RepositoryFactory and accidentally using local SQLite instead of enterprise PostgreSQL.
  • Use Case: Before changing a repository interface or database migration, use this Skill to trace implementers and consumers, validate edition routing, inspect migration heads, and document evidence from targeted tests.

Quick Start

Use the asdlc-registry-core-contracts skill to review the planned change, identify affected contracts and consumers, apply the relevant safety gates, and report required tests and compatibility actions.

Frequently Asked Questions about asdlc-registry-core-contracts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent schema drift when modifying repository interfaces?

To prevent schema drift when modifying repository interfaces, you must apply interface tracing, validate Alembic migration heads, and document evidence from targeted pinning tests to ensure local and enterprise repository parity.

How do I validate Alembic migration heads before deploying core contract changes?

You validate Alembic migration heads by applying change safety gates that inspect migration heads, protect against schema drift, and ensure compatibility-registry updates before modifying core database-routing contracts.

What is the best way to trace consumers of artifact identity and versioning contracts?

The best way to trace consumers of artifact identity and versioning contracts is through kernel boundary mapping, which identifies the real modules, interfaces, implementations, and tests behind the Registry Core concept.

How do I check if a core contract change is additive or breaking?

You check if a core contract change is additive or breaking by applying change safety gates that guide additive versus breaking changes, requiring interface tracing and compatibility-registry evidence for public-surface compatibility.

Do I need targeted pinning tests for local and enterprise repository parity?

Yes, you need targeted pinning tests to verify local and enterprise repository parity, prevent services from bypassing RepositoryFactory, and document compatibility-registry evidence for core contract modifications.