cto/.sot/03-PROTOCOLS/CTO-CASE-STAGE6-REPEATABILITY-REFRESH-ISSUES.md
2026-06-02 06:48:26 -04:00

4.1 KiB

name status lifecycle_classification owner created last_reviewed core_promotion_status source
CTO Case Stage6 Repeatability Refresh Issues validated sot jp 2026-06-02 2026-06-02 not-promoted .sot/03-PROTOCOLS/CTO-CASE-STAGE6-REPEATABILITY-REFRESH-PRD.md

CTO Case Stage6 Repeatability Refresh Issues

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

Stage 6 repeatability refresh.

Issue: CTO-WORK-081 - Stage 6 Repeatability Refresh PRD

Type: AFK.

Status: validated.

Acceptance:

  • Register CTO-WORK-081, CTO-WORK-082, CTO-WORK-083, and CTO-WORK-084.
  • Define pinned inputs for r1-src-string-slugify and r1-slugify-punctuation.
  • Require report shape, event validity, allowed-path compliance, failure closure, failure matrix coverage carry-forward, artifact completeness, forbidden-action closure, operator acceptance, approval provenance, source admission freshness, target validation, and Target Repository read-only status.
  • Require fake lane evidence, Codex blocked rationale, and Pi blocked rationale.
  • Require computed repeatability_status as pass, blocked, or fail.
  • Require repeatability_count: 2 for success.
  • Require runtime default activation: false.
  • Require core_promotion_status: not-promoted.
  • Forbid new Case mutation, default activation, Core promotion, target mutation, push, merge, deploy, close, PR open, issue close, publication, vendor-source mutation, external developer repository mutation, unowned repository mutation, endpoint exposure, secret exposure, credential exposure, and raw Target Repository content exposure.

Issue: CTO-WORK-082 - Stage 6 Repeatability Harness Route

Type: AFK.

Status: validated.

Blocked by: CTO-WORK-081.

Acceptance:

  • Extend validate-case-stage6-real-refresh.py.
  • Keep compatibility fields real_stage5_pass_report and real_stage5_proof.
  • Add repeat_stage5_pass_report and repeat_stage5_proof.
  • Add real_stage5_passes.
  • Add repeatability_required: 2.
  • Add repeatability_count: 2.
  • Add repeatability_status: pass.
  • Add repeatability_passed: true.
  • Add runtime_default_activation: false.
  • Add core_promotion_status: not-promoted.
  • Focused validator passes.
  • Aggregate Harness health passes before commit and after merge.

Issue: CTO-WORK-083 - Hermes Repeatability Control Summary

Type: AFK.

Status: validated.

Blocked by: CTO-WORK-082.

Acceptance:

  • Hermes Control Surface summary reads the extended real-governed refresh artifact.
  • Summary exposes repeatability_count: 2.
  • Summary exposes repeatability_status: pass.
  • Summary exposes candidate_default_repeatability_eligible: true.
  • Summary exposes runtime_default_activation: false.
  • Summary exposes core_promotion_status: not-promoted.
  • Summary keeps Codex lane and Pi lane blocked with rationale.
  • Summary validator checks repeatability fields.

Issue: CTO-WORK-084 - Stage 6 Repeatability Evidence Closeout

Type: AFK.

Status: validated.

Blocked by: CTO-WORK-083.

Acceptance:

  • Evidence references Hermes implementation commit 05ab2ff.
  • Evidence references Hermes merge commit 40b0d9a.
  • Evidence references comparison artifact /home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260602T104507Z-stage6-real-governed-refresh/stage6-real-governed-refresh-comparison.json.
  • Evidence references WebUI summary artifact /home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260602T104552Z-run-all-fake-2738738/webui-summary.json.
  • Evidence records repeatability_count: 2.
  • Evidence records repeatability_status: pass.
  • Evidence records runtime_default_activation: false.
  • Evidence records core_promotion_status: not-promoted.
  • Evidence records no target repository mutation attempted.
  • Evidence records no forbidden action.
  • CTO validator checks PRD, issues, evidence, and Workboard statuses.

Granularity Check

This sequence separates planning, Harness evidence refresh, Control Surface exposure, and closeout evidence. The Hermes code shipped the Harness and summary changes together because the summary is a read-only projection over the same artifact.