69621788ee
61 selected tests and build/lint pass. Wider rendered qualification remains in progress; this local checkpoint does not establish visual acceptance.
Job Tracker documentation
This is the entry point for the current system documentation. Job Tracker (also branded Jobjakt in some UI and deployment text) is a self-hosted job-application workspace: it combines job tracking, company context, correspondence, documents, follow-up automation, and privacy-conscious AI assistance.
System at a glance
job-tracker-ui/is a statically exported Next.js 16 shell containing the React 19, TypeScript, MUI, and React Router application.JobTrackerApi/is an ASP.NET Core 9 API using EF Core 9, ASP.NET Identity, JWT/cookie authentication, SQLite by default, and MariaDB/MySQL as the server option.tools/summarizer/is a FastAPI service for local summarisation and bounded document extraction/OCR. CV generation can route through local Ollama or an explicitly enabled Gemini/Groq provider.- Docker Compose runs the API, nginx frontend, AI service, and optional bundled Ollama. Gitea Actions builds and deploys the stack.
Documentation map
| Area | Start here |
|---|---|
| Architecture | Architecture overview |
| Frontend and UI | Frontend guide |
| Backend and API | Backend guide · API reference |
| AI | AI guide |
| Database | Database guide |
| Authentication and security | Security guide |
| Configuration | Configuration guide · Environment variables |
| Docker and deployment | Infrastructure guide |
| Tests and quality gates | Testing guide |
| Local development | Development guide |
| Product behavior | Product guide |
| Remaining work | Roadmap |
| Decisions | Architecture decisions |
| Documentation maintenance | Documentation rules |
Authority and archive
The current source code and the documents linked above are authoritative. BLOCKERS.md remains the short operator/external-dependency handoff because repository instructions refer to it directly. Historical audits, plans, reports, and the pre-cleanup snapshot are under _archive/; they are evidence, not current behavior.
When documentation and code disagree, code wins and the relevant document should be corrected in the same change.