AI Agent Orchestration Platform · View 11 of 32 · 2 · Structure
Decisions
- A published version is immutable and addressed by content hash; change means a new version
- Rollback re-points an alias to a prior hash — it never edits or restores in place
- Prompts and agent definitions travel the same pipeline as code, so a prompt change is a reviewed deployment rather than a console edit
Gates
- Schema lint, policy simulation and a golden-set regression suite before any publish
- Behaviour diff against the currently live version, reviewed by the owning team
- Production entry is a canary at 5 percent for 24 hours, watched on SLO and on quality
Assumptions
- Every project has a golden dataset before it can promote to production; bootstrapping one is part of onboarding
- Version pinning happens at admission, so a run that starts on version N finishes on version N