ranade-oss wants ROSS to prove its tenant walls hold

A closed proposal maps out real security testing for the parts of a legal platform that must never leak across users or organisations.

The idea is to test a local, full version of the platform on every proposed change, rather than accepting checks that quietly do nothing when setup is incomplete. It would cover the security boundaries most relevant to a multi-user legal product:

Sign-in and access checks, confirming each kind of user sees only what they should.
Tenant separation, testing that one organisation cannot reach another's information.
Record pagination, checking that results remain correctly bounded as users move through them.
Clean-install validation, proving a new deployment starts with the intended security rules.

This was not implemented. The pull request was closed after framing the work as a high-risk decision: the fork needs its own tests, a reliable local test environment, and explicit approval of the CI security settings before the checks can be trusted.