Add an enforceable QA verification fixture mode #1617

New issue

Closed

opened 2026-07-29 04:44:03 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

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

Member

Outcome

Give Ward a generic, fail-closed mode in which QA can launch and observe an end-to-end role chain against an explicitly admitted disposable fixture while remaining unable to affect ordinary repositories or release surfaces.

Doctrine owner: coilyco-flight-deck/agent-compose#128

Product boundary

Ward owns the executable enforcement. Ward must not embed Kai-specific repositories, labels, identities, or credentials. A deployment supplies the admitted fixture scope through the typed provider-neutral Ward configuration seam.

Required behavior

Add an explicit QA verification mode to the native Ward agent surface.
Admit only configured fixture repositories and fixture issues.
Permit the minimum actions required to launch, observe, stop, reap, and clean up a director to engineer to QA chain.
Deny pushes to normal repositories, direct-to-main workflows, merges, releases, deploys, production targets, and access outside the fixture scope.
Preserve append-only audit and provenance for every fixture action.
Make cleanup idempotent and visible. A completed or failed run leaves no container, reservation, branch, or open fixture issue behind unless preservation is required for evidence.
Route product failures back to Engineer and substrate failures to Ops. QA does not remediate either class inside the verification run.

Interface shape

Choose a typed mechanic or equivalent native option that is explicit at launch and survives director dispatch into engineer and QA children. A prompt-only convention is insufficient. Ordinary runs remain unchanged when the mode is absent.

Acceptance

A hermetic fixture demonstrates a director to engineer to QA run and terminal cleanup.
Attempts to target a non-fixture repository or issue fail before launch.
Attempts to select merge, release, deploy, or direct-to-main behavior fail closed.
Tests exercise loader behavior with fixtures rather than restating deployment configuration.
The focused runtime configuration tests, focused agent tests, and the full test suite pass.
Documentation explains the authority boundary and the deployment seam.

A companion AOS issue owns the concrete fixture binding and end-to-end proof for the coilyco deployment.

## Outcome Give Ward a generic, fail-closed mode in which QA can launch and observe an end-to-end role chain against an explicitly admitted disposable fixture while remaining unable to affect ordinary repositories or release surfaces. Doctrine owner: coilyco-flight-deck/agent-compose#128 ## Product boundary Ward owns the executable enforcement. Ward must not embed Kai-specific repositories, labels, identities, or credentials. A deployment supplies the admitted fixture scope through the typed provider-neutral Ward configuration seam. ## Required behavior * Add an explicit QA verification mode to the native Ward agent surface. * Admit only configured fixture repositories and fixture issues. * Permit the minimum actions required to launch, observe, stop, reap, and clean up a director to engineer to QA chain. * Deny pushes to normal repositories, direct-to-main workflows, merges, releases, deploys, production targets, and access outside the fixture scope. * Preserve append-only audit and provenance for every fixture action. * Make cleanup idempotent and visible. A completed or failed run leaves no container, reservation, branch, or open fixture issue behind unless preservation is required for evidence. * Route product failures back to Engineer and substrate failures to Ops. QA does not remediate either class inside the verification run. ## Interface shape Choose a typed mechanic or equivalent native option that is explicit at launch and survives director dispatch into engineer and QA children. A prompt-only convention is insufficient. Ordinary runs remain unchanged when the mode is absent. ## Acceptance * A hermetic fixture demonstrates a director to engineer to QA run and terminal cleanup. * Attempts to target a non-fixture repository or issue fail before launch. * Attempts to select merge, release, deploy, or direct-to-main behavior fail closed. * Tests exercise loader behavior with fixtures rather than restating deployment configuration. * The focused runtime configuration tests, focused agent tests, and the full test suite pass. * Documentation explains the authority boundary and the deployment seam. A companion AOS issue owns the concrete fixture binding and end-to-end proof for the coilyco deployment.

coilyco-ops referenced this issue from coilyco-flight-deck/agentic-os

2026-07-29 04:44:20 +00:00

Define the coilyco QA fixture lane and end-to-end proof #781

coilyco-ops referenced this issue from coilyco-flight-deck/agent-compose

2026-07-29 04:45:03 +00:00

Grant QA bounded verification-action authority #128

coilyco-ops commented

2026-07-29 04:45:06 +00:00

Author

Member

Companion graph:

coilyco-flight-deck/agent-compose#128 owns QA verification-action doctrine.
coilyco-flight-deck/agentic-os#781 owns the coilyco fixture binding and end-to-end proof.

Companion graph: * coilyco-flight-deck/agent-compose#128 owns QA verification-action doctrine. * coilyco-flight-deck/agentic-os#781 owns the coilyco fixture binding and end-to-end proof.

coilyco-ops added the

priority

autonomy

headless

labels

2026-07-29 04:47:32 +00:00

coilyco-ops referenced this issue from a commit

2026-07-29 05:02:46 +00:00

feat(agent): add bounded verification fixtures

coilyco-ops closed this issue

2026-07-29 05:02:46 +00:00