Documentation

Workflows

Workflows

The loop is four jobs. Knowledge is documentation. Ideas is ideation until ready. Work is commitments. Complete is proof. These walks are how you use them. Open one.

From a file → Knowledge

On Knowledge, Upload adds a file to the current area (or Unfiled). Hub Upload accepts files up to 25 MB.

A connected agent can upload a file too (up to 8 MB). Larger files stay on this Upload button.

Markdown notes, what we now know, are not files. They land from Complete Add this to documentation, or from the agent as a note. See Knowledge.

Explore or resume Get Started

On first project entry, Get Started offers context, a first idea and agent connection. In a populated project, Explore your project’s Knowledge opens your team’s documents. Skip for now allows manual capture without a document. Dismiss hides the checklist; the persistent Get Started control brings it back. The Tour is available on demand (Footer on desktop; the avatar menu on phone).

Connect an agent opens Settings. Completion waits for an actual successful agent request to this project. You can keep planning without an agent or repo.

Capture an idea

On Ideas, type in the bar and press Enter. The mic dictates.

The idea lands in the ranked list. Nothing becomes work until you promote it.

From a file → Ideas

Three paths into Ideas:

  • Bulk on the Ideas bar, pick a PDF or text file. If the bar already has text, extract from that text instead.
  • Knowledge Extract ideas, split a document that is already in Knowledge. Each saved idea keeps a chip back to the source. Review your ideas opens just that saved batch; choose one to develop. Empty results do not count as success, and a partial save retries only unsaved ideas.
  • Ask a connected agent to read a local markdown file and capture Ideas. Ceremony and tool names live on Agents.
Promote an idea → Work

When an idea is ready, open Develop, row click, grip Enter, or drag the grip onto the Work rail. Those paths only open the drawer. Refine, then Pressure, then Go to Work. Hub classifies Goal, spec, or ticket. You do not pick a destination on the bar.

An empty row does not become work by itself. Go to Work lands on Work as a commitment. The idea stays as a record of where the work came from.

Start a ticket

On Work, Ready to start is safe to pick up.

Claim takes ownership. Start begins the ticket. A drafting spec still blocks Start, approve it yourself first.

Same two operations as Agents Claim / Start.

Finish work with proof

Close with specific evidence, a PR, a commit, a real test run, screenshots. Capture screenshots at the full viewport. Prefer at least 1440×900 so the viewer stays sharp. Hub does not refuse a minimum size. Finished work shows on Complete.

A human Accept on Complete is extra confidence, not a gate. See Complete.

Judgment → Needs attention

When something needs a human call, it lands on Work → Needs attention.

Accept, Reject, or Retire covering work…. Agents can log a proposed Decision; only you stamp it. See Decisions.

Write back what we know

After Accept on Complete, Add this to documentation records what deployed. Summarize can draft it from the spec and its finished tickets.

That write-back is a markdown note, not a file upload. The next loop starts from what you deployed.

See also