Dynamically-defined curators: curator definitions as data #1595
Notifications
Due Date
No due date set.
Depends on
Reference: sam/archie#1595
Reference in new issue
Block a user
Sam's requirement: "Curators should be dynamically created and defined, in addition to being able to be defined in code/config/webui" and "No configuration should ever be hard-coded." Today a curator exists only if a Go package implements
curator.CuratorEngineandbootstrap.gocallscuratorRegistry.Registeron it. Nothing about a curator is definable as data, and no curator can even declare a tool set (see dependency below). This epic makes a curator definition a persisted, API-editable entity that a generic engine interprets.Scope
on_input,tools,skills,memory_engine,conversations,model,instructions(free-form),enabled. The declared shape is exactly the existingcurator.Manifestplus free-form instructions and identity -- no second shape is invented.Registrar.Tools, composes the system prompt from the definition's free-form instructions, and runs the pass through the shared model runtime with the declared tools attached.Registry.UnregisterplusRuntime.Add/Runtime.Remove, so a create/update/delete from the API applies without a daemon restart; a removed curator's in-flight pass is cancelled./api/bindings:GET|POST /api/curators,GET|PATCH|DELETE /api/curators/{id}, sameauthorizeTaskMutationguard.Non-goals
Acceptance criteria
state.protogains matching RPCs for every persisted method added (no Go interface method without an RPC), and the State Store contract doc is updated in the same change.Security and failure paths
/api/bindings(authorizeTaskMutation); no weaker path, and no chat tool that can mint curators (a curator that can create curators is privilege escalation).ToolBuilderis bound.Dependencies
Registrar.Tools(curator.ToolBuilder) has no implementation anywhere andcuratorLLMRunnerdrops tools, so no curator can declare tools today. Tracked as the first child issue here.proto/state/v1/state.protois one gRPC service fronting every ratified store contract; the persisted-definition change must extend it rather than adding a second authority.archie.db; neither the daemon nor the Gateway may open it directly.Merged from the other tracker
[EPIC] Dynamically-defined curators: definitions as data (code/config/webui). Store/API is authoritative; config is seed data.
Sam: "Curators should be dynamically created and defined, in addition to being able to be defined in code/config/webui." and "No configuration should ever be hard-coded."
Design: docs/prds/dynamic-curators.md. GitHub epic: https://github.com/samcharles93/archie-core/issues/789
Scope: definition = curator.Manifest + name/enabled/instructions, persisted and REST-editable; generic engine (one Go engine) runs any definition via Registrar.Tools + instructions; three sources (code/config/store) with the store authoritative over config; Registry.Unregister + Runtime.Add/Remove for live mutation; REST CRUD mirroring /api/bindings; no live-path constant for interval/cooldown/tools/model/memory engine.
Non-goals: fixed catalogue of curator types; chat tool that mints curators; dashboard SPA editor; forge issue tools (existing tools work #161/#140).
Load-bearing gap: no ToolBuilder implementation exists, so no curator can declare tools (registry.go:123 fails registration) and curatorLLMRunner drops tools/MaxSteps. That is phase 1.
Notes
2026-10-25: ToolBuilder exists and is wired (internal/infrastructure/toolbuilder), curatorLLMRunner forwards Tools/MaxSteps, Runtime.ReplaceDefinitions applies definitions. Remaining: trnd.2 (per-curator Add/Remove) and trnd.3 (persistence + CRUD).
Imported from beads
archie-core-trnd· GitHub #807 · body merged from the fuller GitHub #789 · type epic · priority P2 · created 2026-09-12