Desk + CLIDEVELOPMENT CANDIDATE

What is a project management harness?

Short answer

A project management harness connects the record of work to the machinery that performs and checks it. Liquid Brain combines project cards and a Windows Desk with a harness that selects eligible work, assembles context, runs configured sessions, checks results and records the outcome.

Liquid Brain Desk project board with Engineering and Operations example cards
October 17 development candidate UI with synthetic demonstration data. View full size (1920x1080)

From an intention to a reviewable result

A card describes the work: its purpose, priority, dependencies, scope and completion criteria. Desk makes that record visible alongside project views and agent terminals. A managed harness run adds the execution loop: selection, locking, context, session, checks and a recorded transition. Accepted harness work goes to VERIFY by default, leaving final acceptance to a person.

Why a board and an execution record belong together

Consider a search improvement. The card explains what should change. Its scope identifies the intended files. A configured check can exercise the changed behavior. The result then has a place to live: the card history and managed run record. A useful review asks both whether the code changed and whether the relevant evidence supports accepting it.

Choose the right way to work

Use Desk to create and organize cards, inspect Build, and open card-linked Claude or Codex sessions. Use the harness CLI when you want the configured managed-run loop. An interactive terminal session is not automatically a managed harness run and does not automatically execute its gates.

What the current candidate includes

The candidate includes searchable Kanban and List views, card editing, saved project views, planning fields, Build records, reports, task scheduling, usage coverage, import and paused restore, plus collaboration controls under validation. Graph has a known installed HTTP 503 issue. The redesigned Gantt is a separate preview. Release acceptance remains in progress.

Related questions

Does Liquid Brain replace Claude or Codex?
No. It organizes work and provides context and controls around supported agent workflows. Your configured agent still performs the requested work.
Does a successful agent session mark a card DONE?
The managed harness uses VERIFY for accepted work by default. Human acceptance remains separate from the agent saying it finished.
Does less context guarantee lower cost?
No. The product discloses bounded context and omissions. Current-product billed-token savings and equal task quality have not been established.

Related