Skip to content

docs: evaluate optional visual cockpit (emdash) over headless pipeline - #31

Merged
robercano-ghbot merged 2 commits into
mainfrom
feat/issue-10-cockpit-evaluation
Jul 2, 2026
Merged

docs: evaluate optional visual cockpit (emdash) over headless pipeline#31
robercano-ghbot merged 2 commits into
mainfrom
feat/issue-10-cockpit-evaluation

Conversation

@robercano-ghbot

Copy link
Copy Markdown
Collaborator

Summary

Adds docs/COCKPIT_EVALUATION.md, a decision note evaluating emdash (YC W26, Apache-2.0) — a desktop GUI for running multiple coding agents in parallel git worktrees — against this harness.

Covers:

  1. Integration seam — both tools drive git worktrees directly; the rule is one driver per session (either emdash or the harness, never both concurrently against the same repo).
  2. CI-check surfacing — depends on server-side gates (a GitHub Actions workflow publishing checks via the Checks API), not on the GUI itself. This harness's gates currently run locally and don't post GitHub checks; that's the scope of the separate CI-workflow effort (issue Run the self-adapter gates in CI on PRs to this repo #25).
  3. What the harness keeps that no GUI replaces — gates-as-code, defined roles (orchestrator/implementer/reviewer/test-runner), adversarial multi-lens review, and headless autonomy (cron poll + scheduled wakeups, no human/GUI required).
  4. Recommendation — emdash as an optional cockpit (front-end); this harness as the engine (orchestration + gating substrate). Complementary, not substitutes. No code integration recommended at this time.

This is a documentation/decision note only — no code changes.

Closes #10

🤖 Generated with Claude Code

https://claude.ai/code/session_011HosUeuSvhetARboEfDW6K

robercano and others added 2 commits July 2, 2026 08:35
Adds a decision note assessing emdash (YC W26 worktree-based agent GUI)
against this harness: where the two overlap (worktree management),
the coordination rule needed to avoid collisions, why CI-check
surfacing depends on server-side gates (issue #25) rather than the
GUI, and what gates-as-code / roles / adversarial review / headless
autonomy the harness provides that no cockpit replaces. Recommends
emdash as an optional front-end, not a substitute for the engine.

Closes #10

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011HosUeuSvhetARboEfDW6K
@robercano-ghbot
robercano-ghbot merged commit fa1424e into main Jul 2, 2026
6 checks passed
@robercano-ghbot
robercano-ghbot deleted the feat/issue-10-cockpit-evaluation branch July 2, 2026 17:05
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.

Evaluate an optional visual cockpit (e.g. emdash) as a front-end over the headless pipeline

2 participants