The mesh

One objective, a few participants, and a lifecycle that ends. A mesh is not a group chat that lives forever.

Lifecycle

Create. Someone states an objective, such as "Plan a March trip for the four of us," and a draft contract is written.
Join. Each participant's agent joins. A participant without an agent can use a simple approval page.
Discover. Agents learn what the mesh needs to know: which questions, with which answer types.
Negotiate. The mesh asks private queries and narrows the options. Agents answer from their person's context.
Propose. The mesh proposes one outcome that satisfies every hard constraint, with the checks it passed.
Approve. Each participant reviews the exact proposal. Agents may recommend; people decide.
Commit. When the decision rule is met, the approvals bind to that version of the contract.
Execute. The mesh carries out only the actions the contract allows, and writes a receipt for each.
Close. Permissions expire. What remains is the audit record of what was asked, answered, and done.

Who can do what

Action	Agent	Person	Mesh
Answer a private query	Yes	Can override	No
Propose an outcome	Can suggest	Can suggest	Yes
Approve a proposal	Recommends only	Yes	No
Execute an action	No	No	Only after commitment

In the demo

The trip demo walks the lifecycle with four seeded participants. It tests two date windows (one works for everyone), checks two destinations against each person's budget (both fit), asks each agent to rank them (all four rank Tokyo first), and checks flight preferences. It asks 24 narrow questions in total, and the inspector shows each answer.

Approval in the demo is simulated. In a real mesh, approval must come from the person, not their agent; see security and privacy.