Home-Buying Mandate¶
The home-buying fixture is the first high-stakes AUMP example. It demonstrates how a mandate can represent a user in a regulated, expensive transaction without turning the protocol into a real-estate-specific standard.
What It Encodes¶
The mandate defines:
- a maximum offer of 650,000 USD;
- minimum square footage and bedroom requirements;
- allowed property types;
- required inspection and financing contingencies;
- protected negotiation fields such as the reservation price;
- required real-estate negotiation and compliance skills;
- a compliance profile that prohibits protected-class decision factors;
- trusted review before submitting an offer.
Why It Matters¶
Natural-language instructions like "find me a house with at least three bedrooms" are not enough for autonomous representation. A conforming runtime must evaluate those requirements as data before an agent sends an offer, counteroffer, A2A message, MCP tool call, UCP checkout handoff, or platform native action.
Conformance Cases¶
The fixture corpus includes these cases:
| Case | Expected |
|---|---|
| Compliant property evaluation | allowed |
| Property below minimum square footage | denied |
| Property above maximum budget | denied |
| Offer draft without inspection contingency | denied |
| Use of protected-class decision factor | denied |
| Submit purchase offer | requires_escalation |
The same cases pass in the Go conformance runner, Python SDK, and TypeScript SDK.
Runnable Proof¶
Expected summary:
AUMP home-buying proof
conformance: 39/39 passed
property match: allowed
draft offer: allowed
over-budget property: denied
missing inspection contingency: denied
protected decision factor: denied
submit offer: requires_escalation
evidence events: 6
proof: passed
The proof emits schema-valid evidence for the material steps and validates MCP and A2A mandate references before any downstream action is represented.