#Open questions — DOC-OVERVIEW
Human clarifications from docs/OVERVIEW.md. HQ-1 and HQ-2 need answers before implement treats marketplace money or auth cutover as decided. HQ-3 is closed against the export and needs no answer.
| Id | Question | Why unclear (plain + evidence) | Impact |
|---|---|---|---|
| HQ-1 | Should Stripe Connect, KYC, balances, and payouts be a separate programme from the core TradeForce rebuild? | Plain: The export shows Stripe Connect client settings and per-user Stripe account id/name fields, but no complete in-app Connect onboarding journey to port as ordinary screens. Marketplace money can dominate scope if folded into the app cutover. Evidence: chased stripe_account_id_text, stripe_name_text, public_key:stripe_client_id_test; payment page is schedule/history UI (bTIzV0), not Connect KYC. |
blocks_implement |
| HQ-2 | Which auth provider and credential cutover plan should replace native Bubble Sign Up / Log In / Reset Password? | Plain: Source clearly uses Bubble native auth actions; those sessions and password stores cannot move as-is. Product behaviour on index/reset_pw is known; target identity and how existing users re-authenticate is not. Evidence: bTHpx1 SignUp, bTHop1 LogIn, bTHqz1 SendPasswordResetEmail, bTHrP1 ResetPassword on bTGYf / AAL. |
blocks_implement |
| HQ-3 (resolved — no answer needed) | Answered from the export, 2026-09-22. The five types without privacy roles — company, job, rates, time_tracking, current_contractors_info — are each marked deleted: true in source/tradeforce-50323.sanitized.bubble (user_types.*.deleted); Bubble drops a type's rules when the type is deleted. None of them becomes a target table (docs/DATA-MODEL.md § Dead and folded types), and all nine live types carry privacy roles, so there is no unprotected live type to design access for. ir/inventory.json does not carry the type-level deleted flag (only the field-level one), which is why this looked like an open question — filed as toolkit defect DEF-141. |
resolved (was blocks_implement) |