Open Questions / Known Gaps Canonical list of unresolved items and assumptions

## Open · P0 (block diagram drafting) ### Q02 — Complete tool inventory - **Stream:** All - **Best answered by:** Owner / Edmar - **Status:** open - **Where the answer goes:** `reference/tools-systems/index.md` and per-system files in `reference/tools-systems/` ### Q03 — Complete channel inventory - **Stream:** All - **Best answered by:** Owner - **Status:** open - **Where the answer goes:** `reference/tools-systems/whatsapp.md` (channels section), eventually a channels.md file ### Q04 — Who else touches workflows? - **Stream:** All - **Best answered by:** Owner - **Status:** open - **Where the answer goes:** `reference/people/roster.md` and `reference/people/detailed/` ### Q05 — Which stream first, and who is the diagram for? - **Stream:** N/A - **Best answered by:** Owner - **Status:** open ### Q12 — Jenn's classification criteria - **Stream:** All (Stage 03) - **Best answered by:** Jenn - **Status:** partially answered (2026-05-04 — Ritchie interview) - **Partial answer:** Routing into Admin Junkie is known: (1) Andrew/Shlomo/Brian reimbursements → Admin Junkie directly. (2) Jenn reviews Andrew's "Docs to File" items — checks completeness (property present? amount present?) → forwards to Admin Junkie. (3) Hector/JJ bulk reimbursement receipts → go to their respective property group chats, NOT Admin Junkie. Admin Junkie members: Mark, Edmar, Ritchie (Jenn intentionally excluded). Full classification decision logic still open. - **Where the answer goes:** `streams/03-records.md`, `streams/01-money-out-triggers.md` ### Q13 — What Jenn adds during classification - **Stream:** All (Stage 03) - **Best answered by:** Jenn - **Status:** partially answered (2026-05-04 — Ritchie interview) - **Partial answer:** For Andrew's "Docs to File" items, Jenn checks for completeness (property + amount present) before forwarding to Admin Junkie. This is the minimum classification check Jenn performs. Full tagging mechanics still open. ### Q15 — Approver role and threshold logic - **Stream:** 01 - **Best answered by:** Owner - **Status:** ⚠️ CORRECTED 2026-05-04 — prior answer was superseded - **Prior answer (2026-04-27):** Two-track system (Track A / Track B). Incorrect going forward. - **Corrected answer (2026-05-04):** Single approval track. Shlomo changed policy — all vendor invoices, labor bills, AND reimbursements (including Shlomo's own and Andrew's own) now go through Andrew's review. No bypass lane. No dollar threshold — Andrew's gate confirms invoices are within pre-approved project scope. - **Applied to:** `tools-systems/vpt.md` (Approval Chain), `streams/01-money-out-triggers.md`, `pipeline.md` Stage 04, `glossary.md` (Track A/B, In-house bypass approval)