# KYN POS Design Handoff Rules

The app is intentionally structured so a designer can improve visual layout without seeing or editing core business code.

## Designer-safe areas

```text
/templates
/public/assets/css
/public/assets/js
/public/assets/images
```

## Developer-only areas

```text
/inc
/modules
/sql
/storage
```

## Template rules

Templates may contain:

- HTML markup
- Tabler classes
- simple `foreach` loops for data already prepared by a controller
- escaped output using `e()` or `attr()`
- partial includes using `view_partial()`

Templates must not contain:

- SQL queries
- database credentials
- business calculations
- role/permission rules
- payment/tax/tip calculations
- inventory/resupply logic
- direct `$_POST` mutations
- dynamic file includes

## Why this matters

The goal is to let a layout/design person work quickly on UI without touching the logic that protects sales, payments, permissions, food cost, inventory, or TFF resupply calculations.