Page Lifecycle Coordination

Why Cotomy keeps page lifecycle and cross-form coordination in CotomyPageController instead of scattering ready logic across screens.

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.

UI Intent and Business Authority

UI should declare operational intent, while business authority must remain in business logic and operational contracts.

Runtime Boundaries and Operational Safety

Operational safety in business UI depends on a clear runtime boundary between screen intent and execution structure.

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.

Screen Lifecycle and DOM Stability

In long-lived business UI, the screen is a working surface with a lifecycle, not a transient render.

HTML and CSS as One Unit

The first structural problem Cotomy set out to solve: CSS as a boundary issue, not a styling preference.