FactoryRegistry family
factory-registry
Reusable agents and teams WTK can use to improve itself.
- Architecture role
- Governed factory agents and teams
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/factory-registry/README.mdAI Agent Factory Component Registry
Registries equip packages.The Registry Atlas shows the governed component families WTK uses to assemble packages: contracts, skills, tools, evaluators, guardrails, hooks, memory, steering, and target adapters. It does not publish complete agents or teams.
RegistryReusable component families available to package construction.
≠Catalog previewThe release contract WTK requires before complete packages become publicly available.
View catalog preview →10 records
PackagesRegistry family
product-registry
Reusable deployable product agents, teams, packages, and blueprints. These are user facing deployable assets, not WTK factory workers.
- Architecture role
- Promoted product agents, teams, and package discovery
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/product-registry/README.mdSkillsRegistry family
skill-registry
Source controlled factory skill configuration lives here. These files describe how WTK factory agents, teams, profiles, capabilities, bundles, techniques, and instructions should be assembled for local factory execution.
- Architecture role
- Reusable capabilities and operating techniques
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/skill-registry/README.mdToolsRegistry family
tool-registry
A registered tool and a reachable MCP connection do not grant host authority. Operators use wtk host tools to create generated local state at .wtk/host tool bindings.json. A binding records exact verified tool names, host platform and execu
- Architecture role
- Typed actions, connectors, MCP definitions, and receipts
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/tool-registry/README.mdGuardrailsRegistry family
guardrails-registry
Reusable safety, reliability, scope, escalation, and degraded mode policies. Package specific guardrail selections should be copied or referenced into generated packages.
- Architecture role
- Allow, deny, ask, and degraded-mode policy
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/guardrails-registry/README.mdEvaluationRegistry family
eval-registry
Reusable evaluation and qualification assets. WTK should prove package readiness, not only generate package files.
- Architecture role
- Reusable evaluators, fixtures, rubrics, and qualification gates
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/eval-registry/README.mdHooksRegistry family
hooks-registry
Reusable lifecycle hooks. Hooks may apply to factory runs, package compilation/deployment, or local/deployed runtime behavior.
- Architecture role
- Lifecycle enforcement and evidence capture
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/hooks-registry/README.mdMemoryRegistry family
memory-registry
Reusable memory provider definitions, strategies, namespace layouts, retention policy, and promotion rules. Runtime memory state does not belong here.
- Architecture role
- Governed memory strategies, namespaces, and promotion
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/memory-registry/README.mdSteeringRegistry family
steering-registry
Reusable steering content: instructions, personas, operating modes, refusal policies, and handoff patterns.
- Architecture role
- Operating modes, handoffs, personas, and refusals
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/steering-registry/README.mdTargetsRegistry family
targets
Source controlled target compiler and deployment adapter definitions. Generated target artifacts belong under .wtk/packages/<id /targets/, not here.
- Architecture role
- Target-neutral package projections and deployment adapters
- Lifecycle
- Source registry
- Qualification
- Not asserted
WTK/targets/README.md