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

docs(jobs): record discovery provenance evidence
CI and Deploy / test (pull_request) Successful in 4m16s
Details
CI and Deploy / deploy (pull_request) Has been skipped
Details

Browse Source
This commit is contained in:
cesnimda
2026-08-10 10:39:25 +02:00
parent 511a9f6795
commit 3d219eb4ac
6 changed files with 53 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/work-programmes/decisions.md
+10
View File
@@ -609,3 +609,13 @@
- **Consequences:** real-provider re-consent, provider category design, browser gates, SEC-009 deletion and production verification remain explicit blockers before `DONE`. JOBS-001 becomes the sole in-progress item.
- **User approval required:** No for status correction; any future provider-scope/re-consent rollout needs a separately reviewed package and safe account verification.
- **Reversible:** Yes. MAIL-001 can return to `IN PROGRESS` when provider mutation authority is approved and testable.
## DEC-062 — Expose only verified discovery provenance
- **Date:** 2026-08-10
- **Decision:** Treat NAV as verified because the controller itself fetches the official NAV feed; expose a stable source key/display name, label acquisition as `searched`, stamp the request retrieval time and map a deadline only from NAV's explicit `applicationDue` field. Do not infer work mode or add a one-option source filter.
- **Reason/evidence:** the previous card hardcoded NAV and an update date while the response's source field was unused. Phase 4 requires honest source/type/retrieval/deadline data and explicitly prohibits presenting inference as verification. Focused provenance/import tests and full regressions pass.
- **Alternatives considered:** derive source from listing hostname; infer remote/hybrid from title/location; add a disabled or single-option source filter; label `date_modified` as retrieval time. These would confuse derived and verified data or add controls without a real choice.
- **Consequences:** NAV cards now explain where and how the listing was obtained and preserve attribution into tracking. Missing work mode remains visibly absent rather than guessed; source filtering becomes useful only when a second real provider is implemented.
- **User approval required:** No; this is approved repository work using synthetic fixtures with no external request.
- **Reversible:** Revert `511a9f6`; no schema or stored data changes are involved.