Skip to content

Project spec: Kitchen Sink: Harness Mode (never merge) - #3156

Draft
jhoffner wants to merge 3 commits into
mainfrom
project/kitchen-sink-harness-mode
Draft

jhoffner wants to merge 3 commits into
mainfrom
project/kitchen-sink-harness-mode

Conversation

@jhoffner

@jhoffner jhoffner commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Requested by Jake · project thread

Kitchen Sink: Harness Mode turns Kitchen Sink into a direct test bed for each harness we support: Flow State, Codex, Claude Code and Cursor. This PR is the project's standing spec. It is never merged and stays open for the life of the project; it is a draft so it can't be merged by mistake. As of 2026-10-12 · head 8479b6e7.

Winning when A person opens Kitchen Sink, picks any of the four harnesses, and works in that harness's sessions, with Kitchen Sink's sessions and tasks staying in step with what the harness is doing
The read Harnesses usable this way in Kitchen Sink, with session sync and task sync both shown working. 0 of 4 today; 4 of 4 is done
Now 0 done · 1 in flight · 0 not started. FIX-1907's epic spec is approved and on main; its six children are filed, none built yet
Kill line If running a harness directly in Kitchen Sink tells us nothing its own package tests don't already, the test bed is not earning its place: stop at the harnesses that found something

The territory figure did not survive this body; it renders in Spec in the links line below, and the clean image line is with the project thread for pasting.

Above the fence is one person using one harness directly; that is all this project builds. Anything across harnesses is Shift Manager's.

The epics (live table): FIX-1907 harness mode, in flight: spec approved and merged (specs/epics/FIX-1907/, #3162), children FIX-1914 to FIX-1918 plus adopted FIX-1185. One epic, so the arc has a single lane and no figure yet.

Reviewers · look here

  • Is the outcome the right finish line, and is the kill line the right reason to stop short of all four harnesses?
  • Is the fence right: one harness used directly in, orchestration across harnesses out to Shift Manager?
  • The project's earlier Linear description is kept word for word in the branch's absorbed/linear-content.md, beside the four documents.

Spec · Decisions · Rules · Plan · Linear project

How to review this

This is a project-spec: the standing outcome, the cross-epic decisions, and the live state of
one Linear project, in four documents. It is not an implementation plan, not any one epic's
objective, and not a design.

In scope to challenge:

  • The outcome — is this what the project should be driving at, and would we know if we got there?
  • Whether the project overbuilds. Each epic can earn its place while the whole is too much.
    That question can only be asked here.
  • A decision in DECISIONS.md that binds several epics, or a rule in BUSINESS-RULES.md with no
    owner or two.
  • A missing epic the outcome implies, or one listed that does not serve it.

Out of scope — owned by the epic specs below it:

  • Any single epic's objective, issue division, or internals. Those are its epic PR.
  • The figures at the pixel level, and the status in the epics table, which is refreshed as
    the project moves and is never a review finding.

Feedback in the second list is routed to the epic it concerns, not folded in here.

🤖 Generated with Claude Code

https://claude.ai/code/session_017pp7wCd87NW4BH7XVuF9Gv


Generated by Claude Code

… verbatim

Snapshot of P-FIX-50's content field as read on 2026-10-12, before the
project-spec mirror replaces it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017pp7wCd87NW4BH7XVuF9Gv
The outcome, the territory and the epics table for P-FIX-50, with one
epic (FIX-1907). Decisions, rules and the arc are at their bootstrap
shape: headings in place, no cross-epic content yet.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017pp7wCd87NW4BH7XVuF9Gv
…roved

FIX-1907's epic spec merged to main (#3162); its six children are filed.
Epics table, Now line and the PLAN lane link to specs/epics/FIX-1907/.
Flags FIX-1701's stale Linear status (PR #2569 merged).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017pp7wCd87NW4BH7XVuF9Gv
@vercel

vercel Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments
Project Deployment Actions Updated
flow-state-dev-docs Ignored Ignored Oct 12, 2026 6:56pm UTC
flow-state-dev-kitchen-sink Ignored Ignored Oct 12, 2026 6:56pm UTC
flow-state-dev-ui Ignored Ignored Oct 12, 2026 6:56pm UTC

Request Review

@jhoffner

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-31T22:58:29.725771Z 8479b6e Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Keep it up!

Reviewed commit: 8479b6e79e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

This branch has not been deployed

No deployments
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.

2 participants