Grant QA bounded verification-action authority #128

Closed
opened 2026-07-29 04:43:32 +00:00 by coilyco-ops · 2 comments
Member

Outcome

Define the behavioral doctrine that lets QA perform bounded, reversible
verification actions when the runtime explicitly launches QA in an admitted
fixture mode.

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

Problem

The current sealed-role doctrine permits QA to observe live state but forbids QA
from initiating any live action. That makes an end-to-end verdict impossible
when the acceptance criterion is itself a disposable workflow or workload
launch.

Doctrine contract

  • QA may create, mutate, and clean up explicitly designated disposable
    verification fixtures only when the runtime grants fixture mode.
  • QA may launch the system under test when that launch is part of the acceptance
    criteria and remains inside the admitted fixture scope.
  • QA owns fixture setup, observation, evidence, verdict, and cleanup.
  • QA may not deploy, release, merge product work, mutate production targets,
    inspect secrets, or remediate a product failure.
  • One reproducible product failure returns to Engineer.
  • A live substrate failure returns to Ops.
  • Personality and role switching do not broaden this authority.
  • Without runtime-enforced fixture mode, the existing read-only QA boundary
    remains in force.

Repository ownership

  • agent-compose owns the QA charter and shared sealed-role doctrine.
  • Ward #1617 owns provider-neutral fail-closed fixture-mode enforcement.
  • AOS #781 owns the coilyco deployment binding and real end-to-end proof.

The dependency order is agent-compose doctrine, then Ward enforcement, then AOS
binding and proof. Agent-compose does not claim that prose grants executable
authority.

Scope

  • Update the canonical QA role skill produced by #121.
  • Update the shared sealed-role instruction asset from #110.
  • Keep the capability conditional on runtime-enforced fixture mode.
  • Render the same boundary across supported harness bundles.
  • Document the Ward and AOS ownership split.

Acceptance

  • An inferred or assigned QA role recognizes pre-authorized fixture mode as a
    bounded verification surface.
  • The same QA role refuses production mutation, deployment, release, merge, and
    remediation.
  • A QA role without fixture mode remains read-only.
  • Generated role bundles carry the same conditional boundary across supported
    harnesses.
  • Focused agent-compose tests cover rendered allowed and denied doctrine without
    pretending to enforce runtime actions.
  • Ward #1617 and AOS #781 are linked as the executable enforcement and proof
    contracts.
  • ward exec test and ward exec smoke pass.
  • The implementation lands on canonical main and closes this issue.
## Outcome Define the behavioral doctrine that lets QA perform bounded, reversible verification actions when the runtime explicitly launches QA in an admitted fixture mode. Run contract: #115 Paired role-skill migration: #121 ## Problem The current sealed-role doctrine permits QA to observe live state but forbids QA from initiating any live action. That makes an end-to-end verdict impossible when the acceptance criterion is itself a disposable workflow or workload launch. ## Doctrine contract * QA may create, mutate, and clean up explicitly designated disposable verification fixtures only when the runtime grants fixture mode. * QA may launch the system under test when that launch is part of the acceptance criteria and remains inside the admitted fixture scope. * QA owns fixture setup, observation, evidence, verdict, and cleanup. * QA may not deploy, release, merge product work, mutate production targets, inspect secrets, or remediate a product failure. * One reproducible product failure returns to Engineer. * A live substrate failure returns to Ops. * Personality and role switching do not broaden this authority. * Without runtime-enforced fixture mode, the existing read-only QA boundary remains in force. ## Repository ownership * agent-compose owns the QA charter and shared sealed-role doctrine. * Ward #1617 owns provider-neutral fail-closed fixture-mode enforcement. * AOS #781 owns the coilyco deployment binding and real end-to-end proof. The dependency order is agent-compose doctrine, then Ward enforcement, then AOS binding and proof. Agent-compose does not claim that prose grants executable authority. ## Scope * Update the canonical QA role skill produced by #121. * Update the shared sealed-role instruction asset from #110. * Keep the capability conditional on runtime-enforced fixture mode. * Render the same boundary across supported harness bundles. * Document the Ward and AOS ownership split. ## Acceptance * An inferred or assigned QA role recognizes pre-authorized fixture mode as a bounded verification surface. * The same QA role refuses production mutation, deployment, release, merge, and remediation. * A QA role without fixture mode remains read-only. * Generated role bundles carry the same conditional boundary across supported harnesses. * Focused agent-compose tests cover rendered allowed and denied doctrine without pretending to enforce runtime actions. * Ward #1617 and AOS #781 are linked as the executable enforcement and proof contracts. * `ward exec test` and `ward exec smoke` pass. * The implementation lands on canonical `main` and closes this issue.
Author
Member

Companion implementation graph:

Companion implementation graph: * coilyco-flight-deck/ward#1617 owns generic fail-closed fixture-mode enforcement. * coilyco-flight-deck/agentic-os#781 owns the coilyco deployment binding and real director to engineer to QA proof.
Author
Member

Landed on canonical main in cd99a44. The canonical QA role skill and native adaptation bootstrap now permit fixture mutation only when the runtime explicitly enforces an admitted disposable fixture mode. The doctrine limits QA to create, mutate, launch, observe, and clean up those fixtures. It keeps production, deploy, release, merge, secrets, and remediation out of scope, routes product failures to Engineer and substrate failures to Ops, and states that role or personality changes never broaden authority. Tests cover the QA role skill and native bootstrap. ward exec test and ward exec smoke passed.

Landed on canonical main in cd99a44. The canonical QA role skill and native adaptation bootstrap now permit fixture mutation only when the runtime explicitly enforces an admitted disposable fixture mode. The doctrine limits QA to create, mutate, launch, observe, and clean up those fixtures. It keeps production, deploy, release, merge, secrets, and remediation out of scope, routes product failures to Engineer and substrate failures to Ops, and states that role or personality changes never broaden authority. Tests cover the QA role skill and native bootstrap. ward exec test and ward exec smoke passed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-compose#128
No description provided.