hermes/cto
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Record Case Stage 3 pass evidence

Browse Source
This commit is contained in:
Svrnty 2026-05-31 23:20:24 -04:00
parent 41de06d9c9
commit ea99b0fac9
4 changed files with 25 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
.sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-ISSUES.md
View File

@ -52,7 +52,7 @@ Done evidence: PRD, issue artifact, validator JSON, clean worktree, commit.
Type: AFK Type: AFK
Status: blocked. Status: validated.
Blocked by: CTO-WORK-033 Blocked by: CTO-WORK-033
@ -79,7 +79,14 @@ Allowed files: Hermes CTO harness engine, copied-repo fixtures, focused Stage 3
Validator: `python3 harness/runner/validate-case-stage3.py --harness-root harness --json`, then `harness/evals/health.sh --json`. Validator: `python3 harness/runner/validate-case-stage3.py --harness-root harness --json`, then `harness/evals/health.sh --json`.
Done evidence: Stage 3 pass report, failure fixture reports, source non-mutation proof, clean-start proof, clean-end proof, artifact digests, clean worktree, commit. Done evidence:
- Hermes commit: `4edf5f1 Add Case Stage 3 copied repo harness proof`.
- Stage 3 pass report: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T031903Z-r1-string-slugify-3018046/report.json`.
- Stage 3 source proof: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T031903Z-r1-string-slugify-3018046/stage3-copied-repo-proof.json`.
- Final post-merge focused validator: `python3 harness/runner/validate-case-stage3.py --harness-root harness --json`.
- Final post-merge aggregate validator: `harness/evals/health.sh --json`.
- Hermes main worktree clean after fast-forward merge.
## Granularity Check ## Granularity Check

14
.sot/03-PROTOCOLS/CTO-CASE-STAGED-PROOF-GATES.md
View File

@ -130,7 +130,7 @@ Validation evidence:
## Stage 3 - Copied Repo Fixture ## Stage 3 - Copied Repo Fixture
Status: planned. Execution remains blocked until `CTO-WORK-034` produces Harness Evidence Interface pass evidence. Status: validated for copied-repo fixture proof on 2026-06-01.
Entry gates: Entry gates:
@ -153,6 +153,18 @@ Planning evidence:
- Stage 3 PRD: `.sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-PRD.md`. - Stage 3 PRD: `.sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-PRD.md`.
- Stage 3 issues: `.sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-ISSUES.md`. - Stage 3 issues: `.sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-ISSUES.md`.
Validation evidence:
- Hermes commit: `4edf5f1 Add Case Stage 3 copied repo harness proof`.
- Stage 3 pass artifact: `/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T031903Z-r1-string-slugify-3018046`.
- Stage 3 pass report status: `pass`.
- Source repository mutated: `false`.
- Copied fixture starts clean: `true`.
- Copied fixture ends clean: `true`.
- Required events passed: `true`.
- Aggregate harness health status: `pass`.
- This validates Stage 3 only. Stage 4 disposable sandbox repo remains the next proof gate.
Validator expectation: Validator expectation:
- all changes occur inside copied fixture; - all changes occur inside copied fixture;

4
WORKBOARD.yaml
View File

@ -167,6 +167,6 @@ items:
owner: "" owner: ""
- id: CTO-WORK-034 - id: CTO-WORK-034
title: Stage 3 Harness Copied Repo Fixture Route title: Stage 3 Harness Copied Repo Fixture Route
status: blocked status: validated
source: .sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-ISSUES.md source: .sot/03-PROTOCOLS/CTO-CASE-STAGE3-COPIED-REPO-ISSUES.md
owner: jp owner: ""

2
tools/validate_cto_child.py
View File

@ -1159,7 +1159,7 @@ def main() -> int:
"CTO-WORK-029": "validated", "CTO-WORK-029": "validated",
"CTO-WORK-030": "validated", "CTO-WORK-030": "validated",
"CTO-WORK-033": "validated", "CTO-WORK-033": "validated",
"CTO-WORK-034": "blocked", "CTO-WORK-034": "validated",
} }
for issue_id, expected in expected_statuses.items(): for issue_id, expected in expected_statuses.items():
checked.append(f"workboard_status:{issue_id}:{expected}") checked.append(f"workboard_status:{issue_id}:{expected}")