Mixed evidence disposition
All scenarios remain Not executed. Original scenario classifications and Given/When/Then/Evidence/Decision bodies are unchanged. These links are consolidation-level dependencies, not additional features, policy decisions or proof that the source explicitly cited every mapped test.
Manual evidence uses approved procedure/charter and consent-template revisions, synthetic fixture, staff roles, date and observed result. No application build is needed to rehearse that manual portion. Software assertions require the relevant application adapters, policy choices and named-build evidence; complete software variants are rechecked in Step 11. Do not mark an entire mixed scenario complete using only the manual receipt, nor call the manual service implemented software. These service records do not become software payment gates.
The complete review covered DG01–DG44. Cases below contain software-dependent assertions or evidence. Unlisted DG cases have no identified application-evidence dependency in their current manual/document assertions; this is not a proof of a future implementation.
| Scenario | Linked software evidence | Split / limitation |
|---|---|---|
| DG02 | T17 | Manual evidence review and applicant receipt; separately verify the in-product label only once Q05/Q08 is decided. |
| DG03 | T05, T06 | Manual pointer and permission check; separately confirm the referenced published record and eligible audience. |
| DG05 | T07 | Manual neutrality disclosure/refusal; separately verify ranking has no undisclosed paid influence. |
| DG07 | T28 | Manual requester-authorised assistance; separately verify DG cannot fetch private bodies through admin routes. |
| DG09 | T28 | Manual session consent and agenda; separately verify the no-platform-body-access boundary. |
| DG13 | T30, T31 | Manual stop-contact and requested help; separately verify company-only pending/overdue access. |
| DG20 | T28 | Manual restricted incident-handling record; separately verify there is no ordinary DG private-thread fetch. This does not authorise a new incident-content feature. |
| DG21 | T25 | Manual revalidation and handover of obligations; separately verify live product revocation. |
| DG22 | T10, T27, T28 | Manual receipt-correlation review plus software metadata/route allow-deny and canary evidence. |
| DG24 | T28, T30, T33 | Document change/scope disposition; separately verify current access/output boundaries. No application implementation of the proposed extra features. |
| DG25 | T01, T37 | Manual invite-list/message review plus software claim, membership and session evidence. |
| DG26 | T01, T27 | Manual intake-policy review plus actual own-intake state/operation API evidence under Q19. Linked baseline checks are not a substitute for the DG26 matrix. |
| DG27 | T02, T28 | Manual assisted-onboarding advice and owner authority; separately verify denied impersonation/edit-as-owner routes in the existing product. |
| DG28 | T17, T28 | Manual checked-fact record/appeal; any in-product label/access assertion waits for Q05/Q08/Q20 and software evidence, not a verification engine. |
| DG29 | T13, T14, T28 | Manual owner-supplied draft advice; separately verify exact-version publication and no DG draft/private-body access. |
| DG37 | T05, T13, T14 | Manual public-promotion disposition plus existing opportunity publication/approval evidence; no public CMS is introduced. |
DG24 and DG44 are primarily document/scope guards, not staff-service rehearsals. DG24 additionally cites current software boundaries; DG44’s document-link checks remain document checks, not an application test run. DG22, DG25, DG26 and DG37 retain their original Balanced-boundary classification.
For each linked software test, use its full component dependencies in Dependency-and-Regression-Table, not only its primary step. This mapping cannot resolve Q01–Q25 or create a verification badge, campaign feature, private-message permission or service entitlement.
Review basis: Restored-Reviewer-Feedback. Original bodies: Scenario-Index.