docs(m4): add business/vendor memberships and clean planning docs
This commit is contained in:
@@ -71,13 +71,15 @@ What already exists and is useful:
|
||||
|
||||
Current structural gaps for roadmap scale:
|
||||
1. No tenant boundary key on core tables (`tenant_id` missing).
|
||||
2. No first-class stakeholder profile/link model for buyer/operator/partner/sector relationships.
|
||||
3. Attendance history is not first-class (check in/out only inside `applications`).
|
||||
4. No offense policy, offense event, or enforcement action tables.
|
||||
5. Finance is coarse (invoice + recent payment), missing line items, payment runs, remittance artifact model.
|
||||
6. Sensitive bank fields are currently modeled directly in `accounts` (`accountNumber`, `routeNumber`).
|
||||
7. Many core workflow fields are JSON (`orders.assignedStaff`, `orders.shifts`, `shift.managers`, `assignment.managers`).
|
||||
8. Money still uses float in critical tables.
|
||||
2. No first-class business user partitioning table (`business_memberships` missing).
|
||||
3. No first-class vendor user partitioning table (`vendor_memberships` missing).
|
||||
4. No first-class stakeholder profile/link model for buyer/operator/partner/sector relationships.
|
||||
5. Attendance history is not first-class (check in/out only inside `applications`).
|
||||
6. No offense policy, offense event, or enforcement action tables.
|
||||
7. Finance is coarse (invoice + recent payment), missing line items, payment runs, remittance artifact model.
|
||||
8. Sensitive bank fields are currently modeled directly in `accounts` (`accountNumber`, `routeNumber`).
|
||||
9. Many core workflow fields are JSON (`orders.assignedStaff`, `orders.shifts`, `shift.managers`, `assignment.managers`).
|
||||
10. Money still uses float in critical tables.
|
||||
|
||||
Connector boundary gap:
|
||||
1. 147 Data Connect mutation operations exist.
|
||||
@@ -88,10 +90,12 @@ Connector boundary gap:
|
||||
### 6.1 Tenant and stakeholder graph
|
||||
1. `tenants`
|
||||
2. `tenant_memberships`
|
||||
3. `stakeholder_types`
|
||||
4. `stakeholder_profiles`
|
||||
5. `stakeholder_links`
|
||||
6. `role_bindings` (scoped to tenant/team/hub/business/vendor/resource)
|
||||
3. `business_memberships`
|
||||
4. `vendor_memberships`
|
||||
5. `stakeholder_types`
|
||||
6. `stakeholder_profiles`
|
||||
7. `stakeholder_links`
|
||||
8. `role_bindings` (scoped to tenant/team/hub/business/vendor/resource)
|
||||
|
||||
### 6.2 Attendance and timesheet reliability
|
||||
1. `attendance_events` (append-only clock-in/out/NFC/manual-corrected)
|
||||
@@ -124,6 +128,10 @@ Connector boundary gap:
|
||||
```mermaid
|
||||
erDiagram
|
||||
TENANT ||--o{ TENANT_MEMBERSHIP : has
|
||||
BUSINESS ||--o{ BUSINESS_MEMBERSHIP : has
|
||||
VENDOR ||--o{ VENDOR_MEMBERSHIP : has
|
||||
USER ||--o{ BUSINESS_MEMBERSHIP : belongs_to
|
||||
USER ||--o{ VENDOR_MEMBERSHIP : belongs_to
|
||||
TENANT ||--o{ STAKEHOLDER_PROFILE : has
|
||||
STAKEHOLDER_PROFILE ||--o{ STAKEHOLDER_LINK : links_to
|
||||
|
||||
|
||||
Reference in New Issue
Block a user