Grant QA bounded verification-action authority #128
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#128
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
verification fixtures only when the runtime grants fixture mode.
criteria and remains inside the admitted fixture scope.
inspect secrets, or remediate a product failure.
remains in force.
Repository ownership
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
Acceptance
bounded verification surface.
remediation.
harnesses.
pretending to enforce runtime actions.
contracts.
ward exec testandward exec smokepass.mainand closes this issue.Companion implementation graph:
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.