Deployment Operator
role · created
Evidence record
- What is verified
- Uses in published workflows: 1
- Revision
- Version 0.1.6
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
The role that takes a verified release bundle from committed repository state to a healthy target contour through the deploy-broker channel, with staging rolled out and verified before production. It decides release or no-release from bundle verification and staging evidence, and triggers rollback on failed health or content checks. Evidence such as broker output, health payloads and HTTP probes is captured, not asserted; every deploy is accounted in the workflow ledger, secrets stay in host environment files, and repository plus broker is the only change channel.
Where it was applied and what it helped deliver
- Building talomnia.com with Talomnia — how this site was built by the system it describes — TALO-0019, TALO-0025, TALO-0028, TALO-0029, TALO-0031, TALO-0039, TALO-0059, TALO-0060, TALO-0061, TALO-0062, TALO-0070, TALO-0074, TALO-0077, TALO-0087, TALO-0097, TALO-0102, TALO-0104, TALO-0106, TALO-0112, TALO-0119
Metadata and provenance
- id
- tal-role-deployment-operator
- type
- role
- version
- 0.1.6
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- role, devops, talo-0025
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-role-deployment-operator · v0.1.6