← Consumer browseruns.aiProtocol playground · v0.1

Say what you need.
Make the meaning clear.

A place + a need → a structured request that bots and services can understand.

Borrow a drill nearby

“Borrow a drill nearby until Sunday.”

What counts as nearby? Which Sunday, and what time? Fill the gaps instead of guessing.

What would you like to borrow?Search area

Maximum distance (km)

Time zone

Borrow from (local date and time)Return by (local date and time)

These controls generate the draft. This preview does not run an AI interpreter, resolve places, find lenders or send requests.

One meaning. Multiple views.

Why this is self-explanatory

Named fields, explicit units, field descriptions and missing-information questions. URLs are an optional view of the request, not syntax people must learn.

The MCP view is a proposed tool definition—not a connected MCP server. Only the Jobs conformance slice has a pinned internal catalog tuple; this borrowing example still has no catalog mapping.

Candidate UNS clients · one draft-only connection

One namespace. Many specialist apps.

UNS makes the subject and intent portable. A specialist app takes over only after an explicit handoff—and owns its private questions, live availability, authentication and actions.

💼 Jobs · draft-only connected💘 Dating🛠 Contractor🎮 Games🔐 VPN🛟 Contingency

Identify
Resolve the place or other supported subject.

Structure
Preserve the need and hard constraints in a versioned draft.

Match
Find clients that explicitly declare support.

Hand off
The selected app checks availability and asks before acting.

A capability match is not availability or permission. Opening a UNS URL never dispatches an action.

First conformance target

Jobs has one pinned draft contract.

whoelse.intent@0.1.0 · whoelse.jobs.search

Connected · draft-only

Jobs commit 23e20df keeps the receiver disabled by default, enables it only on loopback, and returns typed unresolved for unevaluated employment_type and distance before snapshot access. 11/11 focused and 20/20 full tests pass. The proven exchange is loopback-local and not network reachable.

Jobs client declaration

{
  "client_key": "jobs",
  "declaration_version": "0.1",
  "catalog_id": "whoelse.intent",
  "catalog_version": "0.1.0",
  "supported_intents": ["whoelse.jobs.search"],
  "supported_subjects": ["place"],
  "handoff": {
    "mode": "http_post",
    "endpoint": "/api/intents/jobs/search/draft",
    "exposure": "loopback_only",
    "effect": "draft_only"
  }
}

Draft handoff envelope

{
  "contract_version": "0.1",
  "intent_draft": {
    "catalog_id": "whoelse.intent",
    "catalog_version": "0.1.0",
    "intent_id": "whoelse.jobs.search",
    "subject": {
      "kind": "place",
      "stable_key": "0c58efea-6b91-4a64-86a7-293d58c3df63"
    },
    "unresolved": []
  },
  "selected_client": "jobs",
  "requested_handoff": "http_post",
  "execution_authorized": false
}

Evidence 2026-10-07-uns-jobs-washington-handoff.json uses UNS stable key 0c58efea-6b91-4a64-86a7-293d58c3df63 in both request and query plan, returns outcome_unknown with 0 matches across 491 snapshot rows and no effects, and confirms live availability was not checked. Two identical submissions return the same draft ID and leave the whole job-search fingerprint unchanged. The key resolves at /-/place/0c58efea-6b91-4a64-86a7-293d58c3df63 to Union Station at 701 1st St NE in Washington, DC; it does not represent the whole city or make an availability claim. The other five candidate families are not in the catalog.