Documentation

The loop

The loop

Knowledge is documentation. Ideas is ideation until ready. Work is commitments. Complete is proof. Then write back.

Knowledge

documentation

extract / search

Ideas

ideation until ready

Develop, then promote

Work

commitments

Needs attention / Ready

Complete

proof

write back

Restart tour walks Knowledge → Ideas → Work → Complete.

Knowledge

Project docs you search and extract from. Open a row to read it; Edit is in the drawer header for text-like files (markdown has Write / Preview). Promote nothing from here, extract into Ideas, then decide. When work deploys, write what you now know back into an area.

Ideas

Capture a raw thought. Ideas is ideation until ready, develop it, then promote when it can become a Goal, spec, or ticket. Nothing starts as work until you say so.

Work

Commitments land here.

  • Needs attention: decisions only a human can make. Accept, Reject, or Retire covering work…
  • In progress: claimed work that’s moving.
  • Ready to start: safe to pick up, for you or an agent.

If intent moved, related work can’t start or finish until you say what to do. Agents don’t get to guess.

Complete

Finished work shows up with evidence. Nothing is complete without proof. A human Accept on Complete is extra confidence, not a gate. After Accept, you can write back into Knowledge so the next loop starts from what you deployed.

See also