Runtime Model
Early Architecture Attempts
The pragmatic early design that predated Cotomy: PHP routing, template friction, and the first DOM-wrapper impulse.
Architecture
Runtime Model
Building Systems Alone
How working as a solo internal engineer reshaped my architectural thinking.
Core Principle
Form AJAX Standardization
Why Cotomy standardizes query-string search, AJAX submit, and shared form contracts to control long-term cost in business systems.
Core Principle
Page Lifecycle Coordination
Why Cotomy keeps page lifecycle and cross-form coordination in CotomyPageController instead of scattering ready logic across screens.
Core Principle
CotomyElement Boundary
A design-focused note on why Cotomy starts from CotomyElement and treats DOM handling as an architectural boundary, not a UI convenience API.
Core Principle
UI Intent and Business Authority
UI should declare operational intent, while business authority must remain in business logic and operational contracts.
Core Principle
Runtime Boundaries and Operational Safety
Operational safety in business UI depends on a clear runtime boundary between screen intent and execution structure.
Core Principle
API Protocols for Business Operations
In business UI, form submission and API calls are the same operational protocol, not separate patterns.
Core Principle
Form State and Long-Lived Interaction
Form state in business UI is not just input values. It is a long-lived working context that breaks when several mutation paths redefine it without one design rule.
Core Principle
Screen Lifecycle and DOM Stability
In long-lived business UI, the screen is a working surface with a lifecycle, not a transient render.
