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

replace the "Krow" with "KROW"

Browse Source
This commit is contained in:
Achintha Isuru
2026-02-26 15:13:26 -05:00
parent f9c2d822e6
commit b8d07380c0
60 changed files with 225 additions and 227 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/MILESTONES/M3/demos/m3-client-note.md
View File

@@ -18,7 +18,7 @@
**Client Account (Business User):**
- Email: `legendary@krowd.com`
- Password: `Demo2026!`
- Client Name: "Krow"
- Client Name: "KROW"
**Staff Account (Worker):**
- Phone: `+15557654321`

2
docs/MILESTONES/M3/demos/m3-notes.md
View File

@@ -20,7 +20,7 @@
- Suggestion: Use Google Maps to suggest only city names. Currently users can type anything, which will cause misspellings and inconsistent data. Important for the max distance feature.
**Home page:**
- Same flickering issue — shows "Krower" briefly before displaying the real name.
- Same flickering issue — shows "KROWER" briefly before displaying the real name.
**Profile page:**
- Phone number should be read-only, or require re-verification if changed.

2
docs/MILESTONES/M3/demos/m3.md
View File

@@ -30,7 +30,7 @@ This demo showcases the progress of the milestone 3.
**Client Account (Business User):**
- Email: `legendary@krowd.com`
- Password: `Demo2026!`
- Client Name: "Krow"
- Client Name: "KROW"
**Staff Account (Worker):**
- Phone: `+15557654321`

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

@@ -57,7 +57,7 @@ Context:
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).
1. Tenant: `Legendary Event Staffing and Entertainment` (the company using KROW).
2. User: `Wil` (ops lead), `Maria` (Google client manager), `Omar` (Google procurement approver), `Jose` (vendor scheduler), `Ana` (worker).
3. TenantMembership:
4. `Wil` is `admin` in Legendary tenant.
@@ -109,7 +109,7 @@ Context:
3. Peakline primarily fulfills demand through external approved vendors.
Actor mapping (text):
1. Tenant: `Peakline Events` (another staffing company using Krow).
1. Tenant: `Peakline Events` (another staffing company using KROW).
2. User: `Chris` (operations coordinator), `Nina` (client manager), `Sam` (vendor manager), `Leo` (worker).
3. TenantMembership:
4. `Chris` is `admin` in Peakline tenant.

26
docs/MILESTONES/M4/planning/m4-roadmap-csv-schema-reconciliation.md
View File

@@ -13,19 +13,19 @@ This avoids two failure modes:
## 2) Inputs reviewed
All 13 roadmap exports from `/Users/wiel/Downloads`:
1. `Krow App – Roadmap - Business App_ Google, Nvidia.csv`
2. `Krow App – Roadmap - Client_ Google, Nvidia.csv`
3. `Krow App – Roadmap - Compass- The Operator.csv`
4. `Krow App – Roadmap - Employee App.csv`
5. `Krow App – Roadmap - Features.csv`
6. `Krow App – Roadmap - FoodBuy- Procurement.csv`
7. `Krow App – Roadmap - KROW Dashboard.csv`
8. `Krow App – Roadmap - Offenses.csv`
9. `Krow App – Roadmap - Partner.csv`
10. `Krow App – Roadmap - Roadmap.csv`
11. `Krow App – Roadmap - Sectors_ BA, Flik ( The executors).csv`
12. `Krow App – Roadmap - The Workforce_ Employees.csv`
13. `Krow App – Roadmap - Vendor_ Legendary (Staffing).csv`
1. `KROW App – Roadmap - Business App_ Google, Nvidia.csv`
2. `KROW App – Roadmap - Client_ Google, Nvidia.csv`
3. `KROW App – Roadmap - Compass- The Operator.csv`
4. `KROW App – Roadmap - Employee App.csv`
5. `KROW App – Roadmap - Features.csv`
6. `KROW App – Roadmap - FoodBuy- Procurement.csv`
7. `KROW App – Roadmap - KROW Dashboard.csv`
8. `KROW App – Roadmap - Offenses.csv`
9. `KROW App – Roadmap - Partner.csv`
10. `KROW App – Roadmap - Roadmap.csv`
11. `KROW App – Roadmap - Sectors_ BA, Flik ( The executors).csv`
12. `KROW App – Roadmap - The Workforce_ Employees.csv`
13. `KROW App – Roadmap - Vendor_ Legendary (Staffing).csv`
Parsed signal:
1. 983 non-empty task lines.