hermes/cto
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d2f574802f
cto/.sot/03-PROTOCOLS/CTO-FIRST-REAL-GOVERNED-WORKFLOW-SCOPE-CASE-EVIDENCE.md
Svrnty 4894e7235e Record approved scope Case blocker
2026-06-01 06:50:09 -04:00

2.6 KiB
Raw Blame History

name tier status owner source created last_reviewed lifecycle_classification core_promotion_status description
cto-first-real-governed-workflow-scope-case-evidence local blocked jp .sot/03-PROTOCOLS/CTO-FIRST-REAL-GOVERNED-WORKFLOW-ISSUES.md 2026-06-01 2026-06-01 planning not-promoted Child-local evidence for the approved CTO-WORK-049 src slugify Harness case and real Case no-diff blocker.

CTO First Real Governed Workflow Scope Case Evidence

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

Scope

Work item: CTO-WORK-049

Approved target:

/home/svrnty/workspaces/cortex-os/cto-stage5-target-sandbox

Approved task:

src/strings.py slugify alignment task

Harness Fix

Hermes commit:

59d4d2e Add Stage 5 src slugify case

What changed:

  • added Harness case r1-src-string-slugify
  • registered it in harness/harness.yaml
  • made the Case task contract derive filesChanged from case allowed_writes
  • kept runtime default activation false

Why it mattered:

The previous Harness case r1-string-slugify targeted root strings.py. The approved task targets src/strings.py and test_strings.py. Reusing the root case was not evidence for the approved task.

Evidence

Focused fake proof:

/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T104749Z-r1-src-string-slugify-160593/report.json

Post-merge aggregate proof:

/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T104911Z-run-all-fake-167794/report.json

Real Case approved-scope run:

/home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T104818Z-r1-src-string-slugify-163262/report.json

Observed real Case facts:

  • executable ca path was found
  • local provider config was supplied from Hermes runtime config without writing endpoint value to SOT
  • Case process started: true
  • required events passed: true
  • target repository start clean: true
  • target repository ending clean: true
  • changed files: none
  • tests passed because existing root-path tests still pass
  • Stage 5 proof failed because no approved target diff was produced

Decision

Do not mark CTO-WORK-049 validated.

Do not patch the target by hand.

Do not treat Case process start as success.

Next useful step is backend behavior diagnosis: why ca run --task exits under Harness supervision without producing the required target diff or useful stdout/stderr.

Non-Authority Notice

This record is child-local planning evidence. It does not promote CTO artifacts into Core, does not activate Case as default backend, and does not authorize any broader target mutation.