Earlier work, shown in past tense
Automation2026
Oreo Agent Runtime
The runtime that runs my business loops on a schedule
Results
- ✓One reasoning path instead of a different one per script
- ✓Every action it takes is written down and can be read back
- ✓The gated actions have never fired without a human saying yes
The Situation
- •Loops for outreach, reporting, and alerting were separate scripts with separate habits
- •Each one asked for a decision in its own way, so behaviour drifted between them
- •An agent that can act needs a record of what it did and a hard stop where humans belong
The System
- •Oreo runs the operations loops on a schedule
- •The reasoning layer is reached through one adapter so every system asks the same way
- •Human gates: sending, spending, and publishing stop and wait for approval
- •Everything runs locally and writes an audit log
How it runs
TriggerSchedule firescron
ActionOreo runs the loopOutreach, reporting, alerts
ActionReasoning layer decidesOne reasoning adapter
DecisionHuman gate?Send, spend, publish
ActionTakes the actionOnly when allowed
OutputAsks me firstApproval lane
OutputAudit logEvery action, always
Stack
Pythonlocal modelscronaudit log
What's Next
- Keep the gate list short and explicit
- Retire any loop that stops earning its schedule
This is earlier work.
NigelBuilds now runs managed business automation systems for service businesses. Start with the 21-day Pilot, or see a sample Results Brief first.
Next projectJob Search & Direct-Apply Engine