Edu-Carone-SA puts legal and security gates ahead of production
This fork starts with a clear message: no commercial rollout until its licensing and security risks are understood and closed.
Edu-Carone-SA has laid down the governance scaffolding before making product claims. The fork now documents its current and intended architecture, hosting and data-storage choices, security threats, and the decisions behind them.
Most notably, it treats AGPL compliance as a production blocker, reflecting the obligations attached to the upstream project's licence. It also records software component inventories, giving reviewers a clearer view of the dependencies that would sit beneath a deployed legal-AI service.
The work is organised around sprint checkpoints, making the fork's hardening roadmap easier to follow on GitHub.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?