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.
DG28 · DG badge is evidence-based and qualified
| Field | Value |
|---|---|
| Status | Not executed |
| Type | Manual DG service |
| Layer / kind | Manual + Balanced label boundary |
| Priority | — |
| Gates | S09 |
| Build step | Step-12-Manual-DG-Services-and-Scope-Guards |
| Decisions | Q05, Q08, Q20 |
Given
Owner pays for review; fact evidence, third-party badge screenshot, stale and disputed evidence variants exist.
When
Review source/fact/date/limits; expire or dispute the check; request appeal.
Then / oracle
Payment does not buy a badge or capability guarantee. Eligibility, representative authority and checked fact remain separate. DG does not issue LinkedIn verification or imply endorsement. Screenshot alone is not automatic proof; unconfirmed fact remains unverified. Expiry/hold/appeal await policy.
Evidence required
Checked/not-checked record, dated qualified template, normal no-badge result and independent appeal trail.
Decision dependency (verbatim)
Q05/Q08/Q20: sources, label fields, validity/dispute/appeal; no upload store or registry integration assumed.
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.