David
Blumenau
Menu
Feature atlas
ConnectionsAsk the person who can answer

Bring a waiting decision back to the work.

The problem

An agent may need a human decision when the person is away from the pane where the work is running.

An explanatory exhibit

A decision with a return path

Local explanatory exhibit · invented records · no live service or agent call

Waiting task

Continue the poster.

One human choice is missing.

Pending decision · example-01

Illustrative Engine question card

Which direction should I keep?

Choose warm terracotta

Answer: warm terracotta.
The waiting task can continue with this decision.

Decline this decision

Decision declined.
The task receives a decline rather than an invented preference.

Inspect the consequence

Question waiting

Which poster should we continue?

A question card represents pending state beyond the terminal pane.

Person chooses terracotta

Answer returns to the waiting task

The decision has an identity and an answer path. Current delivery uses an Engine question card; historical routing varied with focus.

What this makes possible

Attention questions can create a durable question card routed through PanelForge and Relay to an Apple client; the answer or decline returns to the waiting agent.

Source information sheet

Evidence, implementation & history Implementation inspected

What I checked

Source and release record inspected; no current product execution is claimed for this illustration. Current Attention instructions always use an Engine question card; focus-dependent routing belongs to the historical record.

Release anchor: attention-mcp v0.1.2; claude-relay commit f2250af (2026-09-30).

Research cut: 14 October 2026. Source areas below are from attention-mcp + claude-relay + panel-forge + claude-engine-app. Private conversation references are retained in the research ledger and are not published here.

Implementation decisions

Attention questions can create a durable question card routed through PanelForge and Relay to an Apple client; the answer or decline returns to the waiting agent.

Represent the question as durable state and use focus/session context for routing, instead of making the agent guess whether a pane is attended.

A path through the feature

  1. The consequence

    Represent the question as durable state and use focus/session context for routing, instead of making the agent guess whether a pane is attended.

Source areas

  • attention-mcp/attention_mcp/server.py
  • claude-relay/README.md
  • claude-relay/attention_presentation.go
  • claude-relay/decisions.go
  • claude-engine-app/Targets/iOS/

The small explanatory exhibit uses invented records to describe the mechanism. Separate recordings and working examples carry their own evidence notes.

Recorded history

Dates describe the researched record, rather than today’s deployment.

  1. attention-mcp v0.1.2; claude-relay commit f2250af (2026-09-30)