Morrow

Community

Open source needs an operating model.

Morrow publishes code alongside the conditions that make outside review, contribution, and responsible use possible.

Public foundation

The source repository has a clean public history, Apache-2.0 license, contribution rules, private security reporting route, governance model, and inspectable release checks.

How decisions should work

Business modules own their policies and public interfaces. Architectural decisions should be recorded, reviewable, and small enough that a contributor can understand why a boundary exists. Maintainers remain responsible for integrating work and verifying release evidence.

Current status

Morrow Desk remains an early V1 foundation, not a production-readiness claim or a complete ERP. Development now happens in the public repository; real hosted deployments act as private proving environments for reviewed commits.