Curator contract, registry, and internal/curator package #19
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#19
Reference in new issue
Block a user
Stand up internal/curator as a package in its own right: the typed curator contract, the owning registry that controls registration and discovery, and the definition of a curator's declared shape (check-in interval, tool set, attached memory engine).
Acceptance Criteria
internal/curator owns a typed contract exposing real curator operations plus start/health/stop. A registry controls registration, discovery, and shutdown ordering, and defines failure isolation. Curators receive a narrow typed registrar and only the host services their declared capability requires -- never *daemon.Daemon or an untyped hook map. internal/plugin/architecture_test.go recognises curator as a conforming engine family.
Close reason
Complete: internal/domain/curator (contract.go, registry.go, registrar.go) already satisfies every acceptance criterion. CuratorEngine is a typed contract with Name/Version/Manifest/Check/Pass/Bind plus embedded Lifecycle (start/health/stop). Registry (registry.go) controls Register/Start/Health/Stop with dependency-free single ownership, panic-isolated safeCheck/safePass/bindSafely. Registrar (registrar.go) is narrow and fully typed (LLMRunner, ToolBuilder, SkillStore, EventSink, Clock) -- no *daemon.Daemon, no untyped hook map, confirmed by grep. go test ./internal/plugin/... -run TestEveryEngineInterfaceHasTypedCapabilityAndFamilyOwner -v shows domain/curator.CuratorEngine PASS as a recognised conforming engine family. go test ./internal/domain/curator/... -race -count=1 is fully green. Note: package lives at internal/domain/curator (per the domain migration), not literally internal/curator as the title says -- that's the current architecture, not a gap.
Imported from beads
archie-core-1786637499933-386-83646cce· GitHub #407 · type feature · priority P2 · created 2026-08-08 · closed 2026-08-15