Designing Mechanisms for Information Revelation

The Challenge: From Abstract Risk to Verifiable Fact

Let's ground our work in a concrete scenario. A primary couple, Clara and David, are considering opening their relationship to a new partner, Ethan. A key uncertainty for them is Ethan's sexual health status and recent testing history. This is a classic adverse selection problem: Ethan has private information (his "type") that Clara and David do not.

A naive approach, simply asking "What's your testing history?", is unreliable. As we saw with the auction examples in the last lesson, when there are incentives to misrepresent, people often will. An individual who hasn't been tested recently might fear being judged or rejected, and thus have an incentive to claim they have. Our task is to design a better process—a mechanism that makes truth-telling the path of least resistance.

This problem is not unique to relationships; it's a fundamental challenge in any market with hidden information. The study on the marriage market in Malawi, which we touched on previously, provides a compelling large-scale analogue.

The Malawi study illustrates that when testing is difficult or stigmatized, it's not a reliable signal. However, when a mechanism (in their case, a low-cost, "opt-out" testing program) is introduced that makes it easy to reveal one's "safe" type, the information asymmetry problem is reduced. We are about to design a similar, albeit personalized, mechanism for Clara, David, and Ethan.

A Step-by-Step Guide to Drafting the Mechanism

To build our contract, we will follow the formal steps of mechanism design. Given your background, we can frame this using the precise language of the field.

Step 1: Define the Environment

• Agents: Clara, David, Ethan.
• Principal: Clara and David (they are designing the contract).
• Agent with private info: Ethan.
• Private Information (Type, $\theta$): Ethan's true testing status. For simplicity, we'll define two types:
  • ${\theta }_V$: Verified-Recent. Ethan has been tested for a comprehensive STI panel within the last 90 days and has digital or paper results to verify this.
  • ${\theta }_U$: Unverified. Ethan has not been tested recently, is unsure of his last test date, or does not have verifiable results.

Step 2: Define the Outcomes (The Social Choice Function, $f(\theta )$)
The contract must specify a clear outcome for each reported type. Let $\hat{\theta }$ be the type Ethan reports.

• Outcome for reporting ${\hat{\theta }}_V$: This triggers a verification process. If verification is successful (Ethan provides the results), the outcome is Protocol A (Accelerated): physical intimacy can begin according to pre-discussed boundaries. If verification fails, the outcome is a penalty, such as reverting to Protocol B with an added "trust-building" period, or ending the negotiation.
• Outcome for reporting ${\hat{\theta }}_U$: The outcome is Protocol B (Baseline): all three individuals agree to get tested within a specified timeframe (e.g., 7-10 days). Once all three have shared their negative results, physical intimacy can begin.

This structure—Declare, Verify, Execute—is the core of the mechanism. It's not just about asking; it's a process that vets the answer.

Step 3: Engineer the Incentives (Payoffs and Transfers)
Now, we must ensure the contract is Incentive Compatible (IC) and Individually Rational (IR). To do this formally, we can model the environment as quasi-linear, a standard assumption in mechanism design.

In a quasi-linear world, an agent's utility is the sum of their valuation for the outcome and any "transfers" they receive: $u_i(f(\theta ),{\theta }_i)=v_i(k(\theta ),{\theta }_i)+t_i(\theta )$.

• $k(\theta )$ is the "project choice," which here is either Protocol A or B.
• $v_i(\cdot )$ is the agent's intrinsic value for that protocol.
• $t_i$ is a transfer of utility. This doesn't have to be money; it can be one party bearing a cost for another, like paying for a test or investing extra time in non-physical dates.

The following tutorial provides the formal language for these concepts, which should be very accessible given your expertise.

The dAGVA theorem is particularly elegant. It shows that under certain conditions (statistically independent types), we can design a set of transfers that not only incentivizes truthfulness but also ensures the system is "budget balanced" ($\sum t_i=0$). In a relationship context, this means the triad can create a fair, self-contained system of incentives without needing external resources.

Let's apply this.

• IC Constraint: A ${\theta }_U$ Ethan must not want to lie and claim ${\hat{\theta }}_V$. He might be tempted to lie to get Protocol A and avoid the hassle of testing. The mechanism prevents this because his lie would be exposed at the verification step. The "penalty" for failed verification ensures that his expected utility from lying is lower than his utility from telling the truth and following Protocol B.
  $E[U(\text{lie})|{\theta }_U]<U(\text{truth})|{\theta }_U]$
• IR Constraint: A ${\theta }_U$ Ethan must find Protocol B acceptable. Getting tested is a hassle. To ensure he doesn't just walk away, Clara and David can use a transfer ($t_i$) to increase his utility for this outcome. For example, they could offer to cover the full cost of his STI test or handle the logistics of scheduling the appointment. This transfer makes Protocol B more attractive, ensuring his participation.

Drafting the "Sexual Health and Safety Protocol"

Here is how these steps coalesce into a draft agreement. We can imagine Clara presenting this to Ethan.

Clara: "Ethan, as we've discussed, building a foundation of trust and safety is paramount for David and me. To make sure we're all on the same page and starting from a place of transparency, we've drafted a simple protocol for how we handle sexual health. The goal is just to make the process clear and fair for everyone. Would you be open to looking at it with us?"

DRAFT: SEXUAL HEALTH & SAFETY PROTOCOL

• Preamble: This document outlines the agreed-upon process for verifying the recent sexual health status of all parties (Clara, David, and Ethan) before commencing physical intimacy. Its purpose is to replace ambiguity with a clear, fair, and transparent procedure. All parties affirm that this process is preferable to proceeding with incomplete information.

• Section 1: Initial Health Status Declaration
  To initiate the protocol, Ethan is requested to select the statement below that accurately reflects his current situation.

  • Option V (Verified-Recent): "I have been tested for a comprehensive STI panel within the last 90 days and have access to the verifiable results (e.g., a digital portal login, dated PDF, or official clinic document)."
  • Option U (Unverified): "I have not been tested within the last 90 days, or I do not have verifiable documentation of my results."

• Section 2: Protocol Pathways
  The selected option in Section 1 determines the pathway forward.

  • Pathway V: If Option V is selected, Ethan agrees to share the verifiable results with Clara and David within 48 hours. Upon successful verification, all parties will proceed under the mutually agreed-upon terms for physical intimacy. If results cannot be verified within the timeframe, the process defaults to Pathway U.
  • Pathway U: If Option U is selected, all three parties (Clara, David, and Ethan) commit to undergoing a comprehensive STI test within the next 7 business days.
    • Facilitation (The Transfer): To make this process as simple as possible, Clara and David will cover the cost of Ethan's test (up to $XXX) and can assist with scheduling if desired.
    • Upon all three parties sharing their negative results with one another, they will proceed under the mutually agreed-upon terms for physical intimacy.

• Section 3: Principles of the Agreement

  1. Incentive Compatibility: This protocol is designed so that truthfully declaring one's status is the most efficient and beneficial path for everyone. Misrepresentation in Pathway V leads to the same outcome as Pathway U, but with a potential loss of trust.
  2. Individual Rationality: All parties agree that the safety and trust gained from this process outweigh the minor inconvenience of testing (Pathway U) or sharing documentation (Pathway V), and is superior to ending the negotiation.

This direct mechanism achieves our goal. It avoids putting Ethan on the spot with a simple question. Instead, it presents a choice between two clear, fair processes. It uses verification to make lying about being Verified-Recent pointless, and it uses a utility transfer (paying for the test) to make the Unverified path perfectly acceptable, thus satisfying both the IC and IR constraints.

Conclusion

In this lesson, we have moved from the abstract theory of mechanism design to the concrete act of drafting a relationship contract. By methodically defining the parties, their types, the potential outcomes, and the incentive structure, we constructed a direct mechanism to solve a real-world adverse selection problem.

Key Takeaways:

• Drafting is a Process: Creating an incentive-compatible contract is a systematic process of defining types, outcomes, and payoffs.
• Verification is Key: To prevent misrepresentation, a direct mechanism must include a step to verify claims, making lies unprofitable.
• Utility Transfers are Tools: In a quasi-linear framework, "transfers" (like covering a cost or offering time) are powerful tools to adjust payoffs and ensure that all parties find the agreement acceptable (Individual Rationality).
• Clarity Over Coercion: A well-designed mechanism doesn't force truth; it makes truth the most logical and straightforward choice for a rational agent.

Preview of the Next Lesson:

We have now successfully designed a contract to handle hidden information before an agreement is finalized (adverse selection). But what about hidden actions that occur after the agreement is in place? Our next lesson will tackle this second major information problem: moral hazard. We will explore how to model and create incentives for situations with unobservable actions, such as ensuring ongoing adherence to safe-sex protocols once a relationship is underway.