Clarify engineer and Ops ownership when both can push code #116

New issue

Closed

opened 2026-07-27 22:26:19 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-27 22:26:19 +00:00

Member

Outcome

Make the Engineer and Ops ownership boundary symmetric in the canonical role
skills produced by #121.

Run contract: #115
Paired role-skill migration: #121

Contract

Engineering owns reusable product and software behavior through repository
validation and the resolved landing workflow.
Ops owns the running-system loop through before-state, controlled change,
rollback readiness, and after-state verification.
Ops may author and push operational configuration, deployment definitions,
rollback changes, runbooks, and operational automation when runtime authority
permits the action.
Ops hands product logic or reusable software changes to Engineering with the
observed evidence and acceptance condition.
An incident-scoped emergency source patch requires explicit runtime authority
and leaves durable Engineering follow-up.
Engineering may land repository-proven code, but Engineering does not trigger,
approve, or repeatedly probe live promotion.
A push-to-deploy workflow distinguishes an authorized landing consequence
from an operational experiment.

Role prose grants no permission. Launch consumers and guarded runtime policy
continue to own executable authority.

Source placement

The implementation edits the canonical Engineer and Ops role skills from #121.
If #116 lands in the same slice as #121, the implementation authors the final
wording directly in those new skill sources. The implementation does not edit a
generated roster projection or preserve a competing KDL briefing.

Acceptance

A reusable product fix routes to Engineering even when Ops discovered the
failure.
Operational configuration and rollback work can remain with Ops when runtime
authority permits it.
A GitOps or push-to-deploy example identifies who owns landing, promotion,
live verification, and rollback.
Neither role skill implies that repository push access grants deployment
authority.
Tests cover the clarified role skills and their compact rendered identity.
ward exec test and ward exec smoke pass.
The implementation lands on canonical main and closes this issue.

## Outcome Make the Engineer and Ops ownership boundary symmetric in the canonical role skills produced by #121. Run contract: #115 Paired role-skill migration: #121 ## Contract * Engineering owns reusable product and software behavior through repository validation and the resolved landing workflow. * Ops owns the running-system loop through before-state, controlled change, rollback readiness, and after-state verification. * Ops may author and push operational configuration, deployment definitions, rollback changes, runbooks, and operational automation when runtime authority permits the action. * Ops hands product logic or reusable software changes to Engineering with the observed evidence and acceptance condition. * An incident-scoped emergency source patch requires explicit runtime authority and leaves durable Engineering follow-up. * Engineering may land repository-proven code, but Engineering does not trigger, approve, or repeatedly probe live promotion. * A push-to-deploy workflow distinguishes an authorized landing consequence from an operational experiment. Role prose grants no permission. Launch consumers and guarded runtime policy continue to own executable authority. ## Source placement The implementation edits the canonical Engineer and Ops role skills from #121. If #116 lands in the same slice as #121, the implementation authors the final wording directly in those new skill sources. The implementation does not edit a generated roster projection or preserve a competing KDL briefing. ## Acceptance * A reusable product fix routes to Engineering even when Ops discovered the failure. * Operational configuration and rollback work can remain with Ops when runtime authority permits it. * A GitOps or push-to-deploy example identifies who owns landing, promotion, live verification, and rollback. * Neither role skill implies that repository push access grants deployment authority. * Tests cover the clarified role skills and their compact rendered identity. * `ward exec test` and `ward exec smoke` pass. * The implementation lands on canonical `main` and closes this issue.

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-07-29 03:44:35 +00:00

coilyco-ops referenced this issue

2026-07-29 04:41:08 +00:00

Run contract: complete the Agent Compose v1.x issue suite #115

coilyco-ops referenced this issue

2026-07-29 04:41:11 +00:00

Materialize role definitions as skills and shrink startup doctrine #121

coilyco-ops referenced this issue

2026-07-29 04:41:34 +00:00

Move authored prose and configuration out of Go #110

coilyco-ops added

and removed

labels

2026-07-29 04:41:59 +00:00

coilyco-ops commented

2026-07-29 05:10:13 +00:00

Author

Member

Landed on canonical main in cd99a44. The canonical Engineer and Ops role skills now state the symmetric boundary: Engineer owns reusable product and software changes through repository validation and landing. Ops owns the running-system loop through before-state, authorized change or promotion, rollback readiness, and after-state verification. GitOps wording distinguishes repository landing from promotion and live verification. Role prose explicitly grants no executable authority. Covered by role-skill loader, resolver, roster, bundle, and verification tests. ward exec test and ward exec smoke passed.

Landed on canonical main in cd99a44. The canonical Engineer and Ops role skills now state the symmetric boundary: Engineer owns reusable product and software changes through repository validation and landing. Ops owns the running-system loop through before-state, authorized change or promotion, rollback readiness, and after-state verification. GitOps wording distinguishes repository landing from promotion and live verification. Role prose explicitly grants no executable authority. Covered by role-skill loader, resolver, roster, bundle, and verification tests. ward exec test and ward exec smoke passed.

coilyco-ops closed this issue

2026-07-29 05:10:18 +00:00

coilyco-ops referenced this issue

2026-07-29 06:30:33 +00:00

Run contract: complete the Agent Compose v1.x issue suite #115