Review the exact context and capability request.
The route is planned and no transport or authority has been granted.
Buildout · Visual Language · specimen data
Waiting for approvalAuthorised handoff study
Design the bounded cross-provider handoff flow tracked by issue #37.
1 of 4 evidenced
Current stepReview the exact context and capability request.
Work itemsNot represented
SessionsNot represented
ProvidersKimi CLI · ChatGPT Web
These controls are static review specimens. They do not resume a session, grant authority, send a handoff, or mutate GitHub.
Human attention
The blocked transition and safe decision share one view.
Waiting for approval
Work items
Bounded tasks retain owners, outputs, and evidence.
A completed label is not shown without adjacent completion evidence.
No work-item detail represented
This summary buildout preserves its state and evidence without inventing task rows.
Sessions
Provider, connection, agent, and session stay distinct.
Desired and actual state appear together. No session is merged merely because it contributes to the same buildout.
No session detail represented
The buildout summary does not invent a provider connection.
Approvals
Authority is exact, expiring, and separate from execution.
No approval represented
This buildout has no consequential request in the fixture.
Artifacts and GitHub projection
Outputs preserve producer, ancestry, and availability.
Activity
Actor, event, affected object, and evidence remain attributable.
No detailed activity represented
The summary evidence remains visible without inventing chronological records.