#Open questions (human clarifications)
Every question below is owned by the doc it was raised in — HQ-n ids are per document, so
HQ-1 in DOC-OVERVIEW and HQ-1 in DOC-MOD-AUTH are different questions. Always cite them
as <DOC-ID> HQ-n. Full text and chase notes live in docs/open-questions/<DOC-ID>.md.
#Open — needs a human answer
| Ref | Question (short) | Impact | Decision record |
|---|---|---|---|
| DOC-OVERVIEW HQ-1 | Is Stripe Connect / KYC / balances / payouts a separate programme from the core rebuild? | blocks_implement | MON-MARKETPLACE — same decision as DOC-ARCHITECTURE HQ-2 |
| DOC-OVERVIEW HQ-2 | Which auth provider and credential cutover replaces native Bubble auth? | blocks_implement | ACC-AUTH-SURFACE → docs/adr/ADR-002-acc-auth-surface.md |
| DOC-ARCHITECTURE HQ-1 | How do existing Bubble users authenticate on Supabase, and which signup activation path ships? | blocks_implement | ACC-AUTH-SURFACE → docs/adr/ADR-002-acc-auth-surface.md |
| DOC-ARCHITECTURE HQ-2 | Is Connect / KYC / payouts a separate programme after core cutover? | blocks_implement | MON-MARKETPLACE — same decision as DOC-OVERVIEW HQ-1 |
| DOC-ARCHITECTURE HQ-3 | Do the two ignore-privacy tracking API events become privileged endpoints, or get redesigned under ordinary RLS? | blocks_implement | ACC-IGNORE-PRIVACY |
| DOC-MOD-AUTH HQ-1 | Preserve Bubble signup activation (active=yes deep link) or replace it with Supabase confirm-email? |
blocks_implement | ACC-AUTH-SURFACE → docs/adr/ADR-002-acc-auth-surface.md |
| DOC-MOD-CONTRACTOR-SHIFTS HQ-1 | Welcome CTA “Go to My Profile Page”: profile panel (label + decompose) or Shift list (export wiring)? | blocks_implement | needs product sign-off |
| DOC-MOD-PAYMENTS HQ-1 | Does PostMark template user-invitation-3 already carry the payments destination, or must the call site send it? |
blocks_implement | needs PostMark template inspection |
Three of the eight are one decision: DOC-OVERVIEW HQ-2, DOC-ARCHITECTURE HQ-1 and DOC-MOD-AUTH HQ-1 are answered together by accepting the ACC-AUTH-SURFACE ADR. DOC-OVERVIEW HQ-1 and DOC-ARCHITECTURE HQ-2 are one programme-boundary decision (MON-MARKETPLACE). So five answers close all eight.
#Resolved — no answer needed
| Ref | Question (short) | How it was closed |
|---|---|---|
| DOC-OVERVIEW HQ-3 | What RLS applies to data types with no Bubble privacy roles? | All five rule-less types are deleted: true in the export and are not migrated; every live type carries roles. See docs/DATA-MODEL.md § Dead and folded types. Raised only because ir/inventory.json omits the type-level deleted flag — toolkit defect DEF-141. |
#Docs with no open questions
DOC-DATA-MODEL, DOC-MOD-SHELL, DOC-MOD-ONBOARDING, DOC-MOD-COMPANY-SHIFTS,
DOC-MOD-TIME-TRACKING, DOC-MOD-ADMIN, DOC-MOD-CHAT — each sidecar records what was chased
instead.
#Index (machine-checked)
| Ref | Notes |
|---|---|
| DOC-OVERVIEW | see docs/open-questions/ |
| DOC-ARCHITECTURE | see docs/open-questions/ |
| DOC-DATA-MODEL | see docs/open-questions/ |
| DOC-MOD-AUTH | see docs/open-questions/ |
| DOC-MOD-SHELL | see docs/open-questions/ |
| DOC-MOD-ONBOARDING | see docs/open-questions/ |
| DOC-MOD-COMPANY-SHIFTS | see docs/open-questions/ |
| DOC-MOD-CONTRACTOR-SHIFTS | see docs/open-questions/ |
| DOC-MOD-TIME-TRACKING | see docs/open-questions/ |
| DOC-MOD-PAYMENTS | see docs/open-questions/ |
| DOC-MOD-ADMIN | see docs/open-questions/ |
| DOC-MOD-CHAT | see docs/open-questions/ |
| HQ-1 | per-document id — see the tables above |
| HQ-2 | per-document id — see the tables above |
| HQ-3 | per-document id — see the tables above |