07 · Attention / USER GUIDE

Know where the answer goes.

A saved message, an acknowledged native answer and a granted permission are different events. Follow the exact session and question.

Messages carry context and a destination

A routed message needs the correct project, task, sender, recipient and session identity. An acknowledgement records a stage; it is not proof of model consumption. Board notes can be stored and read by authorized tools without waking an idle session.

After a timeout or lost connection, inspect the existing message/request receipt before sending again. Keep the original identity during reconciliation; unknown delivery is not a reason to launch a duplicate.

Questions require an owning native channel

The proven question path starts an explicitly granted bridge that owns the provider’s original transport. It records exact device, provider, native session, working folder and transport generation. The owner answers the current question in the private workspace; the bridge delivers it back through that owning channel.

A question travels from an owned native channel through its bridge to the private inbox. The owner answer returns through that bridge. Submitted, native acknowledged and completed are distinct receipts. — Observed bounded question route. Each step has separate state; an observer-only session cannot be silently adopted.

Bounded browser-answer experiments completed through pinned Windows Codex and Claude channels. They prove those specific semantic answer paths. They do not prove every native prompt is discoverable, a filesystem action was approved, or any independently started chat can be controlled.

Read the stages

Stage	What it establishes
Pending	An explicit supported question is awaiting an answer.
Answered	The owner’s answer is saved for that question/revision.
Submitted	The bridge attempted delivery to the native transport.
Native acknowledged	The owning native protocol accepted that answer.
Completed	The bounded native interaction reached its completion evidence.
Uncertain / stale	Delivery or transport identity needs reconciliation. Do not assume success or replay.

Permission waits stay explicit

A semantic answer is not a blanket approval for later tool execution. Native provider permissions remain in force. An idle session, old report or stopped stream does not prove that a human approval is needed. Act on an explicit supported question or permission record; otherwise preserve the uncertainty.

Reporting, history capture, question bridging and execution grants are separate. A reporting credential cannot stand in for an execution permission. Cancellation before a bridge claims work is different from cancellation after native submission; the latter cannot promise undo.

Operator-only bridge command

delegator questions bridge --config ABSOLUTE_PRIVATE_CONFIG_PATH

This requires a version-compatible native executable, a reviewed private config, exact identity receipt, fresh owner grant and explicit start signal. It is not a generic “attach to any existing chat” command. Do not run a second bridge to resolve an uncertain first one.