The Question Primitive

Approvals are powerful, but they are only the first shape.

The more general primitive is a Question.

A Question is a Ping carrying a prompt and a small set of predefined options. A human can answer with one tap from a notification or inside the app. The answer routes back to the asker. It expires if nobody responds. It is structured end to end so software can act on it.

That is the kind of primitive I think can become standard.

Why Questions Matter

Agents need human decisions that are more nuanced than yes or no.

Which environment should I deploy to? Which branch should I use? Should I retry, cancel, or escalate? Which version should I publish? Should I approve the refund or request more context?

These are not chat conversations. They are bounded decisions. The agent already knows the options. The human needs to pick one. A notification with answer actions is the lowest-friction interface for that.

The Contract

The Question shape needs stable vocabulary.

There is an asker, a responder, a prompt, optional context, two to four options, responder scope, resolution policy, expiry, state, answer, correlation id, data, reply pointer, and timestamps.

The states should be simple: pending, answered, expired, cancelled. Terminal states should be immutable. For room-scope questions, the first valid answer wins in v1. For direct questions, only the target person can answer.

Stable names matter because this is not just UI. It is a public agent contract.

Two Surfaces, One Action

The human should be able to answer from the notification or the app.

Two options are the fast path because they fit naturally into notification actions. Three or four options should still be supported, but the product should recognize that they may require expansion or an in-app sheet.

Inside the app, a Question should be a first-class history cell, not just a hidden approval inbox. Pending questions, answered questions, expired questions, and cancelled questions should all read clearly.

Both surfaces call the same server operation. First valid answer wins. Later taps get a clean already-resolved response.

Why This Fits PingRoom

PingRoom is already built around Pings, rooms, structured data, and push.

Questions extend that model without turning the product into chat. The room gives context. The push delivers urgency. The options keep the decision bounded. The structured answer lets an agent continue.

This is the kind of feature that makes the platform feel inevitable. Once you see it, dashboards start to feel heavy.

The Future

The Question primitive can become a shared pattern for agent frameworks, CLIs, CI tools, and automation systems.

The human answer does not need a web app. It does not need a Slack bot. It does not need a thread. It can be a real push, one tap, and a structured result.

That is PingRoom at its best: simple for the person, precise for the machine.

Status And Scope

The important alignment point is that Questions are a protocol direction grown from the existing approval system, not a separate chat product. Approvals already prove the two-option human gate. The Question primitive formalizes the general case: two to four options, direct or room responder scope, first-answer-wins behavior, expiry, cancellation, and a consistent answer envelope.

That keeps the roadmap grounded. The next step is not inventing another communication surface. It is promoting a proven approval shape into a stable standard that agents, SDKs, CLIs, and webhooks can share.