Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
DG26 · Guest and pending intake remain isolated and correctable
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Balanced boundary (checks a limit of Balanced) |
| Layer / kind | Balanced boundary · API/E2E |
| Priority | — |
| Gates | S08 |
| Build step | Step-02-Identity-Membership-Roles |
| Decisions | Q19, Q09 |
Given
Guest, pending, approved, rejected and revoked company identities; submitted V1 and corrected V2 intake.
When
Read/edit/withdraw/correct/reapply under each state and probe member-only and other applicant records.
Then / oracle
Unapproved guest has no member/private opportunity access. Proposed own-intake routes require signed matrix; corrections preserve submitted V1 rather than overwrite. No public-page or export feature assumed. Rejection/revocation blocks member content; own status/support/retention depend on policy.
Evidence required
State/operation table and positive/negative API evidence; immutable submitted revision; unresolved cells pending.
Decision dependency (verbatim)
Q19/Q09: exact own-intake, correction, resubmission, withdrawal and retention rules.
Source: TDD rev 1.3 (PDF); machine-readable in 10-Sources/tdd-bundle/. Back to Scenario-Index · Traceability-Matrix · integration dependencies in Dependency-and-Regression-Table.