Skill registries
What you'll find here
The craik.skill_registry contract that records which reusable
skills are available to a project — project-local versus global,
precedence, and provenance.
Project-local wins.
When a project-local and global entry reference the same skill package, the project-local entry must outrank the global entry.
Entry fields
skill_package_id
scope
project or global.
Source path
Trust boundary
Numeric precedence
Active state
Provenance links
Declaration owner & timestamp
Scope discipline.
Project-scoped entries require project_id. Global entries
must omit project_id. This keeps global discovery from
being confused with project-local authority.
Precedence
Lower precedence values win. Active precedence values must be
unique.
The registry can also record precedence_order for consumers that
want a stable ordered list of active skill entry ids. Every active
entry must appear in active_entry_ids, and precedence_order must
not include inactive entries. This keeps project-local overrides and
global defaults auditable without consumers guessing which entries are
currently live.
Provenance
Every registry entry requires provenance. Discovery should preserve the source that caused a skill to enter the registry — a project skill path, a global skill path, or an evidence record captured during onboarding.