cesnimda
5.5 KiB
Dependencies, source authority and entry gates
28 October 2026. GJ-00 research is authorized by the current owner instruction; no implementation approval is inferred.
Verified development baseline
Local HEAD and remote refs/heads/test/cv-integration-acceptance both: 4a8c907d70cbed235728f7d690b5409e72b93abe. Existing development ancestry includes CV-import ef425c288b38ae0e91dcc216a5c8b6c02c433ab5, CV-UX 4a0af62 and QA remediation 89974a257e4192b3d93779000a7df6998afc4051; ancestry is checked in the GJ-00 evidence lane. main is not this planning base.
Current authority order: CV-QA acceptance, Phase 10 handoff, CV-QA regression record, architecture, Phase 10 requirements, roadmap, TODO, operator blockers. Older Phase 7/9 decisions and roadmap continuations retain historical scope; they cannot override the newer bounded CV-QA decision.
The 27 October acceptance grants CONDITIONAL GO for implemented model-independent CV import/development review. Phase 10 is candidate assessment/planning only, broad cleanup implementation NO-GO; no unused deletion candidate is verified. Preserve 57 functionality groups and 33 routes, older-run review/accept paths and redirects. Human/device/AT/native-language/contrast/print qualification remains open; live CV-model compatibility/accuracy blocked; production NO-GO. Reported prior totals (backend1336, frontend995, ordinary browser364, separate configurations53, real import7, MariaDB80, Python90) are historical report claims, not rerun by GJ-00, and overlap rules remain intact.
No completed PRODUCT-REVIEW-01 decision or initiative entry approval was found in current docs/roadmap and the supplied pack. Absence is a gate, not permission. Request a concrete review artefact with scope, baseline, unresolved debt and authorized next stage.
Independent decisions
| Gate | Current disposition | Evidence needed / responsible owner |
|---|---|---|
| GJ-00 safe planning/research | GO | Current instruction; documentation-only output |
| GJ-00 design review | CONDITIONAL GO | Proposed architecture complete enough for review; settle listed rights/data/acceptance qualifications |
| Phase 10 entry/completion as applicable | NOT SATISFIED for global implementation | Development owner records candidate-specific scope/preservation acceptance and required handoff; this plan cannot close it |
| PRODUCT-REVIEW-01 | NOT ESTABLISHED | Product owner publishes signed decision and approved global scope/order |
| INT-GLOBAL-JOBS-01 implementation scope | NO-GO | Owner approves implementation and issues GJ-01 instruction after applicable prior gates |
| GJ-01 current execution | NO-GO | All preceding entries plus fresh accepted development source; no automatic continuation |
| Country live providers | Separate, blocked/conditional | Per-source grants, credentials, lifecycle and bounded live tests; see rights matrix |
| UI language support | EN/Bokmål source support only | Coverage checks + native QA; Swedish and other locales require actual implementation/qualification |
| Geography/occupation imports | Not qualified | Exact artefact versions/hashes/licences, mappings and benchmark approval |
| Hosted MariaDB CI | Inherited blocker | Isolated runner qualification; current workflow explicitly fails closed before DB execution |
| Live AI | BLOCKED | Independent artifact/environment/security/semantic qualification and owner authorization |
| Main merge / production | NO-GO / not authorized | Independent release owner action; never implied by stage pass |
Stage dependency order
GJ-00 → entry approvals → GJ-01 preferences/i18n → GJ-02 geography → GJ-03 occupations → GJ-04 providers → GJ-05 UI → GJ-06 saved searches/alerts/matching → GJ-07 operations/security → GJ-08 integrated acceptance. Stage prompts remain authoritative. Provider approvals may be pursued independently; an unavailable UK/FINN connector does not block truthful manual/external fallback or a qualified NO/SE source, but blocks any complete live UK/full FINN claim.
Each later branch starts from the latest accepted integration-complete predecessor history, not this old baseline or main. Recheck Git ancestry, source hashes, acceptance scope and gates at entry. Keep approved missing-provider scope explicit rather than declaring an unconditional three-country live-search GO.
Workspace and publication boundaries
At entry the checkout had unrelated tracked changes to .gitignore, AGENTS.md, docker-compose.dev.yml, plus untracked tool/security/Graphify files and supplied docs/planning/. Preserve them; do not reset/stash/delete or commit them indiscriminately. Created the specifically authorized planning branch after local/remote collision check. Only docs/global-jobs/00/ and the supplied docs/planning/global-jobs-prompts/ are eligible for this planning commit. Existing application source is unchanged.
Remote: origin, https://git.cesnimda.uk/cesnimda/jobtrackingapp.git. Inspected workflows: push deployment targets main; planning branch is outside that trigger and MariaDB branch allowlist; maintenance/backup dispatch is not invoked. No force push, PR, merge or deployment. Verify remote branch HEAD after push and retain exact publication identity in the completion report/evidence record.