Completes the objective deletion gate for the UI Service (archie-core-8cda.5.6): go list -deps ./cmd/archie-ui now links zero banned packages -- no modernc.org/sqlite, no internal/store, gateway, channels, memory, secret, agentexec, tools, skill, yaegiutil, curator, or the workflow engine. The closure shrinks from 68 to 26 archie-core packages. Each cut is a producer-side move; no consumer-side defensive shims. - Store contracts (TaskStore family, value types, sentinels) moved from internal/store to internal/domain/storecontract -- the approved contract location per state-store-contract rev. 2d, and NOT internal/contracts: that tree is buf generate output and tools/proto.sh check deletes hand-written files there. internal/store keeps aliases; sentinel message strings are byte-identical and remain the wire contract. - Chat contracts (ChatContract, sessions, turns, streaming, commands) moved from internal/gateway to internal/domain/messaging; gateway keeps aliases. ToolCallEvent rendering helpers become gateway functions (methods cannot live on alias types). - Task vocabulary (Task, statuses, mid-run Store, Definition) split into internal/domain/workflow/task; the pipeline engine stays in package workflow with aliases, so daemon-side callers are unchanged. - overlay.DeniedKeys moved to internal/infrastructure/configuration: webui referenced the constant and that dragged the overlay SQLite store in. - webui.Server's concrete runtime handles become webui-owned view interfaces with daemon-side bootstrap adapters: channel lifecycle (internal/channels/status), MemoryStatus, CuratorStatus, and a SkillCatalog seam replacing the direct skill.DefaultRoots/CatalogRoots calls. Each degrades to an empty page when unwired. - config.SecretRef moved into internal/config (config vocabulary); internal/secret keeps an alias and Registry.Resolve absorbs the zero-value short-circuit. Docs: state-store-contract rev. 2d relocation record; ui-service-boundary deletion gate marked satisfied; ARCHITECTURE.md package map rows.
77 lines
2.7 KiB
Go
77 lines
2.7 KiB
Go
package webui
|
|
|
|
import "net/http"
|
|
|
|
// MemoryProviderHandle is the webui-owned view source for one memory
|
|
// provider: the memory page renders a name, a readiness flag, and the
|
|
// provider's tool vocabulary by name. It is deliberately narrower than
|
|
// memory.MemoryProvider -- whose GetToolSchemas returns runtime tool
|
|
// entries -- so the UI process holds the view without linking the memory
|
|
// runtime (and, transitively, the agent toolchain). Whoever owns the
|
|
// memory runtime supplies adapters at bootstrap (archie-core-8cda.5.6).
|
|
type MemoryProviderHandle interface {
|
|
Name() string
|
|
IsAvailable() bool
|
|
ToolViews() []MemoryToolView
|
|
}
|
|
|
|
// MemoryStatus is the webui-owned surface over the running memory runtime:
|
|
// the two providers the memory page renders, by role.
|
|
type MemoryStatus interface {
|
|
Builtin() MemoryProviderHandle
|
|
External() MemoryProviderHandle
|
|
}
|
|
|
|
// MemoryProviderView describes one memory provider for the dashboard.
|
|
type MemoryProviderView struct {
|
|
Name string `json:"name"`
|
|
// Role is "builtin" or "external". Archie always has a builtin provider;
|
|
// an external one is optional and configured separately.
|
|
Role string `json:"role"`
|
|
// Available reports the provider's own readiness check -- a provider can
|
|
// be configured but unusable when a binary is missing or a connection is
|
|
// down, and that distinction is exactly what an operator needs to see.
|
|
Available bool `json:"available"`
|
|
// Tools are the capabilities this provider gives the agent, by name.
|
|
Tools []MemoryToolView `json:"tools"`
|
|
}
|
|
|
|
// MemoryToolView is one tool a provider exposes to the agent.
|
|
type MemoryToolView struct {
|
|
Name string `json:"name"`
|
|
Description string `json:"description"`
|
|
}
|
|
|
|
// handleMemory reports what Archie can remember and with what.
|
|
//
|
|
// Memory is otherwise invisible: it is a set of tools handed to the model at
|
|
// discovery time, so without this the only way to know what the agent can
|
|
// recall is to read the provider source.
|
|
func (s *Server) handleMemory(w http.ResponseWriter, r *http.Request) {
|
|
if s.Memory == nil {
|
|
writeJSON(w, map[string]any{"providers": []any{}, "enabled": false})
|
|
return
|
|
}
|
|
|
|
views := []MemoryProviderView{}
|
|
if p := s.Memory.Builtin(); p != nil {
|
|
views = append(views, providerView(p, "builtin"))
|
|
}
|
|
if p := s.Memory.External(); p != nil {
|
|
views = append(views, providerView(p, "external"))
|
|
}
|
|
|
|
writeJSON(w, map[string]any{"providers": views, "enabled": true})
|
|
}
|
|
|
|
func providerView(p MemoryProviderHandle, role string) MemoryProviderView {
|
|
view := MemoryProviderView{
|
|
Name: p.Name(),
|
|
Role: role,
|
|
Available: p.IsAvailable(),
|
|
Tools: []MemoryToolView{},
|
|
}
|
|
view.Tools = append(view.Tools, p.ToolViews()...)
|
|
return view
|
|
}
|