# GJ-00 evidence ledger

28 October 2026, Europe/Paris date. Planning/research only. Runtime feature acceptance is not claimed.

## Source and research

- Baseline: `4a8c907d70cbed235728f7d690b5409e72b93abe`, `test/cv-integration-acceptance`; `git ls-remote` confirmed the exact remote SHA. Planning branch did not exist locally/remotely before creation.
- Current architecture pointer/overview/topics, current roadmap/TODO, Phase 10 requirements, CV-QA acceptance/handoff/regression references and BLOCKERS were reviewed. No completed PRODUCT-REVIEW-01 found; Phase 10 implementation approval not established.
- Graphify query located discovery, saved-search, i18n and related owners; scoped graph-node inventory resolved imports/operations/taxonomy seams. Graph contains 10,691 nodes at entry, excludes documentation/config/deployment; not runtime proof. Some broad queries truncated or found no matching node; followed source references/graph labels rather than treating those as exhaustive results.
- Source inspection verified existing per-request NAV feed scan, substring location filtering, public-token fallback, owned saved-search/alert baseline, EN/Bokmål-only UI, HTML URL preview including FINN, technical skill tagger, owner filters/version domains and Admin system checks.
- Official public pages were browsed under the current explicit research authorization. Each substantive source is linked beside its claim in provider/geography/taxonomy/product documents with access date. Swagger UI home pages initially produced empty parsed content; JobAd Links raw OpenAPI 1.4.5 was readable. JobSearch raw Swagger fetch failed through the browser tool; current official service/dataset pages establish public CC0/no-registration status, not tested response contracts. A guessed ESCO licence URL failed; exact dataset licence qualification is left open, not inferred from that failure.
- ONS confirms county/district/parish relationships; precise town settlement polygons/IDs were not acquired. SCB simplified boundaries are explicitly unsuitable for analysis; exact spatial claims remain gated. General Kartverket terms currently state CC BY 4.0, so older NLOD assumptions were not carried forward.
- Some exploratory Windows wildcard paths did not resolve; explicit known paths were used. One nested PowerShell variable expression failed from shell expansion; replaced with a read-only Python graph-label inventory. Neither failure mutated application data or constitutes a feature test failure.

## Validation and publication

Executed documentation checks: 9/9 required outputs present; UTF-8 reads succeeded without replacement characters; 45 local Markdown targets checked, zero broken; ancestry checks for `4a8c907`, `ef425c2`, `4a0af62`, `89974a2` all passed (native exit 0). Source diff lists only the three pre-existing tracked changes; no application changes. Prompt cross-check corrected the GJ-05 branch/checkpoint labels and explicitly retained waiter/mechanic/public-administrator benchmark cases. These are documentation checks, not application test passes. Staged whitespace/scope and remote publication are checked before completion; exact publication SHA is reported to the owner.

Eligible commit paths: `docs/global-jobs/00/`, `docs/planning/global-jobs-prompts/`. Supplied prompt pack retained unchanged. Pre-existing tracked/untracked changes remain outside the index. Check staged diff before commit; do not use `git add .`.

Publish with ordinary commit/push to `planning/int-global-jobs-00`, then `git ls-remote` exact equality. Completion report provides publication SHA; a commit cannot contain its own hash. No PR or main/deploy workflow action is requested. Post-publication evidence may use a second docs-only checkpoint, with both SHAs reported.

## Lanes not executed

## Publication result

Planning content committed locally as `2c38d40c9213aa511684910bce57b691435a9930`. Staged whitespace check passed; an assertion verified exactly 23 documentation files under the two allowed paths. Two ordinary push attempts failed because `git.cesnimda.uk:443` was unreachable; a subsequent remote-head read also failed. **Push BLOCKED; remote publication NOT VERIFIED.** No force push or alternate remote was attempted. Retry `git push -u origin planning/int-global-jobs-00` when connectivity returns, then compare `git rev-parse HEAD` with `git ls-remote --heads origin refs/heads/planning/int-global-jobs-00`. The later documentation-only publication-status commit records this failure; its hash is supplied in the completion report.

## Unexecuted runtime lanes

Backend/frontend/browser/contract/MariaDB/Python suites: **NOT RUN** for this docs-only stage. Prior acceptance counts are referenced historically only. No live advertisement query/detail/feed call, provider credentials, consumer registration, commercial approval, taxonomy/geography data import, benchmark/load test, physical device/AT/native-language check, live-model inference, hosted CI qualification, deployed-identity check or production operation. Researching documentation is not a live provider contract pass. No Graphify rebuild: application code unchanged and docs are excluded from its code-only build scope.