cesnimda
4.1 KiB
4.1 KiB
JobTracker master programme progress
Updated: 2026-08-03
- Overall programme status: Active. Six packages are locally verified; eleven packages including POL-001/002 and AI-001 are implemented with automated/runtime evidence but blocked from later browser/provider/production gates; AI-002 is now in progress.
- Current work package:
AI-002— Ollama adapter and local-first provider routing (IN PROGRESS), extending the POL-002 boundary and AI-001 execution context. - Completed work packages: None are
DONE; all repository security packages still have applicable browser, provider and/or production gates. - Locally verified work: SEC-001, SEC-002, SEC-003, SEC-005A, CORE-001 and PROD-002 (
VERIFIED LOCALLY). - Implemented, verification incomplete: SEC-004, SEC-005B, SEC-008, CORE-002, BG-001, OPS-001A/B/C, POL-001/002 and AI-001 (
IMPLEMENTED — NOT VERIFIED): foundations through durable bounded AI execution pass local checks; real handlers, browser, provider, accounting and production gates remain. - Production-verified work: None.
- Blocked work: SEC-006 requires explicit internet/package-index permission; PROD-001/003/004 and REL-001 require documented production access and unfinished dependencies. Browser access was denied by the browser admin policy check; SMTP/MariaDB environments are unavailable.
- Deferred work: None. Conditional large abstractions, model deletion, multi-replica coordination and unrelated production changes remain outside current packages.
- Next five work packages: AI-002 Ollama adapter/routing; AI-003 Strategy Snapshot queue migration; AI-004 CV processing queue migration; UX-001 authentication/theme corrections; QA-001 job-analysis/keyword quality. SEC-006/007 resume after package-index permission.
- Status counts: 6
VERIFIED LOCALLY; 11IMPLEMENTED — NOT VERIFIED; 1IN PROGRESS; 16NOT STARTED; 5BLOCKED; 0DONE; 0DEFERRED. - Test status: backend 581/581; AI-001 focused queue/state/API 17/17; frontend 47/47 suites and 158/158 tests plus build; Python sidecar 18/18. Prior POL/PROD/OPS/BG/SEC/CORE evidence remains green.
- Deployment status: No deployment performed. No production migrations were run.
- Production status: Unchanged and unverified. Pre-existing Docker development services on 3000/5202 were observed and left untouched.
- Known regressions: No known regression from the implemented packages. POL-002 preserves local AI behaviour and defaults external consent off. Direct clean EF-only SQLite migration still hits the pre-existing historical blank-chain defect before the new migration; normal startup owns reconciliation. Complete usage/provider provenance remains a known pre-rollout gap.
- Outstanding security findings: JT-001 repository ownership is implemented but remains High deployment risk until migration/inventory/provider checks; production portion of JT-002; JT-006, JT-009 and associated JT-011/JT-012/JT-022 prerequisites. JT-005 owner foundation is implemented but workers remain off until persistent notification, entitlement and privacy gates. JT-007/JT-008/JT-010 repository behavior is not fully browser/provider/production verified.
Current evidence
docs/audits/audit-remediation-backlog.mddocs/audits/verification-log.mddocs/verification/sec-001-canonical-origin.mddocs/verification/sec-002-ingress-compose.mddocs/verification/sec-003-microsoft-tenant.mddocs/verification/sec-004-microsoft-identity.mddocs/verification/sec-005a-session-revocation.mddocs/verification/sec-005b-email-ownership.mddocs/verification/core-001-sqlite-provider-parity.mddocs/verification/core-002-route-uniqueness.mddocs/verification/sec-008-attachment-consistency.mddocs/verification/bg-001-tenant-workers.mddocs/verification/ops-001a-durable-operations.mddocs/verification/ops-001b-notifications.mddocs/verification/ops-001c-operation-ui.mddocs/verification/pol-001-free-pro-entitlements.mddocs/verification/pol-002-ai-privacy.mddocs/verification/ai-001-durable-ai-queue.mddocs/verification/prod-002-ai-evaluation.mddocs/work-programmes/master-work-plan.md