# Trigger-Shaped Schedule Entry

> Canonical path: `specs/trigger/trigger.md`
> Status: stable product facade
> Scope: old Trigger-shaped routes and tools backed by canonical schedules.

Normative replacements:
- [`specs/schedule/schedule.md`](../schedule/schedule.md)
- [`specs/architecture/service-actor-event-automation.md`](../architecture/service-actor-event-automation.md)

Trigger-shaped APIs remain stable for supported clients, but every operation is
implemented by Schedule and Automation stores. They expose canonical schedule
ids and never read or write retired Trigger definitions, Trigger runs, aliases,
or compatibility projections.