hamid
91 lines
12 KiB
HTML
91 lines
12 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="en">
|
||
<head>
|
||
<meta charset="utf-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||
<title>Open Questions & To-Do Backlog — Balinyaar docs</title>
|
||
<link rel="stylesheet" href="../assets/doc.css">
|
||
</head>
|
||
<body>
|
||
<div class="layout">
|
||
<aside class="sidebar">
|
||
<a class="brand" href="../index.html"><span class="dot"></span> Balinyaar docs</a>
|
||
<p class="tagline">Trust-first home-nursing marketplace · Iran</p>
|
||
<nav><div class="group"><div class="label">Start here</div><ul><li><a href="../index.html">Docs home</a></li><li><a href="../overview/platform-summary.html">Platform summary & ground truths</a></li></ul></div><div class="group"><div class="label">Business requirements</div><ul><li><a href="../business/index.html">Overview & MVP scope</a></li><li><a href="../business/01-actors-and-onboarding.html">1. Actors & onboarding</a></li><li><a href="../business/02-nurse-verification.html">2. Nurse verification</a></li><li><a href="../business/03-service-catalog-and-pricing.html">3. Service catalog & pricing</a></li><li><a href="../business/04-search-and-matching.html">4. Search & matching</a></li><li><a href="../business/05-booking-and-scheduling.html">5. Booking & scheduling</a></li><li><a href="../business/06-evv-and-service-delivery.html">6. EVV / service delivery</a></li><li><a href="../business/07-cancellation-and-refunds.html">7. Cancellation & refunds</a></li><li><a href="../business/08-payments-and-escrow.html">8. Payments & escrow</a></li><li><a href="../business/09-installments-bnpl.html">9. Installments / BNPL</a></li><li><a href="../business/10-payouts.html">10. Payouts to nurses</a></li><li><a href="../business/11-reviews-trust-and-safety.html">11. Reviews, trust & safety</a></li><li><a href="../business/12-messaging-and-emergencies.html">12. Messaging & emergencies</a></li><li><a href="../business/13-tax-invoicing-and-legal.html">13. Tax, invoicing & legal</a></li><li><a href="../business/14-notifications-and-admin.html">14. Notifications & admin</a></li></ul></div><div class="group"><div class="label">Database model</div><ul><li><a href="../data-model/index.html">Overview & decisions</a></li><li><a href="../data-model/diagrams.html">Diagrams</a></li><li><a href="../data-model/01-identity-and-access.html">1. Identity & access</a></li><li><a href="../data-model/02-geography.html">2. Geography</a></li><li><a href="../data-model/03-services-and-pricing.html">3. Services & pricing</a></li><li><a href="../data-model/04-verification-and-credentials.html">4. Verification & credentials</a></li><li><a href="../data-model/05-booking-and-scheduling.html">5. Booking & scheduling</a></li><li><a href="../data-model/06-payments-ledger-and-refunds.html">6. Payments, ledger & refunds</a></li><li><a href="../data-model/07-payouts.html">7. Payouts</a></li><li><a href="../data-model/08-bnpl.html">8. BNPL / installments</a></li><li><a href="../data-model/09-messaging.html">9. Messaging</a></li><li><a href="../data-model/10-reviews-and-records.html">10. Reviews & records</a></li><li><a href="../data-model/11-notifications.html">11. Notifications</a></li><li><a href="../data-model/12-audit-config-and-reference.html">12. Audit, config & reference</a></li><li><a href="../data-model/13-partner-centers-and-future.html">13. Partner centers & future</a></li></ul></div><div class="group"><div class="label">Payments deep-dive</div><ul><li><a href="../payments/index.html">Overview & exec summary</a></li><li><a href="../payments/iranian-payment-reality.html">Iranian payment reality</a></li><li><a href="../payments/escrow-ledger.html">Escrow as a ledger</a></li><li><a href="../payments/bnpl-landscape.html">BNPL landscape & finding</a></li><li><a href="../payments/cancellation-and-payout.html">Cancellation & nurse payout</a></li><li><a href="../payments/integration-notes.html">Integration & schema touchpoints</a></li><li><a href="../payments/sources.html">Recommendations & sources</a></li></ul></div><div class="group"><div class="label">Research & strategy</div><ul><li><a href="../research/index.html">Overview & exec summary</a></li><li><a href="../research/market-and-competitors.html">Market & competitors</a></li><li><a href="../research/problems-and-risks.html">Problems & risks</a></li><li><a href="../research/verification.html">Verification (research)</a></li><li><a href="../research/legal-landscape.html">Legal landscape</a></li><li><a href="../research/go-to-market.html">Go-to-market & sources</a></li></ul></div><div class="group"><div class="label">Notes & more</div><ul><li><a class="active" href="open-questions.html">Open questions</a></li><li><a href="future-ideas.html">Future ideas</a></li><li><a href="../wireframes/index.html">Wireframes</a></li><li><a href="../fa/index.html">Farsi documents</a></li></ul></div></nav>
|
||
</aside>
|
||
<main class="main"><div class="content">
|
||
<div class="topbar"><button class="theme-toggle" type="button" onclick="__t()">theme</button></div>
|
||
<h1 id="open-questions-to-do-backlog">Open Questions & To-Do Backlog</h1>
|
||
<p><a href="../index.html">← Product docs home</a></p>
|
||
<p>From <code>whatsInYourMind.txt</code> — things to build, research, or decide. Some are now resolved in the refined data model; marked below.</p>
|
||
<hr>
|
||
<h2 id="build-surface-backlog">Build / surface backlog <a class="anchor" href="#build-surface-backlog" aria-hidden="true">#</a></h2>
|
||
<ul>
|
||
<li><strong>Ticket page</strong> — the admin-readable messaging surface; modeled in</li>
|
||
</ul>
|
||
<p> <a href="../data-model/09-messaging.html">Messaging (ticket system)</a> and required by <a href="../business/12-messaging-and-emergencies.html">Messaging & On-Site Emergencies</a>.</p>
|
||
<ul>
|
||
<li><strong>Backoffice / admin</strong> — see <a href="../business/14-notifications-and-admin.html">Notifications & Admin / Backoffice</a>.</li>
|
||
<li><strong>Verify the registration code</strong> — OTP confirmation step in onboarding.</li>
|
||
<li><strong>Rate limiting</strong> — abuse protection on auth/OTP and API.</li>
|
||
<li><strong>Workbox for cache</strong> (maybe) — PWA/offline caching, client-side.</li>
|
||
</ul>
|
||
<h2 id="needs-research">Needs research <a class="anchor" href="#needs-research" aria-hidden="true">#</a></h2>
|
||
<ul>
|
||
<li><strong>Terms of Service page</strong> — <em>(needs research)</em>.</li>
|
||
<li><strong>Privacy & Policy page</strong> — <em>(needs research)</em>.</li>
|
||
</ul>
|
||
<hr>
|
||
<h2 id="resolved-questions-kept-for-the-record">Resolved questions (kept for the record) <a class="anchor" href="#resolved-questions-kept-for-the-record" aria-hidden="true">#</a></h2>
|
||
<p>These were the two hardest open questions; both are now <strong>answered</strong> against verified payment research and built into the model.</p>
|
||
<ul>
|
||
<li><del>اگر پرداخت قسطی داشته باشیم و طرف اون وسط بخواد کنسل کنه چی میشه؟</del></li>
|
||
</ul>
|
||
<p> <strong>(BNPL booking cancelled mid-plan — what happens?)</strong> → Resolved. Money always flows <code>customer ↔ provider ↔ Balinyaar</code>; Balinyaar calls the provider's revert/cancel/update API and the provider unwinds the customer's installments. See <a href="../payments/cancellation-and-payout.html">Q1 — cancellation/refund</a> and <a href="../data-model/index.html">the two questions</a>.</p>
|
||
<ul>
|
||
<li><del>BNPL اگر باشه خب پول پرستار رو کی میده؟</del></li>
|
||
</ul>
|
||
<p> <strong>(Under BNPL, who pays the nurse?)</strong> → Resolved. <strong>Balinyaar</strong> pays the nurse, on its own weekly schedule, from <code>gross − balinyaar_commission</code> — identical to a card booking; the BNPL commission is a platform expense, never the nurse's. See <a href="../payments/cancellation-and-payout.html">Q2 — who pays the nurse & when</a>.</p>
|
||
<hr>
|
||
<p>See also the launch-blocking items to confirm with counsel / providers: <a href="../research/go-to-market.html">research open questions</a> and <a href="../data-model/index.html">data-model open items</a>.</p>
|
||
<hr>
|
||
<h2 id="decided-public-guest-browse-depth-ui-phase-13-2026-07-19">Decided — public guest-browse depth (ui-phase-13, 2026-07-19) <a class="anchor" href="#decided-public-guest-browse-depth-ui-phase-13-2026-07-19" aria-hidden="true">#</a></h2>
|
||
<p><strong>Question:</strong> how deep should the anonymous (logged-out) web experience go, now that the entire public surface is a bare <code>/login</code>?</p>
|
||
<p>Three tiers were framed:</p>
|
||
<ul>
|
||
<li><strong>(a) Landing only</strong> — a marketing page at <code>/</code>; zero data, zero new endpoints.</li>
|
||
<li><strong>(b) Landing + static public pages</strong> — (a) plus category/how-it-works/trust content; still zero</li>
|
||
</ul>
|
||
<p> data (a static i18n category grid, not the live catalog).</p>
|
||
<ul>
|
||
<li><strong>(c) Guest search + public nurse profiles</strong> — read-only anonymous variants of the search-results</li>
|
||
</ul>
|
||
<p> and nurse-profile screens. Requires <strong>public read endpoints that don't exist today</strong> (search and profile reads sit behind the auth middleware + cookie-bearing <code>clientFetch</code>) plus a privacy review of which nurse fields may be shown logged-out (never phone, exact address, or document data).</p>
|
||
<p><strong>Decision: ship (a)+(b) now; tier (c) is deferred as a REQ-gated follow-up</strong>, not built against placeholder endpoints. Rationale:</p>
|
||
<ul>
|
||
<li>(a)+(b) already close the biggest gap — a family can see the brand, the trust story (identity/</li>
|
||
</ul>
|
||
<p> license/INO/bank verification), the escrow guarantee, and the service categories before creating an account, all with <strong>zero new backend surface</strong>.</p>
|
||
<ul>
|
||
<li>(c) is a materially bigger commitment: a new anonymous, rate-limited search read and a</li>
|
||
</ul>
|
||
<p> privacy-reviewed public nurse-profile shape are backend work with real abuse/PII exposure considerations (scraping, competitor intel, nurse safety) — the kind of decision that shouldn't be made by inferring it from a frontend phase.</p>
|
||
<ul>
|
||
<li>What (c) would need, if approved later: an anonymous <code>nurse_search</code> read (verified-only invariant</li>
|
||
</ul>
|
||
<p> preserved, rate-limited, no customer-context fields) and a privacy-reviewed public nurse-profile read (display name, photo, verified-badge state, rating aggregate, service/price rows only — never phone, exact coverage area, or document data). Filed as REQ-066/REQ-067 in <a href="../../archive/build-chain/working-context/frontend/requests/for-backend.html">for-backend.md</a>; guest-search routes and the guest→login handoff at the booking CTA stay unbuilt until those land.</p>
|
||
<p>Implemented as: a public landing rewritten in at <code>/</code> (middleware rewrite, not a redirect, so the URL/ canonical stays <code>/</code>) with hero, static category grid, how-it-works, a trust/verification explainer, a nurse-recruitment CTA, and a footer — see <a href="../../archive/build-chain/working-context/reports/ui-phase-13-report.html">ui-phase-13-report.md</a> for the full build record.</p>
|
||
<a class="back-to-top" href="#">↑ Back to top</a>
|
||
</div></main>
|
||
</div>
|
||
<script>
|
||
(function(){var k='balinyaar-docs-theme';var s=localStorage.getItem(k);
|
||
if(s)document.documentElement.setAttribute('data-theme',s);
|
||
else if(matchMedia('(prefers-color-scheme: dark)').matches)document.documentElement.setAttribute('data-theme','dark');})();
|
||
function __t(){var d=document.documentElement;var n=d.getAttribute('data-theme')==='dark'?'light':'dark';
|
||
d.setAttribute('data-theme',n);localStorage.setItem('balinyaar-docs-theme',n);}
|
||
</script>
|
||
|
||
</body>
|
||
</html>
|