OpenParcelBox/firmware/constraints.md

Firmware Constraints

Architecture

• Development is based on Zephyr RTOS.
• The code must remain modular.
• Business logic, hardware access, and communications must be clearly separated.

Power Consumption

• Low-power modes should be used whenever possible.
• Wake-up should happen only on meaningful events.

Maintenance

• Errors should be logged or exposed through diagnostics.
• Configuration must be documented.
• The update procedure must be documented.

Security

• Commands must be authenticated.
• Sensitive data must be stored securely.
• The firmware must remain usable without any mandatory cloud service.