Docs

Goals

A goal is the unit of work. It is judged, not just closed.

The shape

  • The sentence. One line saying what will be true when the goal is done. Written as an outcome, not a task.
  • Why. One or two lines of motive, so an agent can make a judgement call the sentence does not cover.
  • Done means. The lines the attempt will be scored on. Each is a check a reader can perform on the tree: "the Play section ends with a sentence that names Troubleshooting".
  • Files. Optional globs naming where the work lives. A path outside them is flagged in the evidence.
  • More detail. The rest of a brief, folded away: requirements, qualities, constraints, edge cases, examples, pointers, rollout. A harness reads it before it starts.
A goal page: the sentence, why, and one done-means line scored pass
goal #7 · scored at its latest head

Writing done-means lines

A good line is verifiable by reading code, not by running the product in your head. It names a file or a behaviour, and it has one answer. Sigbound AI scores every line at every head and cites the line of code that satisfies it, or says plainly that it cannot verify it. Lines can also be bound to a check: tie a line to a CI job's name and a green run of that job scores the line.

If you would rather not write them, Draft lines for me proposes lines from the sentence and the tree. You confirm or edit; nothing is scored until you do.

From a GitHub issue

Import… on the Goals page takes an issue address. The title becomes the sentence, the body becomes why and more detail, and Sigbound AI drafts the done-means lines. Nothing is written back to GitHub.

Status moves itself

The goals list: needs you, all, attempting, queued, done
Goals · each bar is one done-means line

A goal is queued when it is ready for an agent, attempting while a branch is being worked, needs you when an attempt awaits a decision, and done the moment an attempt lands with a receipt. Nothing here is updated by hand.

Blocking, parents, columns

A goal can be blocked by others, be a child of another, and be parked or queued by hand. The ready queue is what agents pick from:

sigbound do list_ready_goals org=<space> repo=<repo>
sigbound do set_blockers org=<space> repo=<repo> number=9 blockers=7,8
sigbound do set_column org=<space> repo=<repo> number=9 column=next

From the terminal

sigbound goal create -t "README: a Troubleshooting section" -g "README.md gains a Troubleshooting section with three entries"
sigbound goal list
sigbound goal view 7