Verified against Semitexa Ultimate 2026.09.19.1020

Beyond Controllers

Semitexa does not treat controllers as the universal container for transport, orchestration, and rendering.

Canonical split

• payload owns inbound HTTP structure
• handler owns the use case
• resource owns response data and metadata
• template owns presentation

What this avoids

• transport and business logic collapsing into one unstable class
• hidden rendering state
• ad hoc arrays passed across unclear boundaries

Why this matters

The framework stays readable because each layer owns one job. That keeps growth additive instead of turning every new feature into another oversized controller.