This section describes how MemberPulse V3 should be implemented on Convex with:Documentation Index
Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- A normalized, queryable data model
- Strict tenant scoping (
clientId) and isolation - Secure handling of PII and secrets
- Explicit domain rules enforced server-side
Start here
Normalization
What becomes a table vs embedded data, and where join tables are required.
Tenant Scoping
How we guarantee isolation in a shared Convex deployment.
Security
PII, secrets, and authorization patterns.
Domain Rules
Invariants and lifecycle rules enforced in Convex mutations.
schema.ts
The proposed Convex schema and indexes.
Features
Convex Implementation
Acceptance Criteria
Frontend
- Developer-facing configuration and usage is documented and internally consistent.
Backend / API
- Convex implementation matches the rules and contracts described on this page.
Permissions
- Tenant scoping and access controls are enforced as described.
Business Rules
- Domain rules/invariants are enforced as described.
Error Handling
- Access violations and validation failures produce deterministic errors.