Krow/Krow-workspace
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(m4): add explicit actor mapping text to both scenarios

Browse Source
This commit is contained in:
zouantchaw
2026-02-25 11:17:54 -05:00
parent 50c7116d20
commit 67cf5e0e4c
1 changed files with 40 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
docs/MILESTONES/M4/planning/m4-core-data-actors-scenarios.md
View File

@@ -38,6 +38,26 @@ Context:
2. Business is `Google Mountain View Cafes`. 2. Business is `Google Mountain View Cafes`.
3. Legendary uses its own workforce, and can still route overflow to approved vendors. 3. Legendary uses its own workforce, and can still route overflow to approved vendors.
Actor mapping (text):
1. Tenant: `Legendary Event Staffing and Entertainment` (the company using Krow).
2. User: `Wil` (ops lead), `Maria` (client manager), `Ana` (worker).
3. TenantMembership:
4. `Wil` is `admin` in Legendary tenant.
5. `Maria` is `manager` in Legendary tenant.
6. `Ana` is `member` in Legendary tenant.
7. Business: `Google Mountain View Cafes` (client account under the tenant).
8. Vendor: `Legendary Staffing Pool A` (or an external approved vendor).
9. Workforce/Staff: `Ana` is a staff profile in workforce, linked to certifications and assignments.
10. StakeholderType: `buyer`, `operator`, `vendor_partner`, `workforce`, `procurement_partner`.
11. StakeholderProfile:
12. `Google Procurement` = `buyer`.
13. `Legendary Ops` = `operator`.
14. `FoodBuy` = `procurement_partner`.
15. StakeholderLink:
16. `Google Procurement` `contracts_with` `Legendary Ops`.
17. `Legendary Ops` `sources_from` `Vendor`.
18. `Google Procurement` `reports_through` `FoodBuy`.
```mermaid ```mermaid
sequenceDiagram sequenceDiagram
participant Tenant as "Tenant (Legendary)" participant Tenant as "Tenant (Legendary)"
@@ -60,6 +80,26 @@ Context:
2. Business is `NVIDIA Campus Dining`. 2. Business is `NVIDIA Campus Dining`.
3. Peakline primarily fulfills demand through external approved vendors. 3. Peakline primarily fulfills demand through external approved vendors.
Actor mapping (text):
1. Tenant: `Peakline Events` (another staffing company using Krow).
2. User: `Chris` (operations coordinator), `Nina` (client manager), `Leo` (worker).
3. TenantMembership:
4. `Chris` is `admin` in Peakline tenant.
5. `Nina` is `manager` in Peakline tenant.
6. `Leo` is `member` in Peakline tenant.
7. Business: `NVIDIA Campus Dining` (client account under the tenant).
8. Vendor: `Metro Staffing LLC` (approved external vendor for this tenant).
9. Workforce/Staff: `Leo` is a workforce profile fulfilled through Metro Staffing for assignment and attendance.
10. StakeholderType: `buyer`, `operator`, `vendor_partner`, `workforce`, `procurement_partner`.
11. StakeholderProfile:
12. `NVIDIA Procurement` = `buyer`.
13. `Peakline Ops` = `operator`.
14. `FoodBuy Regional` = `procurement_partner`.
15. StakeholderLink:
16. `NVIDIA Procurement` `contracts_with` `Peakline Ops`.
17. `Peakline Ops` `sources_from` `Metro Staffing LLC`.
18. `NVIDIA Procurement` `reports_through` `FoodBuy Regional`.
```mermaid ```mermaid
sequenceDiagram sequenceDiagram
participant Tenant as "Tenant (Peakline Events)" participant Tenant as "Tenant (Peakline Events)"