cto/.sot/03-PROTOCOLS/CTO-CASE-SPARK-ENDPOINT-CONFIG-ISSUES.md
2026-05-31 22:21:47 -04:00

3.3 KiB

title status lifecycle_classification owner created last_reviewed core_promotion_status route
CTO Case Spark Endpoint Config Issues draft sot jp 2026-06-01 2026-06-01 not-promoted cto

CTO Case Spark Endpoint Config Issues

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

CTO-WORK-030 - Spark Local Provider Endpoint Config

Status: blocked.

Supply explicit Spark OpenAI-compatible endpoint config for the selected qwen-local / qwen3.6-35b-a3b Case path, without storing endpoint secrets in SOT or commits.

Acceptance:

  • CTO_HARNESS_CASE_LOCAL_BASE_URL is supplied at runtime for the real Qwen Case Stage 2 retry.
  • Missing endpoint config blocks before case_process_started.
  • Missing endpoint config writes backend/provider-local-config-unavailable.txt.
  • Endpoint values are not written to SOT, task file, argv, backend logs, report, trace, generated config, or commit.
  • Harness report proves case_model_provider: qwen-local.
  • Harness report proves case_model: qwen3.6-35b-a3b.
  • Harness report proves case_model_admission_status: admitted.
  • Harness report proves no fallback to anthropic or claude-sonnet-4-6.
  • Real Case Stage 2 pass evidence exists only through the Harness Evidence Interface.
  • A configured endpoint alone does not validate CTO-WORK-016, CTO-WORK-020, CTO-WORK-022, or CTO-WORK-028.
  • No Target Repository path may be inspected or copied.
  • Same-run fake baseline comparison remains required for any pass claim.
  • CTO-WORK-016 remains blocked until real Case Stage 2 pass evidence exists.
  • CTO-WORK-022 remains blocked until explicit endpoint config and real Case Stage 2 pass evidence exist.

Blocked by:

  • Spark endpoint availability.
  • Runtime-safe way to provide CTO_HARNESS_CASE_LOCAL_BASE_URL without recording secret values.

Current evidence:

  • Non-secret readiness check on 2026-06-01 showed CTO_HARNESS_CASE_LOCAL_BASE_URL=missing.
  • Existing Hermes harness blocks missing local provider config before case_process_started.

Hermes Case Qwen Loop Evidence - 2026-06-01

  • Hermes commit: 6c453ee Add Case Qwen loop entrypoint.
  • New command: harness/evals/case-qwen-loop.sh --json.
  • The command sets fixed non-secret Case/Qwen routing knobs for qwen-local / qwen3.6-35b-a3b.
  • The command requires CTO_HARNESS_CASE_BIN and CTO_HARNESS_CASE_MODEL_ADMISSION_FILE from the caller.
  • The command delegates to run-case.sh --engine case so runtime artifacts keep the Harness Evidence Interface shape.
  • The command must not print CTO_HARNESS_CASE_LOCAL_BASE_URL.
  • Focused validator passed: python3 harness/runner/validate-case-provider-adapter.py --harness-root harness --json.
  • Focused validator artifact: /home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022022Z-r1-string-slugify-2694767.
  • Pre-merge aggregate validator passed: harness/evals/health.sh --json.
  • Pre-merge aggregate validator artifact: /home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022036Z-r1-string-slugify-2695716.
  • Post-merge aggregate validator passed: harness/evals/health.sh --json.
  • Post-merge aggregate validator artifact: /home/svrnty/.hermes/profiles/cto-planb/harness-runs/20260601T022100Z-r1-string-slugify-2697229.
  • CTO-WORK-030 remains blocked until CTO_HARNESS_CASE_LOCAL_BASE_URL is supplied at runtime and a real Stage 2 pass report exists.