Documentation

A Clean Framework application starts with explicit server responsibilities: routes select controllers, use cases enforce rules, repositories handle persistence and native views render useful HTML.

Keep request parsing and response selection in controllers. Put business operations and transaction ownership in application services, bind SQL values in repositories and escape text at the point it is rendered. Session authentication, authorization and CSRF checks run before protected controller work.

For progressive enhancement, build a complete server-rendered route first. A native link or form must still reach a meaningful result. Add FrontBaseJS behavior around that contract, and let the server remain authoritative for authentication, validation and access decisions.

Before adopting a release, verify the exact framework commit, its PHP support window and required extensions. This KoniKode development site targets PHP 8.5. Framework release qualification, proprietary licensing and an application deployment review are distinct steps.

• Map routes, controllers, use cases, persistence and views before writing integrations
• Test denied access and interrupted requests as well as successful pages
• Use the protected library for version-specific implementation details