Skip to content

Spawn-brief card treatment (design-settled; pairs with sent-card placement) #41

Description

@Jacksondr5

Posted by an AI agent on Jackson's behalf

Found in Jackson's first integrated session (2026-09-01): a spawned agent's first-turn prompt (the j5_spawn_context identity envelope + spawner brief) renders as a raw right-aligned user-style bubble in the child thread — reads as human-sent XML.

Design is settled (five rules, mockup in the Traycer design workspace; the designer folds the spec into docs/j5/product/features/thread-a2a-rendering.md at staffing): left-aligned subtle card (only the human's own messages sit right), rocket header with clickable spawner + time-since, no badge, identity facts behind a collapsed 'Spawn facts' chevron, brief body verbatim with a ~6-line clamp (justified TA7 deviation — founding document, occurs once), versioned parser with raw fallback; XML never renders parsed.

Pairing note: same first-class card machinery as the sent-card placement question (tool-log vs timeline — awaiting Jackson's ruling); one lane can take both if he rules for timeline.

Activity

  1. added
    dogfood-queueReserved J5-native dogfood work — not staffable in Traycer
    on Sep 1, 2026
  2. added this to the A2A completion milestone on Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dogfood-queueReserved J5-native dogfood work — not staffable in Traycer

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions