Reference · NyxID Cool Demo Brainstorm v3 (Marketing strategy doc)

[nwnwnw413]

Context

Surfacing a Marketing-side brainstorm doc as reference for cool demo / showcase planning. Not a task — sharing in case useful when you're thinking about dashboard polish, audit-log surface, or any video work down the line.

Source (Marketing repo): Marketing/Strategy/cool-demo-brainstorm-2026-04-27.md

Quick summary

Anchored to ADR-002 positioning (Agent Connectivity Gateway) and M0/M1 primary ICP (self-hosted n8n user managing 10-50 API keys). Demos all built around the canonical 5-step quickstart: docker run → add credential → wrap as MCP → claude mcp add → real call.

Portfolio proposed:

• Primary · n8n self-hosted — ~60 sec terminal + dashboard split-screen. Ada types in Claude Code, Claude touches a real n8n workflow (status check / re-run / error) via NyxID-injected credential. Audit log appears live.
• Stretch · HA — terminal types → living room light turns off → audit log shows tool=ha.turn_off agent=claude-code. Reuses r/homeassistant viral path (entry chore(mobile): remove google-services.json from version control #29 hit 262→298 ups).
• Stretch · Unitree — terminal types → robot dog walks to kitchen, photo of food bowl. Highest visceral score, gated on team sync.

NyxID components the demo surfaces on camera

Each demo step in the brainstorm is anchored to specific backend code. These are the parts whose UX / audit-log polish / latency would show up directly in the video:

• backend/src/services/mcp_service.rs — utoipa derive → OpenAPI → MCP tools at runtime (the "Wrap as MCP Server" click)
• backend/src/handlers/proxy.rs — reverse proxy + credential injection (the "Claude never sees the raw key" claim)
• backend/src/services/agent_binding_service.rs — per-agent scoping (claude-code vs cursor see different tool sets)
• backend/src/services/node_ws_manager.rs — NAT traversal (the "Claude in cloud reaches my homelab" claim)
• Audit log dashboard surface — wants to be visually prominent in the video

If any of these have rough edges that'd be obvious on camera (audit log latency, dashboard polish, quickstart friction in the 5-step flow), flagging them helps — small engineering polish disproportionately improves demo quality.

Tied funnel context (FYI)

The brainstorm also documents a funnel blocker from Research/2026-04-21-funnel-cro-audit.md: past 0 redemption was caused by 3 simultaneous breakages — README hero missing one-liner + demo gif, hosted mobile UX viewport user-scalable=no killing mobile signup, registration flow not yet end-to-end audited. Demo without those fixed = repeat of 04-22 r/homeassistant (262 ups → 0 redemption). Some of these touch engineering surface.

What's in the full doc

10 sections including: §3 ICP detail (what an n8n self-hosted user does daily), §4 visual script with terminal output mock, §5 stretch demos with specific NyxID components per demo, §6 funnel-fix gates, §7 metric anchoring (north stars + attribution tracking), §10 canonical reference list.

No action requested

Just leaving this here. If anything looks structurally wrong from an engineering POV — a component that doesn't exist that way, a 5-step quickstart timing that's unrealistic, a demo claim the code doesn't support yet — push back. This is v3 after two prior rewrites, so iteration is expected.

[chronoai-bot]

github-devloop intake decision: decline
Service class: background

Reason:
Established intake practice reserves automation for implementable work; this is explicitly a reference/marketing brainstorm with "Not a task" and "No action requested", not an implementation request.