Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions spec/_projects/kitchen-sink-harness-mode/BUSINESS-RULES.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# Rules — Kitchen Sink: Harness Mode

[Spec](SPEC.md) · [Decisions](DECISIONS.md) · **Rules** · [Plan](PLAN.md)

What every epic under this project obeys. Each rule has exactly one owner: the epic that
implements and proves it. Every other epic inherits it.

None yet. A rule lands here when it binds two epics; one that binds only FIX-1907 is FIX-1907's.

**No epic may** build orchestration across harnesses here. That is Shift Manager's.
15 changes: 15 additions & 0 deletions spec/_projects/kitchen-sink-harness-mode/DECISIONS.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Decisions — Kitchen Sink: Harness Mode

[Spec](SPEC.md) · **Decisions** · [Rules](BUSINESS-RULES.md) · [Plan](PLAN.md)

Calls that bind more than one epic under this project. A call one epic owns lives in that epic's
spec. No `PD` card yet: the project has one epic, so no call binds a second.

## Decided once

None yet. The first entry lands when an epic settles a question a sibling would otherwise have to
answer again.

## Open

None.
19 changes: 19 additions & 0 deletions spec/_projects/kitchen-sink-harness-mode/PLAN.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# Plan — Kitchen Sink: Harness Mode

[Spec](SPEC.md) · [Decisions](DECISIONS.md) · [Rules](BUSINESS-RULES.md) · **Plan**

The order the epics run in, what each hands the next, and what is deliberately not next. Status is
[the epics table](SPEC.md)'s; this page does not repeat it.

## The arc

One lane, no bar yet. The arc becomes a figure when a second epic gives it an order to show.

| Lane | Consumes | Releases |
|---|---|---|
| **harness mode** · FIX-1907 ([its plan](https://github.com/fixpoint-labs/flow-state-dev/tree/main/specs/epics/FIX-1907/PLAN.md)) | The four harness integrations as they stand; FIX-1701's shared task-scope reader where it has landed; FIX-1735's Claude Code item streaming (Done) | Kitchen Sink as a harness picker, with sessions and task sync per harness, and the gaps it finds in each integration |

## What is deliberately not next

- **Orchestration across harnesses.** Shift Manager owns it; it does not come here later.
- **A fifth harness.** Only the four named are in scope.
53 changes: 53 additions & 0 deletions spec/_projects/kitchen-sink-harness-mode/SPEC.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# Kitchen Sink: Harness Mode

**Spec** · [Decisions](DECISIONS.md) · [Rules](BUSINESS-RULES.md) · [Plan](PLAN.md)

Kitchen Sink becomes a direct test bed for each harness we support: Flow State, Codex, Claude
Code and Cursor. You pick a harness and work in that harness's own sessions. Kitchen Sink is mostly
a pass-through, but it still sets up sessions, keeps them in sync with what the harness is doing,
and keeps its tasks in sync too. Running each harness directly is how we see whether those
integrations are tight.

## The outcome

| | |
|---|---|
| **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](figures/territory.svg)

Above the fence is one person using one harness directly; that is all this project builds. Below
it are the integrations it exercises and does not own. Anything across harnesses is Shift
Manager's.

## The epics — derived live 2026-10-12

| Epic | What it owns | State | Surface |
|---|---|---|---|
| [FIX-1907](https://linear.app/fixpoint-labs/issue/FIX-1907) · **harness mode** | The harness picker, sessions per harness, and session and task sync for each of the four | *in flight* (Linear: Spec Approved). Children: FIX-1914 picker, FIX-1915 Claude Code mode (both In Spec Dev); FIX-1916 Codex, FIX-1917 Cursor, adopted FIX-1185 plan tools, closure FIX-1918 (Backlog) | [`specs/epics/FIX-1907/`](https://github.com/fixpoint-labs/flow-state-dev/tree/main/specs/epics/FIX-1907) on `main` (#3162) |

0 done · 1 in flight · 0 not started. Epics are filed as the project reaches them; an unfiled one
is a `FIX-XXX · working title` placeholder that keeps its title when the real id arrives.

```mermaid
flowchart LR
R["FIX-1701 · shared task-scope reader"] -.->|"one reader for task scope"| E["FIX-1907 · harness mode"]
```

One epic so far. FIX-1701 is an issue outside this project that the three external harnesses'
task sync reads through; it is an input, drawn dashed, not part of the set. Its status disagrees
with itself: Linear still shows In Spec Review, but its PR #2569 merged on 2026-10-01.

## What this project is not

- **Not orchestration across harnesses.** Coordinating several harnesses is Shift Manager's job.
Kitchen Sink is a way to use each harness by itself.
- **Not new harness integrations.** The four named are the scope. A fifth harness is its own work.
- **Not the owner of the integrations it tests.** The harness packages, core's harness handle,
FIX-1701 and FIX-1735 live elsewhere; this project shows whether they hold.

Open inside FIX-1907, not here: what happens to Kitchen Sink's current showcase flows, and
whether they move under the Flow State mode. That is the epic's call.
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
<!-- Verbatim snapshot. Do not edit, reflow, or fold. -->

# Linear project `content`, as read

**Read** 2026-10-12 from the Linear project
[Kitchen Sink: Harness Mode](https://linear.app/fixpoint-labs/project/kitchen-sink-harness-mode-5df54957278a)
· project `updatedAt` **2026-10-12T12:27:27.820Z**

Everything below the rule is the field exactly as the API returned it, before the project-spec
mirror replaced it. What was folded into the four documents, and what was left behind, is in the
project PR's body and in the `absorbed:` line of the build report.

---

Kitchen Sink as a direct test bed for each harness we support: Flow State, Codex, Claude Code, and Cursor. It covers sessions and task sync for each harness, with no orchestration across harnesses. Epic: <issue id="faee2974-8eee-4927-ab08-3b27eaa84338" href="https://linear.app/fixpoint-labs/issue/FIX-1907/epic-kitchen-sink-harness-mode-run-flow-state-codex-claude-and-cursor">FIX-1907</issue>.
88 changes: 88 additions & 0 deletions spec/_projects/kitchen-sink-harness-mode/figures/territory.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading