Ideas across the ecosystem
Three layers. One place to think, build, and share what we learn.
Choose a topic to explore AI agents, application architecture, runtime and rendering, or real product workflows. Browse twelve articles at a time, newest first.
Showing 1–12 of 35 articles
Ideas and practical guides across Semitexa OS, Platform, and Framework.
The same live order board built twice: Laravel with Livewire and Reverb, and Semitexa with Server-Sent Events. Code, measured latency, moving parts, and where each one is worse.
Compare the two builds →MCP replaced its HTTP+SSE transport with Streamable HTTP. What changed, when to use stdio, Streamable HTTP or plain SSE, and how Semitexa uses stdio for MCP and SSE for the browser.
Choose the transport →How EventSource reconnects, what Last-Event-ID really does, and how a server replays missed SSE events or tells the page to re-sync. With two bugs we shipped.
Recover the missed events →Prompt management for PHP: prompt templates with ids, fail-closed rendering, a preview of what the model receives, per-tenant overrides and drift checks.
Open the prompt catalog →Broken access control and IDOR top the OWASP list, and AI agents forget the check. See how Semitexa makes every PHP route declare who may call it.
See the access contract →What design tokens are, how one token contract gives dark mode with light-dark(), and how to let an LLM restyle an app by choosing, never writing CSS.
Read the token contract →Harness engineering for PHP: guides and sensors around a coding agent, the PHP tools for each, running the right checks per change, and a Laravel starter.
Build the harness →Claude Code reads AGENTS.md since 2.1.277, but only without a CLAUDE.md. How to keep one instruction file for every agent, and how ai:verify keeps it short.
Keep one file →Follow one click from a fingertip through TLS, undersea fiber and a Swoole worker in Helsinki back to every open screen, then press a live Say hello button.
Follow one click →Laravel Octane, Hyperf and Semitexa compared: what each keeps in memory, where request state lives, tenancy, live pages, AI agents, and when to choose which.
Compare the three →SSE vs WebSockets for live dashboards and tables: who talks, what proxies and PHP runtimes change, and the SSE plus POST pattern a live grid runs on.
Choose the transport →A PHP data grid driven by Server-Sent Events: the server owns the view, re-runs it on change and sends only the rows that moved. Watch the wire live.
Watch the grid on the wire →What would help you move forward?
Your brief goes to our team. It isn’t published on the website. A high-level overview is enough to start.
Explore the offers and our work