cesnimda/jobtrackingapp
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(architecture): document the AI Career Assistant (Phase 5)
CI and Deploy / test (push) Failing after 1m56s
Details
CI and Deploy / deploy (push) Has been skipped
Details

Browse Source 
ai-career-assistant.md (modules, prompt flow, provider abstraction, append-only
history model, extension points, security). Master guide + roadmap Phase 5
updated with the shipped workspace and the open provider-selection extension.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
cesnimda
2026-07-18 15:26:04 +02:00
parent bb0c0feb4c
commit fd9bd3f47a
3 changed files with 104 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/implementation-roadmap.md
+10
View File
@@ -145,6 +145,16 @@ Goal: `Content Tab → Customise Tab → Preview → Export` (guide `:312`).
Goal: polish. This is the healthiest area — grounding in the structured profile is already right, and "AI never has final control" already holds.
> **AI Career Assistant SHIPPED 2026-07-18** (commits `f299d7b` backend, `bb0c0fe` frontend). A unified
> per-application **AI Workspace** tab with five suggestion modules — job-analysis, career-match,
> cover-letter (6 tones), interview, application-review — each running through the existing
> `ISummarizerService`/ai-service provider abstraction and stored as **append-only history**
> (`AiInteraction`) with reuse / compare / copy / delete. Suggestion-only throughout; nothing
> auto-applies; `Markdown` renders React nodes (no HTML-injection surface). See
> `docs/architecture/ai-career-assistant.md`. **Still open:** per-request user-selectable providers
> (needs an ai-service per-request override + a configured key per provider — deployment/credential
> work, documented as an extension point); 5.2 AI usage metering (Phase 7 blocker) remains.
| # | Task | Priority | Difficulty | Dependencies | Expected value |
|---|---|---|---|---|---|
| 5.1 | **Fix `docs/00-ai-context.md` to match the code.** **Decided 2026-07-17: do NOT build the abstraction.** | **P1** | **S** | none | The doc describes a provider interface over OpenAI/Gemini/Claude/Ollama with admin control and per-user choice. Reality: one `AI_PROVIDER` env var over Ollama/Gemini/Groq. Multi-provider cloud AI also undermines the privacy moat (see `docs/research/competitors.md` §4). Revisit only if a customer asks. `docs/architecture/current.md` §9 already records the truth. |