Module workflow 

The workflow layer: what a harness’s board owes and where each piece stands — Board, Task, Lane, Dependency, Attempt, Handoff, Review (docs/ONTOLOGY.md §2.8). It sits above orchestration: a task names the profile that works it, and an attempt is one session’s run at it. Lower layers never import this one.

Modules

codec

The workflow half per harness: what a harness’s board stores, read as super::Workflow. Read side only for now; a board is written through the harness’s own door (hermes kanban).

Structs

Attempt

One run at a task: a profile claimed it, worked it in a session, and ended with a handoff, a block, or an error.

Board

One board: a queue of tasks with its own store, workspaces and dispatcher.

Comment

A note on the task’s thread: the inter-agent protocol, read by every later attempt.

Dependency

parent must be done before child is ready.

Handoff

What an attempt handed to the next reader: the closeout in prose and the evidence as data.

Review

One review step on a task.

Task

One task on a board.

Workflow

A home’s boards.

Workspace

Where a task is worked.

Enums

Lane

Where a task stands. The lanes are the board’s own (Hermes Kanban names them); every harness’s board maps onto them, and a lane the model does not know is unknown with the source word in the task’s residue.

Verdict

A reviewer’s verdict on a handoff.

WorkspaceKind

What kind of directory a task is worked in.