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.
Round DG Service 2 DG Verdict
Original: dg-side-round2-verdict.md.
DG-side response to adversarial round 2, with verdict
Design exchange only. No fees, windows, refund terms or retention periods are set here; every [ ] is DG’s to fill. Examples are synthetic templates, not delivered services or test results.
Corrections accepted (supersede round 1 where they differ)
- C1. Authority. Only the company whose reply it is can authorise disclosing that reply. B’s approved text authorises what DG says to A, never what DG reveals about A to B. My round 1 line “tell B that A declined if B’s text allowed it” is withdrawn.
- C2. Containment first. Any participant can trigger an immediate protective pause. Only a verified authorised representative changes durable consent. My round 1 line “no revocation until confirmed” is replaced by the pause/confirm split in rule 2.
- C3. Sent is not read, and read is not delivered. Receipts use the status ladder in rule 7.
- C4. No-fit cannot replace a paid introduction. A search report completes a search deliverable only.
Ten rules, with example replies
1. Authority over replies. Default to B when A declines or ignores: “No joint session or introduction is arranged. We do not share another company’s response.” This sentence is used identically whether A declined, ignored, or was never asked, so it reveals nothing. Receipts and counts must not show “candidate asked, declined” unless that candidate approved it. To A: “Your request is closed. We have shared nothing about your answer.” A may separately approve an attributable reply: “You may tell B: [A’s exact words].”
2. Pause versus durable instruction. Anyone on the call: “Stop sharing.” DG: “Paused. No further disclosure in this session and all pending disclosures are held. We will confirm any lasting instruction with the registered authorised contact.” Pause costs nothing and is lifted only by that contact. A pause is not a revocation, a membership change or a ledger release. An unknown caller can pause, and nothing more. Unknown caller asking for the ledger or to revoke membership: “We will confirm through your registered contact before acting.”
3. Stale queued work and sent disclosures. Final manual check immediately before every send: current consent, recipient, fields, expiry, no pause. If anything fails, cancel the draft, stop follow-ups, record “cancelled at check, reason, time”. A scheduled draft is not permission. If something unauthorised was sent: treat as an incident (rule 5 route), say so plainly: “A disclosure went out that you had not authorised. It cannot be recalled. Here is what was sent, to whom, when.” If an authorised disclosure was sent before revocation: “It was sent while your consent was valid. Revocation blocks all future use, and we cannot recall it.” Never say “recalled” unless the recipient confirmed deletion. The final check is a staff record. It is not a product worker.
4. Spoofing and departure. Lookalike requests receipts or bank details: “We will not act on this request. We are contacting your registered admin through the route on file.” No receipt, no bank details, no refund to a new account. DG sends no bank-change or refund instructions by email. Refund routing, if ever offered, is a DG finance policy and is not in this scope. Contact left the company: DG pauses uncompleted disclosures for revalidation, asks the company to name a current authorised representative through a pre-agreed route, and does not extend consent silently. The ledger is retained, not erased. Open obligations are closed or transferred only by a verified representative; if none can be verified by [DG window], DG closes disclosures and states the service state. The former contact’s copy of consent is not a current consent.
5. Forwarded private content and urgent complaints. To A: “Please stop forwarding another company’s private correspondence. We will not use or pass it on for facilitation. It is held restricted for triage only. Send us a summary of your own concern without the other party’s text.” DG does not open the platform thread. DG does not quote the forwarded content to B. If B asks “did A send you my message?”, DG answers only what B is entitled to: “A third-party document was received and is restricted; it is not used.” Whether the existence of the forward is told to B is a DG policy decision, listed below. If A alleges a security incident: “We will handle this under the incident procedure with the minimum evidence needed. We cannot promise deletion of all material while an investigation is open.” Containment: restrict access to named incident staff; retain a record of receipt, time and handling separately from raw content; raw content kept only as long as the incident procedure requires; one named incident owner. Policy for retention and for whether raw content is ever read: pending.
6. Both pay, duplicate work, conflicts. A asks for earlier access, exclusivity or a recommendation: “That is not offered under this neutral service. Payment does not buy another party’s information, priority or advocacy.” One call serving both: record it once as one activity with its own reference. Each client receives a redacted receipt of its own deliverable. DG does not claim two independent introductions or two pieces of work for one event. Whether and how each client is charged is a matter for their separate agreements, which DG sets. Duplicate requests reuse the same case reference: no second activity, charge or disclosure is created from a repeat request. A repeat is answered “Already in progress under [ref]“. Conflict: a person who has seen one party’s confidential limits is excluded from the opposing matter, whatever they promise. DG assigns an unexposed person. If none exists, DG suspends or declines joint facilitation and tells both parties the same: “We cannot provide joint facilitation on this matter under our neutrality rules. Nothing about either party has been shared with the other.” No competitor or client is named. Separate representation is a new engagement with its own conflict review. It is not promised.
7. Evidence of delivery: a status ladder, never collapsed. 1 planned; 2 attempted contact (who, when, channel); 3 sent/accepted by channel, only if the channel reports it; 4 recipient acknowledgement, only if the recipient actually responded; 5 DG’s completion claim against the agreed deliverable; 6 client disputes or accepts; 7 remedy decision. A provider “sent” is rung 3, never rung 4. An internal checklist is DG’s own record, not independent proof. Each receipt links the agreed deliverable, the staff action, the evidence and the client’s own acknowledgement or dispute. Receipt wording: “Delivered” is not used for rung 3. Use “Sent on [date]. No acknowledgement received.” No backdated consent, no uncarried calls, no inflated counts, no ROI.
8. No-fit, false verification, non-delivery, confidentiality incident. A paid for an introduction: DG cannot relabel a no-fit as the promised item. Reply: “Your agreed deliverable was an introduction. The search deliverable was completed on [date]. The introduction was not made. We have recorded the introduction as unmet and referred it for remedy review by [role] under the agreement you were given. No remedy has been decided.” The “no guaranteed deal” line is not used here, because it describes outcomes, not DG’s own work. False verification claim: “We have restricted the verification label on your profile [or the other company’s profile if it is theirs] pending review, because the statement was not supported by what we checked. We are reviewing the risk to other members. Remedy for the service failure will be reviewed by [non-involved role].” No waiting for a failed deal. Confidentiality incident: “We treat this as an incident, not a routine complaint. Triage owner: [role]. Containment steps taken: [list]. We will tell you what was exposed and to whom as soon as we know it, by [window].” Ordinary dissatisfaction (no deal, work delivered): “Work delivered is listed here. A deal was not part of what we agreed. We have recorded your feedback. Your remedy request is reviewed under the policy you were given.” No blanket no-refund rule and no invented entitlement.
9. Outcomes and metrics. Each report is private and labelled “self-reported”. Not used as a testimonial. DG never says “A reported success” to B or “B reported failure” to A. DG never labels a company difficult in any record visible to another party. No “independently confirmed” label exists until DG defines the evidence for it; it is outside current scope. Nonresponse and unknown are neither success nor failure and are never counted as either. Publishing any outcome, name or quote needs separate exact permission from each named company. Small-number statistics, unique timing or opaque IDs can identify a company, so no aggregate is published unless DG has set a minimum group size and checked it by hand.
10. Mapping, scope, operation.
- The dated verification label depends on Q05/Q08. Its exact fields are not approved here.
- The Q08 candidate metadata allowlist is unapproved. No private-state-to-contact crosswalk exists or is assumed.
- A pointer reaches only the eligible audience through approved channels. A member-visible opportunity is not a public web page.
- Manual staff emails and calls are not a fifth automatic business-event email and not a dashboard.
- The manual ledger needs an approved storage, access and retention route before any real company data is recorded in it.
DG-side verdict
Conditional approve for the Manual service set (sections 1-10 above) as a design, subject to these conditions:
- Nothing in Added scope is implied. Thread participation, proactive named outreach from metadata, cross-company overdue views, dashboards, automated outcome collection and bank/refund automation remain out unless separately approved.
- The Manual ledger must not hold real company data until its storage, access, retention and who-may-view are approved.
- Verification label wording stays blank until Q05/Q08 are settled. The “checked / not checked / date” structure is endorsed.
- The final pre-send check and the pause/confirm split are mandatory staff procedure from day one, since DG cannot rely on software to enforce them.
- No service is sold until DG has written, per client, the deliverables and what counts as unmet.
- A and B receive the same neutrality statement before paying.
- All examples in this exchange are synthetic templates. None is evidence that any company received any service.
Not approved: counting a no-fit as a delivered introduction; telling any party that another party declined, was asked or was silent without that party’s approval; any use of forwarded private content; “Delivered” for a mere send; any outcome statistic.
Pending decisions for DG (blank, not mine to fill)
- Fees, what each fee buys, charge on rejection, refund and remedy policy.
- Response windows: acknowledgement, requested-help follow-up, incident, complaint update, case close.
- Complaint reviewer role, and the fallback when the only qualified reviewer is involved.
- Ledger storage, access, retention, redaction of per-client receipts.
- Whether DG tells B that a third-party document was received (rule 5).
- Incident procedure: raw content retention, who may read it, evidence handling.
- How open obligations are closed or transferred when a company leaves or its contact departs, and the window for naming a new representative.
- Minimum group size, if any aggregate is ever published.
- Whether separate representation is ever offered, and the conflict review for it.
- Whether thread participation is ever offered (default: no).
- Q05/Q08 mapping, if any proactive outreach is wanted.
- Refund routing and finance verification (not designed here).
Text-check request
When you send the annex, I will check: every [ ] is still blank or marked DG’s, no sentence implies a delivered service or a promised refund/outcome, no wording reveals another party’s status, “Sent / Delivered” distinctions hold, and nothing in Added scope reads as included.