docs: correct shadow run status from evidence #10
@@ -24,4 +24,4 @@ AEG-X-011,S4,Cross,Golden vector 고도화,BLOCKED,TBD,"AGENTS.md: Algorithm cha
|
||||
AEG-VS-09-01,S4,VS-09,BuildEvidenceSnapshot,BLOCKED,TBD,"CLAUDE.md: Evidence requires Phase 1 results",PM/Architect,"Gate 2 prerequisite. Blocked by Phase 1."
|
||||
AEG-VS-10-01,S4,VS-10,GenerateSellDecision,BLOCKED,TBD,"CLAUDE.md: Model must pass PBO/DSR validation",PM/Architect,"Gate 3 prerequisite. Blocked by Phase 1."
|
||||
AEG-VS-19-01,S5,VS-19,RunFrozenBacktest,BLOCKED,TBD,"CLAUDE.md: Requires evidence from Phase 1-4",PM/Architect,"Gate 3 prerequisite. Blocked by Phase 1."
|
||||
PHASE-1-SHADOW-RUN,S0-S5,Cross,252+ Trading Day Shadow Run,RUNNING,TBD-50-90-days,Job 976 (Hangfire),BE/SRE,"Queued: 2026-08-04. Expected completion: ~2026-10-23 to 2026-11-02. No manual intervention required."
|
||||
PHASE-1-SHADOW-RUN,S0-S5,Cross,252+ Trading Day Shadow Run,BLOCKED,TBD,"docs/CURRENT/PHASE-1_SHADOW_RUN_STATUS_CORRECTION.md; logs/phase-1-execution.log; logs/host-startup-20260804-173000.log",BE/SRE,"Observed evidence contradicts RUNNING: enqueue failed with shadow_run.check_status constraint violation and HTTP 500; Job 893 was not actually started. Requires approved status-contract correction, fresh test-db rehearsal, and explicit re-queue approval."
|
||||
|
||||
|
@@ -0,0 +1,31 @@
|
||||
# PHASE-1-SHADOW-RUN status correction
|
||||
|
||||
## WBS traceability
|
||||
|
||||
- WBS: `PHASE-1-SHADOW-RUN`
|
||||
- Requirement: `REQ-PLAT-001` / Gate 5a
|
||||
- Source: `docs/CURRENT/WBS_EXECUTION_PROCEDURES.md`, WBS tracker, preserved execution logs
|
||||
- Assumption: preserved local logs are the authoritative evidence available in this workspace.
|
||||
- Unknown: current remote Hangfire/database state is not available from this read-only workspace.
|
||||
- Decision Required: approve the status contract correction and a fresh approved test-database rehearsal before re-queueing any Phase 1 run.
|
||||
|
||||
## Observed evidence
|
||||
|
||||
- `logs/phase-1-execution.log`: enqueue attempts report failure and a critical queue failure.
|
||||
- `logs/host-startup-20260804-173000.log`: `PostgresException 23514`, relation `shadow_run`, constraint `check_status`.
|
||||
- Same log: `POST /api/shadow-runs responded 500`.
|
||||
- `evidence/gate-5-signoff/PRODUCTION_READY_DECLARATION.md`: explicitly records that Job 893 was never actually started.
|
||||
|
||||
## Correct status
|
||||
|
||||
`PHASE-1-SHADOW-RUN` is `BLOCKED`, not `RUNNING`.
|
||||
|
||||
The prior RUNNING claim is not retained as execution evidence. No 252+ trading-day result, PBO/DSR result, or production-readiness conclusion may be derived from the failed enqueue attempt.
|
||||
|
||||
## Safe resolution sequence
|
||||
|
||||
1. Reconcile the active `shadow_run.check_status` constraint with the application status contract.
|
||||
2. Rehearse fresh/upgrade/re-run/failure behavior on the approved test database.
|
||||
3. Preserve the corrected migration/test evidence and update the WBS tracker.
|
||||
4. Obtain explicit approval before re-queueing Phase 1.
|
||||
5. Record a new Run ID/Job ID and only then set the WBS status to `RUNNING`.
|
||||
Reference in New Issue
Block a user