[strategy] RFC: non-developer personas — in scope or out?

[EmersonBraun]

The plan today is 100% developer-tooling. No story for marketing user defining a campaign agent in a UI, CEO dashboard for agent KPIs, support agent using a chat console, ops monitoring agent runs.

Strategic question: is this intentional? If AgentsKit is the 'Vercel of agents', Vercel itself shipped a non-dev surface (v0).

Force a written decision via RFC. If out, document explicitly in ROADMAP-PRD Out of Scope. If in, spawn the dependent issues:

• ops monitoring dashboard (already covered partially by [F4] #87 — AgentsKit Cloud (hosted runtime) #200 Cloud)
• support-console template (HITL chat triage)
• no-code campaign builder on top of agentskit flow

Acceptance

• RFC merged in rfcs/
• ROADMAP-PRD updated either way

[EmersonBraun]

This is a meta / planning issue (RFC, plan refresh, release-timing decision) that needs maintainer judgement and stakeholder input rather than code changes. Leaving open.