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.
Cotomy Problem Series
Structural problems in web application development and the architectural ideas that led to Cotomy.
Core Principle
Form Submission as Runtime
Form submission is a system-level protocol, not per-screen glue code.
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 State and Long-Lived Interaction
Form state in business UI is a sustained working context, not a transient event payload.
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
Runtime Boundaries and Operational Safety
Operational safety in business UI depends on a clear runtime boundary between screen intent and execution structure.
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
Binding Entity Screens to UI and Database Safely
Entity structure and UI controls are often bound through fragile string matching. This article explores the structural gap and Cotomy’s mitigation approach.
Core Principle
Screen State Consistency in Long-Lived UIs
State failures in business UIs are usually not isolated bugs. They appear when DOM state, in-memory state, and server state have no explicit ownership and synchronization rules.
Core Principle
Synchronizing UI and Server State
Server-side postback screens were limited, but they kept one execution path. Once Ajax became the main update mechanism, keeping display, input state, and server truth aligned became a structural problem.
