Skip to content

Program: establish long-range roadmap and release authority - #1

Draft
jenksed wants to merge 12 commits into
mainfrom
program/long-range-roadmap
Draft

Program: establish long-range roadmap and release authority#1
jenksed wants to merge 12 commits into
mainfrom
program/long-range-roadmap

Conversation

@jenksed

@jenksed jenksed commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Review-only program architecture proposal. Do not merge without owner review.

Establishes:

  • one root program authority entry point;
  • canonical machine-readable multi-horizon roadmap and evidence/current-state ledger;
  • planning lifecycle distinct from release lifecycle;
  • release-manifest and roadmap-node contracts;
  • structural program validation wired into CI;
  • stable/candidate/dev release/runtime authority as the first ACTIVE work package;
  • explicit supersession of stale pre-v1.0-tag status wording for active authorization while preserving historical evidence;
  • bounded post-v1 roadmap with Signal View NEXT and speculative hosted/team/training paths owner-gated.

No webhook product implementation is included. No stable release is promoted. No merge is authorized by this PR.

@ecc-tools

ecc-tools Bot commented Aug 26, 2026

Copy link
Copy Markdown

Analyzing 200 commits...

@ecc-tools

ecc-tools Bot commented Aug 26, 2026

Copy link
Copy Markdown

Analysis Complete

Generated ECC bundle from 11 commits | Confidence: 50%

View Pull Request #2

Repository Profile
Attribute Value
Language TypeScript
Framework Not detected
Commit Convention freeform
Test Directory separate
Changed Files (10)
Metric Value
Files changed 10
Additions 1582
Deletions 71

Top hotspots

Path Status +/-
docs/program/work-packages/WP-001-release-runtime-isolation.md added +457 / -0
docs/program/program.json added +286 / -0
scripts/validate_program.exs added +245 / -0
docs/program/README.md added +229 / -0
AGENTS.md modified +117 / -71

Top directories

Directory Files Total changes
docs/program 2 515
docs/program/work-packages 1 457
scripts 1 245
. 2 229
docs/program/schema 2 192
Analysis Depth Readiness (evidence-backed, 43%)

ECC Tools uses this to decide whether recommendations should stay at commit-history/setup guidance or expand into CI, security, harness, reference-set, AI-routing, and team backlog work.

Area Status Evidence / Next Step
Commit history Ready 11 commits sampled
CI/CD signals Ready .github/workflows/ci.yml
Security evidence Missing Add AgentShield, audit, SARIF, SBOM, or security review evidence so recommendations can cover security posture.
Harness configuration Missing Add Claude, Codex, OpenCode, Zed, dmux, MCP, plugin, or cross-harness config evidence for harness-agnostic recommendations.
Reference/eval evidence Missing Add fixtures, golden traces, reference sets, or evaluator benchmarks so deeper recommendations have regression evidence.
AI routing and cost controls Missing Add model-routing, budget, usage, or cost-control files before relying on AI-heavy automation recommendations.
Team handoff and project tracking Ready docs/program/schema/roadmap-node.schema.json
Reference Set Readiness (0/7, 0%)
Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Missing Add cross-harness, adapter-compliance, or harness-audit evidence for Claude, Codex, OpenCode, Zed, dmux, and agent surfaces.
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.
Likely Future Issues (3)
Severity Signal Why it may show up
MEDIUM CLI changes may ship without shell or end-to-end coverage 1 CLI surface paths changed; 0 CLI-focused integration or e2e tests changed
MEDIUM CI workflow changes may ship without failure-mode evidence 1 CI/test-runner paths changed; 0 CI failure-mode evidence artifacts changed
MEDIUM Dependency or CI drift could surface after merge CI/workflow files changed; no lockfile changes detected
  • CLI changes may ship without shell or end-to-end coverage: The PR changes CLI, bin, or command-entry files without touching any obvious CLI-focused integration or end-to-end tests.
  • CI workflow changes may ship without failure-mode evidence: The PR changes CI workflows or test-runner entrypoints without touching CI failure fixtures, captured logs, troubleshooting notes, or regression evidence.
  • Dependency or CI drift could surface after merge: Package or workflow changes landed without an accompanying lockfile update, which often turns into CI or release noise later.
Suggested Follow-up Work (3)
Type Suggested title Targets
PR test: add CLI coverage for bin/verify-program bin/verify-program
PR ci: add failure-mode evidence for .github/workflows/ci.yml .github/workflows/ci.yml
PR chore: refresh lockfile and validate CI after dependency updates .github/workflows/ci.yml
  • test: add CLI coverage for bin/verify-program: Backfill CLI coverage before another command-surface change lands on the touched paths.
  • ci: add failure-mode evidence for .github/workflows/ci.yml: Backfill CI failure-mode evidence before another workflow or test-runner change lands on the touched surface.
  • chore: refresh lockfile and validate CI after dependency updates: Package or workflow changes without a lockfile refresh tend to turn into noisy follow-up fixes after merge.

Copy-ready bodies

test: add CLI coverage for bin/verify-program

## Summary
- Add shell, CLI, or end-to-end coverage for the recently changed command surface.

## Why
- Backfill CLI coverage before another command-surface change lands on the touched paths.

## Touched paths
- `bin/verify-program`

## Validation
- Add or extend shell, CLI, or end-to-end coverage for the changed command surface.
- Exercise the user-facing command invocation and expected exit/output behavior.

ci: add failure-mode evidence for .github/workflows/ci.yml

## Summary
- Add CI failure-mode evidence for the recently changed workflow or test-runner surface.

## Why
- Backfill CI failure-mode evidence before another workflow or test-runner change lands on the touched surface.

## Touched paths
- `.github/workflows/ci.yml`

## Validation
- Add or update a CI failure fixture, captured failing log, troubleshooting note, workflow dry-run evidence, or regression test for the changed CI/test-runner behavior.
- Run the affected workflow or test-runner entrypoint locally or in CI and record pass/fail evidence.

chore: refresh lockfile and validate CI after dependency updates

## Summary
- Refresh the lockfile and rerun CI after the dependency or workflow changes in this PR.

## Why
- Package or workflow changes without a lockfile refresh tend to turn into noisy follow-up fixes after merge.

## Touched paths
- `.github/workflows/ci.yml`

## Validation
- Refresh the lockfile in the same package manager used by the repo.
- Run the repo typecheck / test / CI entrypoints that depend on the updated package graph.
Generated Instincts (5)
Domain Count
git 1
code-style 3
testing 1

After merging, import with:

/instinct-import .claude/homunculus/instincts/inherited/switchyard-instincts.yaml

Files

  • .claude/ecc-tools.json
  • .claude/skills/switchyard/SKILL.md
  • .agents/skills/switchyard/SKILL.md
  • .agents/skills/switchyard/agents/openai.yaml
  • .claude/identity.json
  • .codex/config.toml
  • .codex/AGENTS.md
  • .codex/agents/explorer.toml
  • .codex/agents/reviewer.toml
  • .codex/agents/docs-researcher.toml
  • .claude/homunculus/instincts/inherited/switchyard-instincts.yaml

ECC Tools | Everything Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant