Cycle flow

A cycle is a unit of substantial work made auditable. You open it, declare what you set out to do, and seal it with a meditation the next session inherits — so a multi-session effort reads back as one coherent arc instead of scattered chats.

gov cycle open <slug>          →   cycle bound to the workspace
        │
gov cycle set-manifest         →   title, vision, branches recorded
        │
   …do the work…
        │
gov cycle decision-add         →   bind decisions made along the way
        │
gov cycle close-ritual <slug>  →   7 steps → sealed cycle + seed

Open

seif gov cycle open c1-my-feature
seif gov cycle set-manifest --title "My feature" --vision "What this cycle delivers"

The slug (c<N>-slug) is how the cycle is referenced everywhere afterward.

Record decisions

seif gov cycle decision-add <decision-id>   # bind a decision to this cycle

Decisions taken mid-cycle are linked both ways, so the cycle carries its own rationale.

Seal

seif gov cycle close-ritual c1-my-feature

The closure ritual runs seven steps locally — checkpoint, audit, quality, meditate, absorb, seal, seed. The final seed points at the sealed cycle, which carries the whole arc, so the next cold start resumes exactly where you stopped. (gov cycle close seals without the full ritual when you only need the pointer cleared.)

Housekeeping

seif gov cycle list            # cycles in .seif/cycles/ (filter with --status)
seif gov cycle gc              # garbage-collect stale OPEN cycles (dry-run by default)

Where to go next

• Governance flow — pendings and decisions that feed a cycle.
• Session flow — recording who did the work.