CotomyPageController in Practice
Design screen entry first with CotomyPageController, then structure CRUD flow around one endpoint boundary.
Design screen entry first with CotomyPageController, then structure CRUD flow around one endpoint boundary.
Binding, creating, and managing UI structure with CotomyElement in real DOM-centric workflows.
UI should declare operational intent, while business authority must remain in business logic and operational contracts.
Operational safety in business UI depends on a clear runtime boundary between screen intent and execution structure.
In business UI, form submission and API calls are the same operational protocol, not separate patterns.
Form state in business UI is a sustained working context, not a transient event payload.
In long-lived business UI, the screen is a working surface with a lifecycle, not a transient render.
Form submission is a system-level protocol, not per-screen glue code.
The first structural problem Cotomy set out to solve: CSS as a boundary issue, not a styling preference.
Patch release that fixes request keepalive handling on page unload.