# Jackson Meeting Participant + Two-Way Context Bridge Plan — 2026-05-11

Neal clarified the target: this lane is **not** the private coaching copilot. It is Jackson participating in meetings as Neal's chief of staff/operations manager.

## Product target
- Jackson joins/participates in Zoom meetings with full current awareness.
- Jackson can listen to live meeting context, reason from Neal/AURA context, and contribute in-meeting.
- Meeting context returns to Jackson afterward as durable relationship/project memory.
- This can eventually replace Fireflies when the full capture, memory, and participation loop is reliable.

## Current safe test shape
1. Recall.ai gets the bot into an internal Zoom only after Neal explicitly approves that join.
2. Jackson listens through the meeting transcript stream.
3. Zoom chat participation stays exact-approval-gated for now: Jackson drafts or proposes; Neal approves the actual send.
4. The private sidecar/coaching interface is parked as a separate lane.

## Bridge we need to build toward
- **Inbound awareness:** before each meeting, Jackson gets the relevant person/project/room brief, current commitments, open questions, and meeting purpose.
- **Live participation:** live transcript turns into concise context for Jackson; Jackson can propose approved chat or, later, voice participation.
- **Outbound memory:** after the meeting, summary, decisions, commitments, people context, and follow-ups write back to Jackson/ACC relationship memory without raw credential or transcript sprawl.
- **Approval gates:** no external/prospect meeting participation, Zoom chat send, voice output, or broad memory write without the explicit gate for that stage.

## Jackson voice and business awareness requirement
- Jackson enters meetings as Jackson, not as a generic Zoom assistant.
- His response context must include APS business context, Neal relationship memory, current room or person context, open commitments, and the live meeting transcript.
- His output should use Jackson voice and Opus level reasoning: warm, direct, commercially aware, strategic, and able to challenge weak assumptions when useful.
- The current internal Recall.ai path can prove transcript, wake phrase, and approved Zoom chat plumbing. The full version still needs a bridge from live transcript into Jackson's richer context and reasoning stack before any client or prospect use.

## Next implementation checkpoint
Prove one internal Zoom loop end-to-end: Recall bot admitted → transcript webhook receives live words → Jackson receives compact context → Jackson produces a draft contribution → approved chat send path is available but not autonomous.

Created by Bernie from the scheduled inbox watcher at 2026-05-11T22:41:00Z.