KindSchema answers from the built-in contract registry rather than the installed kinds #1241

Closed
opened 2026-10-27 13:39:35 +00:00 by sam · 0 comments
Owner

Surfaced by nx30.

FINDING
The kind schema used to declare a kind's Args/Result to CEL is answered from the built-in contract registry rather than from the kinds actually installed in this build/config.

WHY IT MATTERS
A kind that is not installed would be described to the checker from a built-in table, so a playbook could type-check against a kind the process cannot run, or against a version of that kind's schema that the installed build does not implement. Reject-at-load is only meaningful if the thing being checked against is the thing that will run.

WHAT TO DO
Answer from the installed kinds, or fail the load for a kind that is not installed. Establish which registry is authoritative for "installed" first, and whether the built-in table is intended as the source of truth or as a seed.

Close reason

Wrong: every kind is built in and KindSchema, Invoke and the other lookups all read the one registry map in domain/eda/module, so the checked schema is the one that runs. No separate installed-kinds set exists.


Imported from beads archie-core-bdf0 · GitHub #1103 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-13

Surfaced by nx30. FINDING The kind schema used to declare a kind's Args/Result to CEL is answered from the built-in contract registry rather than from the kinds actually installed in this build/config. WHY IT MATTERS A kind that is not installed would be described to the checker from a built-in table, so a playbook could type-check against a kind the process cannot run, or against a version of that kind's schema that the installed build does not implement. Reject-at-load is only meaningful if the thing being checked against is the thing that will run. WHAT TO DO Answer from the installed kinds, or fail the load for a kind that is not installed. Establish which registry is authoritative for "installed" first, and whether the built-in table is intended as the source of truth or as a seed. ### Close reason Wrong: every kind is built in and KindSchema, Invoke and the other lookups all read the one registry map in domain/eda/module, so the checked schema is the one that runs. No separate installed-kinds set exists. --- _Imported from beads `archie-core-bdf0` · GitHub #1103 · type bug · priority P2 · created 2026-09-21 · closed 2026-10-13_
sam added the mediumbug labels 2026-10-27 13:39:35 +00:00
sam self-assigned this 2026-10-27 13:39:35 +00:00
sam closed this issue 2026-10-27 13:39:35 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1241