Problem
aidd-qa now provides implementation-independent browser acceptance QA, but aidd-orchestrator:01-sdlc does not invoke it. The current SDLC validates, reviews, challenges, and opens a draft pull request without publishing acceptance evidence.
A reviewer therefore cannot tell from the pull request whether the reviewed commit passed technical validation and independent acceptance QA, failed it, was blocked, or had no supported acceptance interface.
Outcome
A draft pull request exposes a complete, commit-bound evidence set: technical validation, independent review, acceptance QA when applicable, and an explicit reason when QA is skipped or blocked.
Flow
- Deliver runs technical validation and commits the candidate.
- Check independently reviews and challenges that exact commit.
- The SDLC opens a draft pull request and publishes the technical validation summary.
- It discovers the installed QA capability and gives it only the acceptance criteria plus the reviewed candidate.
- QA runs against that exact commit and publishes
qa.md plus evidence links.
- The pull request records one evidence state:
passed, failed, blocked, or skipped with a reason.
- Any new candidate commit invalidates prior review and QA evidence and re-enters the appropriate checks.
Acceptance criteria
Prior art
Out of scope
- Implementing QA domain logic inside the orchestrator.
- Automatic merge or automatic promotion out of draft.
- Creating technical tests inside the QA plugin.
- API or CLI acceptance interfaces.
Problem
aidd-qanow provides implementation-independent browser acceptance QA, butaidd-orchestrator:01-sdlcdoes not invoke it. The current SDLC validates, reviews, challenges, and opens a draft pull request without publishing acceptance evidence.A reviewer therefore cannot tell from the pull request whether the reviewed commit passed technical validation and independent acceptance QA, failed it, was blocked, or had no supported acceptance interface.
Outcome
A draft pull request exposes a complete, commit-bound evidence set: technical validation, independent review, acceptance QA when applicable, and an explicit reason when QA is skipped or blocked.
Flow
qa.mdplus evidence links.passed,failed,blocked, orskippedwith a reason.Acceptance criteria
qa.mdand linked videos.failedorblockedstate remains explicit and never becomes successful evidence.skippedstate rather than false success.Prior art
aidd-qa.Out of scope