Schedule Ownership and the Retained API

Context

The earlier independent-schedule direction was superseded by the walkthrough ownership ruling. Existing period pricing remains usable while the owner-aware write contract and setup are outstanding.

Decision

Ownerless schedule APIs remain implemented, but the later product ruling assigns schedules to selling owners and removes standalone administration.

Alternatives Considered

Retain permanent ownerless schedule administration. This conflicts with the later owner-bound product direction.

Restore a standalone schedule screen. The recorded ruling removes that surface in favour of owner setup.

Consequences

Existing ownerless schedules need an owner-aware migration path. Staff currently have no standalone console preparation surface. Unused schedule components can be reused by the owner setup or removed.