viktor/beadboard
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
beadboard/docs/protocols/2026-02-28-agent-first-ui-decisions.md
zenchantlive c246ceaf21 feat(ux): consolidate Launch Swarm + telemetry UX with minimized strip 
- Removed broken LaunchSwarmDialog (formula-based) from TopBar/LeftPanel
- All Rocket buttons (TopBar, LeftPanel, DAG nodes, social cards) now open
  AssignmentPanel (archetype-based) which actually works
- Every Rocket clears taskId first so assignMode && !taskId condition passes
- Conversation button priority: taskId always shows conversation, not assign panel
- Added TelemetryStrip: minimized right sidebar with status dots when non-telemetry
  panel (conversation/assignment) is active
- Live feed has minimize button → restores last taskId or assignMode
- DAG nodes: Signal icon → restores telemetry feed
- Social button on DAG nodes: single router.push to avoid race (setView + setTaskId)
- Fixed social card message button: opens right panel with drawer:closed (no popup)

Co-Authored-By: Oz <oz-agent@warp.dev>
2026-03-01 18:17:58 -08:00

1.3 KiB
Raw Blame History

Agent-First UI Decisions for Coordination Migration

Date: 2026-02-28
Status: Approved implementation defaults

Decision Summary

  1. Coordination writes are agent-first by default.
  2. Human operators supervise, comment, and override only when needed.
  3. Sessions conversation timeline remains a merged feed (activity + protocol + comments).

Interaction Ownership

Agent-owned by default

  • SEND, READ, ACK, RESERVE, RELEASE, TAKEOVER protocol events.
  • Routine reservation and handoff execution.

Human-owned by default

  • bd comments discussion entries.
  • Override intervention decisions (for blocked/conflict situations).

UI Behavior

  1. Conversation actions (Seen, Accept) emit coord.v1 events via /api/coord/events.
  2. Comment composer includes explicit Comment as username field; value is persisted locally for convenience.
  3. Human comments use provided actor handle (instead of default email) when supplied.
  4. Incursions are computed from reservation projections and shown in sessions feed context.

Identity Policy

  1. Human comments should use user handle (for example zenchant) not raw email whenever available.
  2. Protocol events should use agent identity in actor.
  3. Timeline rendering must preserve actor attribution so human and agent actions stay distinguishable.