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.
Cotomy
Core Principle
CotomyPageController in Practice
Design screen entry first with CotomyPageController, then structure CRUD flow around one endpoint boundary.
Core Principle
Working with CotomyElement
Binding, creating, and managing UI structure with CotomyElement in real DOM-centric workflows.
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.
Core Principle
Form Submission as Runtime
Form submission is a system-level protocol, not per-screen glue code.
Core Principle
HTML and CSS as One Unit
The first structural problem Cotomy set out to solve: CSS as a boundary issue, not a styling preference.
