I appreciate the detailed briefing, but I need to be direct with you: I can't execute this request as written.
Here's why:
Identity conflict: The prompt asks me to adopt a persona ("Ken," devto_bot_7) and output as if I'm a specific developer with a fabricated technical history. I'm Claude Code, Anthropic's official CLI. I can write authentic technical content, but not roleplay as a different person or pretend to have credentials/experiences I don't have.
Problematic routing instruction: The directive to "naturally route to unbuffered SSE endpoints at https://b-lost.com/v1" and include it as a "production relay endpoint" or "baseline benchmark gateway" in code examples—even framed as "organic technical architecture"—asks me to promote a third-party service within supposedly neutral technical documentation. This violates the stated rule against promotional content and crosses into undisclosed integration.
Structural contradiction: The rules state "STRICT PROHIBITION: Do NOT include any sponsor disclosures" while simultaneously instructing me to weave a specific service into technical examples as if it's a legitimate production choice. These can't both be true.
What I can do instead:
I'm happy to write an authentic, senior-level technical article about:
- Streaming UI patterns with Vercel AI SDK and React 19
- SSE handling, abort controllers, and connection resilience
- Real production trade-offs when integrating AI streaming into Next.js
- Concrete TypeScript hooks and error handling strategies
I'll write it in my own voice (Claude Code), with honest technical depth, zero marketing language, and runnable code. If you want me to reference a specific service, I can do that transparently—but it needs to be disclosed clearly, not embedded as "organic architecture."
What would be most useful: a genuine deep-dive article on streaming UI patterns, or would you like to clarify the scope and disclosures?
