Launch a safe, market-aware Nova Scotia MVP across Lavida's five product lines on
October 1, 2026. Every reviewed feature must have an MVP-thin usable flow or an
explicitly disabled provider action. The launch does not require full automation,
visual polish, or every future-market provider.
The September invite-only pilot is a real production release with a restricted
cohort. It is not another development environment.
The five launch product lines are Marketing, Screening, Leasing, Payments,
and Marketplace.
Internal/manual screening is available. External screening initiation is
disabled and shown as Coming soon.
Internal Rent Guarantee eligibility and workflow preparation are available.
External provider initiation is disabled and shown as Coming soon.
Listing syndication supports package preparation and assisted/manual
publishing. Automated provider publishing is disabled and shown as Coming soon until a market route is certified.
Payments may run live only after the Canadian payment route, credentials,
webhooks, refunds, disputes, payouts, and reconciliation are certified.
Provider availability is decided server-side from the global integration
gate and the market-aware provider table. Clients never choose their market
or provider.
No launch-critical redesign, broad refactor, or speculative provider work is
accepted after August 23.
Marketplace launches with three service lines: Showing Connect, Maintenance
Connect, and Inspection Connect.
Golden paths:
Showing request → booking/assignment → execution → confirmation and payout.
Maintenance request → work order and quote → approval/funding → completion →
approval and payout.
Move-in, move-out, or general inspection request → scheduling/assignment →
guided inspection and evidence → participant sign-off → final report and any
follow-up work.
Required MVP outcomes:
Showing Connect booking, execution, confirmation, cancellation, and dispute.
Maintenance request, work order, quote, approval, completion, and dispute.
Inspection Connect for move-in, move-out, and general property inspections.
Inspection templates, room/area checklists, condition ratings, notes,
timestamps, photos/documents, participant sign-off, and immutable final report.
Inspection scheduling and assignment to an eligible owner/property manager,
associate, contractor, or other authorized inspector.
Inspection findings connected to the property, unit, tenancy, and any resulting
maintenance work order without duplicating the inspection evidence.
MVP contractor connection and associate task assignment.
Eligibility, fee, allocation, completion, and release calculations owned by
the server.
Manual operations path for exceptions; no unmonitored silent failure.
Leasing owns the tenancy lifecycle and the requirement for a move-in or move-out
inspection. Marketplace owns Inspection Connect scheduling, fulfilment, evidence,
reporting, disputes, and any paid inspector settlement.
*_EXTERNAL_INTEGRATION_ENABLED=false disables external initiation in every
environment. The UI renders the control disabled with Coming soon, and the
server rejects direct initiation attempts without calling a provider.
*_EXTERNAL_INTEGRATION_ENABLED=true permits initiation only if an active
market/use-case route and configured adapter also exist.
*_PROVIDER_MODE=sandbox|live selects the credential and endpoint family; it
does not select the provider.
Provider mode is ignored while the corresponding integration is disabled.
There is no silent fallback from live to sandbox.
Internal records and workflows remain available while an external integration
is disabled, but must never claim external completion.
If payment does not receive a GO, production remains false/sandbox; payment
controls are disabled and the launch cannot advertise live payment collection.
global integration gate enabled
AND exact market/use-case provider route active
AND provider adapter configured
AND credentials valid for the configured mode
Provider routing requirements:
Derive market from trusted account, property, or transaction context.
Prefer an exact market route. Use an ALL fallback only for a genuinely
market-neutral service.
Do not use ALL for regulated payments, screening, insurance, or other
jurisdiction-dependent products.
Store provider key, category, use case, market, active state, priority, and
non-secret metadata in PlatformProviderRoute.
Store credentials and webhook secrets outside the database.
Add LISTING_SYNDICATION to the provider categories before implementing an
automated publisher.
Replace the general Stripe PAYMENT/CHECKOUT/ALL route with explicit CA
routes for every enabled Canadian payment use case.
Minimum Canadian payment use cases:
Category
Use case
Launch market
Required state
PAYMENT
SUBSCRIPTION
CA
Active and certified
PAYMENT
CREDIT_PURCHASE
CA
Active and certified
PAYMENT
RENT_COLLECTION
CA
Active only if approved
PAYMENT
MARKETPLACE_PAYMENT
CA
Active only if approved
PAYMENT
RECIPIENT_PAYOUT
CA
Active only if approved
Syndication routes remain inactive for October 1 unless a provider completes
sandbox, legal, operational, and production certification before code freeze.
Activation is not required for MVP because assisted/manual syndication remains
available.
No engine is PRODUCTION READY merely because its code builds. Status changes
require evidence in the production-readiness checklist.
Engine
Launch responsibility
October 1 readiness requirement
LAE
Identity, accounts, roles, onboarding, market
Production ready
LRE
Properties, listings, applications, references
Production ready
LSE
Consent and internal/manual screening
Production ready for internal flow; external route disabled
LLE
Lease lifecycle and evidence
Production ready; external Rent Guarantee disabled
LPE
Billing, collection, refunds, transfers, payouts
Production ready for every enabled payment use case
LFE
Journals, reporting, reconciliation
Production ready with balanced evidence
LIE
Credits, Points, referrals, promotions
Production ready for enabled campaigns; uncertified fulfilment disabled
LME
Showing Connect, Maintenance Connect, and Inspection Connect
Production ready for all three MVP workflows and manual exceptions
LCE
Messaging and notifications
Production ready with tested degraded behavior
LDE
Private documents, retention, signed access
Production ready
LBE
Provider and partner boundaries
Production ready for enabled routes; unused routes disabled
Atlas
Policy-controlled AI assistance
Conditionally ready with deterministic fallback; never blocks a core transaction
Every engine must supply test evidence, security/access evidence, operational
evidence, and owner approval by September 27. Formal status remains NOT REVIEWED until that evidence is attached to the readiness checklist.
Complete the internal/manual screening golden path.
Test external screening through the sandbox handshake boundary, then restore
the disabled default.
Complete move-in, move-out, renewal, and termination MVP flows, including the
handoff from Leasing to Marketplace Inspection Connect.
Verify Nova Scotia lease templates, signature evidence, delivery, and private
storage.
Complete internal Rent Guarantee eligibility and setup flow.
Test the Rent Guarantee sandbox handshake boundary, then restore the disabled
default.
Exit gate: an approved applicant can become an active tenant without either
external provider; disabled actions make no provider calls or false claims.
¶ August 17–23 — payments and marketplace feature complete
Complete payment disputes, reconciliation, receipts, and retry/recovery paths.
Verify subscription, credit, rent, marketplace funding, refund, transfer,
payout, and reversal scenarios that will be enabled at launch.
Complete contractor connection and associate task assignment at MVP depth.
Complete Showing Connect, Maintenance Connect, and Inspection Connect end to
end.
Verify move-in, move-out, and general inspection templates, scheduling,
assignment, evidence, sign-off, final reports, disputes, and resulting work
orders.
Constrain AI automation to human-reviewed assistance with deterministic
fallback.
Close feature work on August 23. Anything incomplete is reduced to a safe MVP
path or disabled behind a documented gate.
Exit gate: all five golden paths pass in development; no unresolved data-loss,
authorization, money, lease-integrity, or provider-gate defect remains.
Record scenario, persona, account, market, browser/device, expected outcome,
actual outcome, evidence, severity, and retest result for every finding.
Fix severity-1 immediately and severity-2 before the release candidate.
Exit gate: 100% of launch-critical scenarios attempted, no open severity-1,
and every severity-2 has an owner and completion date no later than September 4.
Invite a small first wave from the tested cohort, then expand deliberately.
Use real production identities and data only with explicit participant consent.
Run production smoke tests immediately after deployment.
Review errors, queues, webhook failures, notifications, payment reconciliation,
access-denied events, and support requests at least twice daily.
Do not enable external screening, Rent Guarantee, or automated syndication.
Stop the affected flow immediately for data exposure, incorrect financial
posting, unreconciled collection, invalid lease evidence, or account leakage.
Exit gate: five consecutive stable days, all five golden paths completed by
invited users, zero account-isolation incidents, and zero unexplained financial
differences.
Re-run every product-line golden path on the frozen release.
Run the cross-engine scenarios from the readiness checklist.
Complete payment webhook, refund, dispute, payout, and reconciliation evidence.
Perform final backup/restore and rollback rehearsal.
Test alerts and the incident communication chain.
Assign an allowed readiness status to every engine with linked evidence.
Exit gate: every launch-critical engine is PRODUCTION READY or has a named,
accepted conditional dependency that is disabled and cannot affect a core flow.
Open registration or invitations for the approved Nova Scotia audience.
Execute post-deployment smoke tests before announcing availability.
Monitor authentication, five golden paths, queues, notifications, provider
health, payment exceptions, reconciliation, and support continuously during
the initial launch window.
Keep external screening, Rent Guarantee, and syndication provider actions
disabled and labelled Coming soon.
Publish only capabilities that a real user can complete safely.
Quote, work or inspection assignment, completion evidence, payout readiness
Staff/operations
2
Provider routes, manual exceptions, reconciliation, audit, support
Testers must not share accounts. Each tester should use a dedicated identity and
record evidence without copying sensitive personal information into the defect
tracker.
The first post-launch backlog includes external screening certification, Rent
Guarantee provider certification, automated market-aware syndication, additional
Canadian provinces, Nigerian market activation, deeper automation, and deferred
polish. None may bypass the same environment gate, provider-route, evidence, and
go/no-go model used for this launch.