hermes/cto
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
0996df1bf9
cto/.sot/03-PROTOCOLS/CTO-CASE-STAGE6-CANDIDATE-DEFAULT-ISSUES.md

4.3 KiB
Raw Blame History

name tier status owner source created last_reviewed lifecycle_classification core_promotion_status description
cto-case-stage6-candidate-default-issues local draft jp .sot/03-PROTOCOLS/CTO-CASE-STAGE6-CANDIDATE-DEFAULT-PRD.md 2026-06-01 2026-06-01 planning not-promoted Child-local issue sequence for Stage 6 Case candidate-default comparison proof.

CTO Case Stage 6 Candidate Default Issues

Local planning SOT only. Not a Core Protocol. Not active Core authority.

Issue Sequence

CTO-WORK-042 - Stage 6 Candidate Default PRD

Type: AFK

Status: validated.

Blocked by: CTO-WORK-038

User stories covered: CTO Case Candidate Backend PRD stories 1, 3, 4, 5, 7, 8, 9, 10, 11, 12, 13.

What to build: Define the Stage 6 candidate-default comparison proof before implementation starts.

Acceptance criteria:

  • PRD states Stage 6 allowed mutation scope is scoped real-repo use only.
  • PRD requires Stage 5 validation before Stage 6.
  • PRD requires comparison against fake, Codex, and Pi where applicable.
  • PRD requires Harness Evidence Interface comparison, not raw backend logs alone.
  • PRD requires report shape, event validity, allowed-path compliance, failure closure, and artifact completeness comparison.
  • PRD requires current Case source admission.
  • PRD requires failure matrix coverage or explicit blocked rationale.
  • PRD requires operator acceptance after comparison proof.
  • PRD forbids treating Stage 6 as default activation, Core promotion, Runtime authorization, or permission for push, merge, deploy, close, PR open, issue close, public publication, vendor-source mutation, or unowned repository mutation.
  • Local CTO validator checks Stage 6 PRD and issue artifact.

Allowed files: CTO child workspace planning docs and local validator only.

Validator: python3 tools/validate_cto_child.py

Done evidence: PRD, issue artifact, validator JSON, clean worktree, commit.

CTO-WORK-043 - Stage 6 Harness Candidate Default Comparison Route

Type: HITL

Status: candidate.

Blocked by: CTO-WORK-042

User stories covered: CTO Case Candidate Backend PRD stories 1, 3, 4, 5, 7, 8, 9, 10, 11, 12, 13.

What to build: In /home/svrnty/workspaces/hermes/cto/harness, implement the Stage 6 candidate-default comparison route behind the existing Harness seam.

Acceptance criteria:

  • case remains disabled by default.
  • Stage 6 requires Stage 5 proof evidence before comparison.
  • Candidate-default comparison runs or imports evidence for fake, Codex, and Pi where applicable.
  • Missing comparison lane is recorded as explicitly blocked with rationale, not silently ignored.
  • Comparison output records report shape parity.
  • Comparison output records event validity parity.
  • Comparison output records allowed-path compliance parity.
  • Comparison output records failure closure parity.
  • Comparison output records artifact completeness parity.
  • Case source admission freshness is recorded.
  • Failure matrix coverage is complete or explicitly blocked with rationale.
  • Operator acceptance or rejection is recorded after comparison proof.
  • Candidate-default status is recorded as evidence only; no runtime default, Core promotion, push, merge, deploy, close, PR open, issue close, public publication, vendor-source mutation, or unowned repository mutation occurs.
  • Fake remains the default validation lane and broad health remains green after focused Stage 6 validation.

Allowed files: Hermes CTO harness comparison validator, Harness docs, and tests. WebUI, Core, Case source, vendor source, unowned repositories, critical repositories, production repositories, and external developer repositories are forbidden.

Validator: python3 harness/runner/validate-case-stage6.py --harness-root harness --json, then harness/evals/health.sh --json.

Done evidence: Stage 6 comparison report, blocked-lane rationale where applicable, source freshness proof, failure matrix coverage proof, operator outcome, artifact digests, clean worktree, commit.

Granularity Check

This is intentionally two slices: one planning route and one executable Harness comparison route. Stage 6 is not over-granular because it is the first point where Case can be discussed as candidate default, and it must separate evidence comparison from runtime default activation.