Surface Configuration

A surface configuration answers four questions.

What opens it?

Define the host, path, and accepted query or signed context fields. Reject unknown or unsafe context instead of passing it straight into the agent.

Who owns it?

Attach the surface to a workspace and team. Ownership controls access, review, billing, and policy.

What can it do?

List the allowed tools, data scopes, and handoff rules. The agent should inherit policy from configuration, not improvise it.

What should it create?

Choose the expected output: quote, support ticket, summary, checklist, saved memory, or routed handoff. A good surface has a visible finish line.