Security and privacy

Most of this page describes the design. Real scheduling meshes, which run locally for now, already work this way in a few places: agents answer only yes or no, nobody sees another person's answers, approvals name one proposal version, meshes expire after 7 days, and each person can see everything their agent told the mesh. Read the rest as how Scope Mesh is meant to work, not as a guarantee.

Private context stays with the agent

By default, a participant's calendar, email, budget, and accounts never leave their agent. The mesh holds the contract, the questions, and the answers.

Minimum disclosure

The mesh asks whether a constraint is met instead of asking for the data behind it: “Is $1,280 within budget?” rather than “What is your budget?” Answer types are fixed in the contract, so an agent can't be talked into sending more than the question allows. The demo's MCP endpoint works the same way: its join tool only accepts yes/no answers and a first choice.

Narrow answers still leak something. Enough yes/no questions about prices can narrow down a budget. A real mesh needs per-participant query limits and a contract that states in advance which questions may be asked.

Scoped capabilities

Each permission names a purpose and a category (“calendar: availability only”) and belongs to one mesh. Permissions are not reusable across meshes.

Proposal-bound approvals

An approval names one version of one proposal. Approval belongs to the person: an agent may recommend, but the commitment is the person's. This is why the demo MCP endpoint has no approval tool.

Expiry and revocation

Permissions expire when the mesh closes or on a set date, whichever comes first, and a participant can withdraw them at any time.

Replay resistance

Commitments will carry the contract version, the mesh id, and an expiry, so one can't be reused in another mesh or after its plan changes.

Audit log

Every query, answer, proposal, approval, and action is recorded, so each participant can see exactly what was shared about them. The demo's “Show what Scope Mesh learned” view is that record.

Not built yet

• Identity, accounts, and signed approvals.
• Execution against real services such as airlines, hotels, or payments.
• Cryptographic privacy modes. Future versions could support proofs and private computation for especially sensitive constraints. Nothing like that is deployed.

The demo itself

The demo runs on the server when the page is built. Your browser receives only the public result: events, answers, and the proposal. The seeded budgets and calendars are never sent to it, and automated tests check that the result contains none of them.