feat(cognitive): add local provider registry and discovery
This commit is contained in:
+11
-2
@@ -1,6 +1,15 @@
|
||||
# Assistant project status
|
||||
|
||||
Audit date: 2026-08-16. Active implementation: DEV-000053 revision 1.
|
||||
Audit date: 2026-08-17. Active implementation: DEV-000056 revision 1.
|
||||
|
||||
## Current milestone
|
||||
|
||||
**Provider-neutral Cognitive Architecture + Local AI integration.**
|
||||
|
||||
- Docker production baseline at `9e99a04c…` is completed and healthy.
|
||||
- The OpenAI integration is a bootstrap adapter only. Real OpenAI credentials and production traffic are intentionally deferred.
|
||||
- The current milestone integrates one normally available local CPU provider and one opportunistic local Ollama/GPU provider through typed discovery, health and routing boundaries.
|
||||
- Discovery never activates a provider, model or binding. Until a later benchmark and explicit promotion task, all discovered bindings remain `INACTIVE` and production remains fully LLM-free.
|
||||
|
||||
## Delivered
|
||||
|
||||
@@ -20,7 +29,7 @@ Audit date: 2026-08-16. Active implementation: DEV-000053 revision 1.
|
||||
|
||||
## Remaining work requiring a new task decision
|
||||
|
||||
1. **Cognitive provider:** the cognitive worker intentionally remains the deterministic fake. Selecting a real model/provider, data policy and allowed proposal contract requires a separate capability/architecture decision; it must not gain canonical mutation authority.
|
||||
1. **Cognitive qualification and promotion:** DEV-000056 discovers and registers local providers/models without activation. A later benchmark decision must establish demonstrated capabilities and explicitly promote exact binding revisions through `EVALUATING → VALIDATED → CANARY → ACTIVE`.
|
||||
2. **Product breadth:** notification delivery is the only accepted real external operation. Any additional operation needs its own proposal, authority model, idempotency/reconciliation semantics and Capability binding.
|
||||
3. **Artifact and Epistemics product behavior:** their ownership boundaries exist, but no product task has yet specified durable user-facing workflows for them.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user