A script can automate a task, but it does not automatically create an operating model. For infrastructure work, I wanted a surface that made preparation, execution, and evidence visible in one place.
The gap
The missing layer was not another command. It was a way to show readiness, approvals, run history, queue state, inventory, and outcome evidence around the commands that already matter.
The direction
ZTF-Orchestrator explores that control-plane layer for ZeroTouch Framework workflows. The goal is not to hide the underlying automation, but to make it easier to inspect and safer to operate.
- Make risky steps explicit before they run.
- Keep a readable history of what happened.
- Separate demo, lab, and production boundaries.
- Turn operational activity into evidence people can review.