Phase 1 of dynamic curator definitions (archie-core-trnd.1): - ToolBuilder implementation resolves declared tool names from the daemon's process-wide tool registry, returning exactly the declared set and failing closed on an unknown name. - curatorLLMRunner now carries ChatRequest.Tools and MaxSteps into core.GenerateOptions and widens ChatResult with the executed tool calls so a pass can attribute its actions. - One generic DefinitionEngine interprets a Definition (Manifest + name/enabled/instructions): its pass composes instructions with the built declared tool set, runs the model loop, and records an action per tool invocation. - [[curators]] config definitions carry the Manifest shape verbatim plus name/enabled/instructions; a definition missing interval is refused, never defaulted. - Idle curators are observable: the runtime logs a debug line when Check reports not-due.
19 lines
715 B
Go
19 lines
715 B
Go
package curator
|
|
|
|
// Definition is a curator definition as data: the declared Manifest plus
|
|
// the identity, lifecycle flag, and free-form instructions the manifest
|
|
// cannot express. One generic engine (DefinitionEngine) interprets any
|
|
// definition -- there is deliberately no catalogue of curator "types" and
|
|
// no second authority beside the existing registry.
|
|
type Definition struct {
|
|
// Name is the registry key.
|
|
Name string
|
|
// Enabled gates registration: a disabled definition is seed data that
|
|
// the app layer does not register.
|
|
Enabled bool
|
|
// Instructions is the free-form system prompt for the generic engine.
|
|
Instructions string
|
|
// Manifest is the declared shape, verbatim.
|
|
Manifest Manifest
|
|
}
|