Deliver role-aware shell (sidebar, breadcrumbs, quick search, tables, detail/create layouts), locale-ready pages, shared backend/feature docs, and Vercel project config so HR, finance, and members can demo against typed mocks. Co-authored-by: Cursor <cursoragent@cursor.com>
2.4 KiB
2.4 KiB
Open items (cross-repo)
Tracked decisions and flags that span Gishen-B2B, Admin, Ecom, and Mobile.
Workspace: /Users/kirukib/Desktop/Yaltopia Project/Gishen-B2B
Active
1. Checkout entitlement split ownership
| Field | Value |
|---|---|
| Status | Open — default recommendation documented |
| Description | Basket split (org credit vs member gateway payment) must appear in Ecom Web / Mobile checkout, not only B2B |
| Default recommendation | Single shared implementation owned with Gishen-Ecom; shared backend calculates split |
| B2B scope | Show allowance_remaining on /me; link to Ecom for checkout |
| Decision needed | Confirm shared package vs per-repo duplicate UI |
| References | gishen-ecom.md, ../backend/endpoints/packages.md |
Action: Product/engineering leads confirm owner before Ecom checkout sprint.
2. SSO / deep link B2B member → Ecom storefront
| Field | Value |
|---|---|
| Status | Open |
| Description | How member session propagates from B2B portal to Ecom cart |
| Options | (a) Shared auth token, (b) customer_id query + magic link, (c) full SSO provider |
| B2B impact | /me CTA "Shop with coverage" |
3. Pending org draft packages
| Field | Value |
|---|---|
| Status | Decided — default block |
| Description | Can SUPER_USER draft packages while pending_activation? |
| Decision | Default: block entitlements until active. Packages may be saved as draft only. |
| Spec | ../backend/entities/package.md |
Watch list (informational)
Telegram Mini App
Rides Ecom backend spec — no B2B action.
Procurement vs Stock Manager
Admin-only overlap — ignore in B2B.
Production auth provider
Mock demo login ships first. OAuth/SSO provider TBD — track in shared platform auth spec.
Custom domain
b2b.gishenpharmacy.org optional after first Vercel deploy.
Resolved
None yet — move items here when decided.
How to update
When an open item is resolved:
- Move to Resolved with decision date and owner.
- Update affected
docs/backend/entities/endpoints. - Update
../features/INDEX.mdif routes or ownership change. - Notify sibling repo spec sheets (Admin/Ecom).