audit: allow explicit local provider endpoints
CI / test (push) Successful in 13s
CI / test (pull_request) Successful in 13s

This commit is contained in:
m
2026-08-17 11:21:06 +03:00
parent bcb106e0a3
commit fd61befdf1
6 changed files with 123 additions and 5 deletions
+13 -1
View File
@@ -1,6 +1,6 @@
# Assistant project status
Audit date: 2026-08-17. Active implementation: DEV-000059 revision 1.
Audit date: 2026-08-17. Active implementation: DEV-000060 revision 1.
## Current milestone
@@ -14,6 +14,18 @@ Audit date: 2026-08-17. Active implementation: DEV-000059 revision 1.
- DEV-000058 promoted the exact CPU `Qwen2.5-3B-Instruct-Q4_K_M` lineage to `VALIDATED/CANARY` through an authenticated, evidence-gated, append-only CAS transition. Ordinary routing still excludes it; only an explicit `AllowCanary` request can select it. All other current bindings remain `INACTIVE`.
- DEV-000059 enables that exact canary behind a fail-closed cognitive-worker flag and a 4 KiB output clamp. Five authenticated synthetic Creator requests completed through the full production path with typed usage observations, zero failures and zero API cost. The binding remains `CANARY`, not `ACTIVE`.
## Cognitive Foundation baseline
- `COGNITIVE_FOUNDATION = COMPLETED`
- `PRODUCTION_REGISTRY = RUNNING`
- `LOCAL_CPU_CANARY = WORKING`
- `CANARY_SUCCESSFUL_REQUESTS = 5`
- `ACTIVE_BINDINGS = none`
- `OPENAI_REAL_CREDENTIAL = not required / not activated`
- `NEXT_MILESTONE = Human Interaction + Intent/Evidence Semantics + Project Copilot Foundation`
DEV-000060 corrects the LLM-free production audit with an exact, fail-closed cognitive-worker environment allowlist. Non-secret local provider endpoint variables are permitted only by name; plaintext credentials remain prohibited and secret-file references are restricted to the existing `OPENAI_API_KEY_FILE` mechanism under `/run/secrets`.
## Delivered
- Foundation V1 is frozen and all exit criteria pass.