Lists and Cycles

Organize objects into governed collections and staged workflows.

Lists define scope: a governed set of objects included in work. Cycles define operating cadence: when that work repeats, which stages it moves through, and how progress is recorded.

Together, Lists and Cycles define who or what is in scope and when the work happens.

Choose the right shape

Need	Use
A curated or dynamic collection	List
Ordered work stages	Cycle
Multiple saved perspectives	List views
A workflow inside a larger workflow	Nested cycle

Examples include a weekly QA review List, monthly customer intelligence Cycle, payroll lock Cycle, implementation issue List, or content publication Cycle.

Entries point to canonical object records. This lets one object participate in multiple workflows while retaining one identity and one governed set of relationships.

Model transitions explicitly

A stage should describe meaningful operating state, not merely a screen column. Define who can move an entry, which transitions are valid, what evidence is required, and what should happen when a cycle rolls over.

Keep state that belongs to the workflow on the entry or transition. Keep durable business facts on the underlying object.

Lists and Cycles are also an execution surface for agents: an agent can triage, propose movement, or act when its authority grant permits it.