JTBD-15 · CRM JTBD validation matrix
Enforce team / tenant permissions
partially supported. Part of the job works and is proved; the rest is named rather than implied. Read what is excluded before planning around it.
What the catalogue records
Production Spine v1 (ADR-038) enforces the permission half: organizations, memberships, eleven bounded permissions in five role bundles, server-authoritative authorization on every route, one tenant per application instance, and a fail-closed actor boundary. The identity underneath it is not validated: the framework authenticates nobody and ships no verifier, so which person holds a membership is only as trustworthy as the deployment adapter, and in local-development mode it is an assertion. This is not shared-database multi-tenancy, and remote exposure still requires a verifier the framework does not provide.
Evidence
Proved by these tests, which run on every push:
tests/actor-fails-closed.test.jstests/production-spine.test.jstests/spine-route-authorization.test.jstests/spine-tenancy-truth.test.jsWhat this status does not mean
A status here describes this repository at this commit, nothing more. It is not a statement about what a CRM should do, and it is not a roadmap commitment. The whole framework ships no authentication, so no status on this page implies you can deploy it. The boundaries are listed in full on the claims ledger.
Other jobs in CRM JTBD validation matrix
- Manage a custom CRM business object end to end — validated end to end
- Associate a generated CRM record with another generated CRM record — validated end to end
- Request commercial approval on a deal — validated end to end
- Manage a deal through pipeline stages — validated end to end
- Capture a lead — validated end to end
- Qualify (or disqualify) a lead — validated end to end
- Convert a qualified lead into Company, Contact and Opportunity — validated end to end
- Manage a custom object with an approval rule — partially supported
All 17 jobs in CRM JTBD validation matrix · the whole catalogue