Phases · the lifecycle
Always know where an arc stands.
Phases are an arc's lifecycle position — and unlike a status dropdown, they move as the relationship moves. Prospect, Active, Expansion, Renewal: each phase tells people and agents what's expected next, and every transition is a recorded event.
One arc is mid-transition — its ghost stays in Active, its live card arrives in Expansion with a record of what triggered the move.
Phases are events, not state.
Moving an arc from Active to Expansion writes a beat to its stream — so the transition is part of the relationship's history, not a silent edit.
Enterprise, SMB, and partner arcs can have different phase sets. The platform enforces the right lifecycle for the right relationship type.
Each phase tells humans and agents what actions are appropriate, what health thresholds matter, and what documentation is required before moving on.
Transitions are events, not edits
Every move leaves a mark.
Moving an arc's phase emits a beat. That beat is append-only, attributed, and visible to every human and agent with access — so the question "why is this in Expansion?" always has an answer.
- Phase transitions are configurable per scope type.
- Agents can trigger transitions and log the reason.
- Health rolls up by phase — so you see where the whole pipeline stands.
Move relationships forward.
Give every arc a lifecycle that moves with it — and a full record of every step it took.