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

docs(redesign): record production no-go and P5-14 scope

Browse Source
This commit is contained in:
cesnimda
2026-10-08 22:47:13 +02:00
parent 1095ef1d29
commit ef661983a0
5 changed files with 406 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/redesign/phase-5/OPEN_BLOCKERS.md
+1 -1
View File
@@ -53,7 +53,7 @@ Reconciled against [P4-06](../phase-4/p4-06/README.md#opendeferred-issue-reconci
**P5-13 — AI Model Semantic Qualification / AI Review UI: DEFERRED — BLOCKED / NOT QUALIFIED.** This records Connor's explicit deferral at source checkpoint `9c9157507937b3e084a7ca1e79a2ebd77d0b0928`; it does not complete P5-13 or remove its [approved requirements](PHASE5_PLAN.md#p5-13--cv-ai-review-presentation).
**Latest qualification checkpoint / sequencing — 2026-10-08:** [The bounded qualification record](p5-13-qualification/README.md) retains **NO-GO for P5-13 UI**, 0/366 real calls, 0 human reviews and unmeasured factuality. Fresh 108 focused AI / 5 revision / 2 native HTTP cases pass separately, including stale/tampered/foreign-owner safeguards and isolated Production withholding; they do not qualify a model. The Linux-engine pipe remains unavailable and optional loopback health/inventory probes timed out; no new Docker recovery was attempted or deployed target established. The candidate's Production block remains active. Connor's latest instruction schedules deployment for the **release-candidate decision after P5-15**, superseding the historical release-first ordering below. No later slice, production merge or deployment begins in this checkpoint; F04/current backup-restore/configuration/rollback/protected-CI proof remains separately required.
**Current release/P5-14 sequencing — 2026-10-08:** Connor now authorizes fresh release assessment from `1095ef1`, followed by P5-14 for implemented CV capabilities **even if release is NO-GO**. The [production decision](production-release-decision/README.md) identifies automatic deployment from `main` and records missing actual ingress/current backup-restore/configuration/rollback/protected-CI evidence. No production merge, push or deployment occurs while any critical gate is unresolved. This supersedes the qualification-only/deploy-after-P5-15 instruction and the historical release-first prerequisite below. [Qualification](p5-13-qualification/README.md) remains NO-GO for P5-13 UI: 0/366 real calls, 0 human reviews and unmeasured factuality. Deterministic API/revision/HTTP evidence is independent of semantic qualification; the Production block stays active. P5-14 excludes unimplemented AI review, retains all missing AI responsive/acceptance obligations and stops before P5-15/B07. No qualification or Docker recovery is initiated here. Every individual P5-15 change/checkpoint must later be committed and pushed.
Local configuration selects Ollama `qwen2.5:7b`; actual deployed provider/model/digest/settings remain unverified. Docker Desktop is blocked while starting its inference manager by an AF_UNIX socket reparse-point (`IO_REPARSE_TAG_AF_UNIX`) that cannot be removed/opened normally (Windows error 1920). The deeper filesystem cause remains unknown. No destructive recovery was attempted; the failed bounded rename and supported Model Runner disable/start attempts remain documented. Do not spend another checkpoint retrying Docker recovery or repeat recovery attempts during unrelated phases.