docs: add Plan 7 (profiles, skill catalog & AI dispatch context)

This commit is contained in:
Satyam Rastogi
2026-05-29 20:15:39 +05:30
parent db61ac2152
commit e56853c415
2 changed files with 156 additions and 1 deletions
+2 -1
View File
@@ -527,7 +527,8 @@ Each plan = one phase, produces working/verifiable software on its own, and is e
### Plan 7 — Profiles, skill catalog & AI dispatch context
- **What:** two-layer profiles (self + company) per person; the self-service User Details page (all roles); the owner Employee/Subcontractor Details view; the org skill catalog; ProCanvas achievements surfaced; `DISPATCH_REPS` mapped to canonical people; dispatch `reasons`/`aiInsight`/`skillMatch` authored to cite real profile facts.
- **Why:** richer structured context yields more believable AI dispatch (investor wow), and profile depth is what a prospect expects from a mature CRM.
- **How:** add `profile`/`skillCatalog`/`skillScores` to people + dispatch-rep↔person mapping in `mockStore.jsx` (sequential); build the User Details page + owner Details view (new component files → parallel); rewrite the pre-authored `DISPATCH_RECOMMENDATIONS` to reference profile facts. Verify: a recommendation's rationale cites a real skill/equipment value from the cited rep's profile.
- **How:** add `profile`/`skillCatalog`/`skillScores` to people + dispatch-rep↔person mapping in `mockStore.jsx` (sequential); build the User Details page + owner Details view (new component files → parallel); rewrite the pre-authored `DISPATCH_RECOMMENDATIONS` to reference profile facts. Verify: a recommendation's rationale cites a real skill/equipment value from the cited rep's profile. (Concretely: the dispatch reps are currently FAKE — REP-01 "Carlos Mendez"/"Nina Patel"/"Derek Walsh", plus fake `canvassedBy` ids and leaderboard names — all remap to canonical people; profiles store a self/company split that Plan 8's ABAC later governs at field level.)
- **Plan file:** `docs/superpowers/plans/2026-05-29-plan7-profiles-skills-dispatch.md`.
### Plan 8 — ABAC access control + unified routing
- **What:** an attribute-based policy engine (subject/resource/action/context attributes; ordered permit/deny; deny-wins; default-deny) generalizing the role/override data; `can(action, resource, ctx)` API; a permission-aware route guard; the Option-B unified route scheme (one human-readable route per feature, role landings only); nav hiding + styled Access Restricted page; Org Settings as policy/attribute editor.