Schedules & Automations
Start governed work from time, events or changing conditions.
Primitive's automation direction is to treat schedules as one trigger type among several, then route the resulting work through the same agents, skills, authority and receipts as interactive work.
Instead of remembering to ask the AI the same thing every hour, you can define when work should wake up. The important part is that scheduled work still follows the same rules as work you started yourself.
Automation is not a separate mini-product. A trigger creates work; work executes through Primitive's normal governed runtime; results create state, evidence and potentially more events. The current Control programme contains automation/orchestration packets, but the full general-purpose automation surface is not yet documented as production-complete.
Trigger model
Time schedules, external events and internal state transitions should converge on a common trigger-to-work contract instead of each creating its own executor.
Independent schedules
Multiple independent checks can serve different lanes or roles without requiring one monolithic cron loop. The orchestrator should consume resulting signals and allocate work adaptively.
Governance
Automated execution does not bypass permissions. Consequential effects still pass through the relevant authority boundary and leave receipts.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.