feat: advance phase 5 AI workflow
This commit is contained in:
+8
-21
@@ -3,7 +3,7 @@
|
||||
|
||||
Version: 1.0
|
||||
Status: Living document
|
||||
Last Updated: YYYY-MM-DD
|
||||
Last Updated: 2026-07-30
|
||||
|
||||
---
|
||||
|
||||
@@ -491,27 +491,14 @@ Security features:
|
||||
|
||||
# AI
|
||||
|
||||
The application supports multiple providers.
|
||||
The deployment selects one AI provider with the `AI_PROVIDER` environment variable. The supported
|
||||
providers are Ollama, Gemini, and Groq; OpenAI and Claude are not implemented. The .NET API calls the
|
||||
private `ai-service` through `ISummarizerService`, and the provider is never selected by an end user or
|
||||
an administrator at request time.
|
||||
|
||||
Architecture:
|
||||
|
||||
Provider Interface
|
||||
|
||||
↓
|
||||
|
||||
OpenAI
|
||||
|
||||
Gemini
|
||||
|
||||
Claude
|
||||
|
||||
Ollama
|
||||
|
||||
Future Providers
|
||||
|
||||
The admin controls available providers.
|
||||
|
||||
Users should never be locked into one AI model.
|
||||
Ollama is the privacy-first local option. Cloud providers are deployment choices for operators who
|
||||
accept their data-handling and cost trade-offs. Keep this boundary until customer demand justifies a
|
||||
more complex provider router. See `docs/decisions/ADR-004-ai-provider-system.md`.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user