03 / Systems
Automation systems
Events become actions through observable states, rules and controls. If it can be structured, it can often be automated — but only where exceptions and failures can be governed.
How it works
I define triggers, state, validations, rules, actions, retries and escalation. The system must know what to do when the flow is valid and how to behave when it is not: stop, retry, notify or hand off to a person. I automate only the safe stretch.
The architecture
- 01 Event
- 02 State
- 03 Validation
- 04 Rules
- 05 Action
- 06 Monitor / Recovery
Technologies
- Python
- asyncio
- Telethon
- WebSockets
- systemd