Your API Changed. Did Your Docs Notice?
Follow Semitexa's Payload, Handler and Resource pipeline to see how API docs and contract facts stay tied to the code that actually runs.
Follow a contract change to the client →Ideas across the ecosystem
Articles for the whole of Semitexa.
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–6 of 6 articles
Architecture & business rules
Follow requests, contracts, domain decisions, and persistence through explicit application boundaries.
Domain-Driven Design in Semitexa: Make Business Decisions Explicit
Follow a fulfilment decision through domain policy, bounded contexts, contracts and version-checked persistence, and see how Semitexa supports DDD in PHP.
Follow the business decision →From Database Rows to Business Rules: Domain Models in Semitexa
Follow an API credential through a persistence resource, a mapper, immutable domain behavior and repository writes: where SQL ends and business rules begin.
Trace the domain model boundary →From PHP Attributes to SQL: Inside Semitexa Schema Sync
See how independent modules add columns to one table and how Semitexa turns PHP attributes into a merged schema, a comparison and a safe SQL plan.
Trace the schema sync pipeline →From URL to HTML: Following a Semitexa Request
No controller required: follow one real Semitexa request through Payload, Handler, Resource, and Template, and see who takes over each controller job.
Follow the four-stage flow →Three Layers, One Workflow: OS, Platform, and Framework
Where does a feature belong in Semitexa? A practical map of OS experience, Platform interface, and Framework execution, with a clear visual guide.
Read the three-layer guide →