Launch Scope¶
Last audited: 2026-07-05.
Status: controlled founding pilot scope. This is not approval for a broad public
paid launch. Public launch is allowed only after the release gates in the
pre-release charter pass and the pilot memo says
go.
Primary sources:
- Pre-release charter
- Pre-release delivery epics
- Production launch readiness audit
- Mobile flow docs
- Deployment guide
- Production release signoff
Product goal¶
What the app must do for first real users.
MamNajem must let a self-managing Polish landlord with 2-10 long-term residential rental units run live lease operations from a phone without needing tenant adoption before the owner gets value.
For the first real users, the app must support this complete launch promise:
- Owner signs up, signs in, accepts legal terms, completes onboarding, and enters bank-transfer details.
- Owner creates a property, active lease, rent schedule, tenant record, tenant invitation, documents, and operational reminders.
- Tenant accepts an invitation, sees only assigned lease/property context, reads documents, uploads rent proof, responds to handover/final settlement tasks, and can message the owner.
- Rent management defaults to off-ledger bank transfer, payment proof, owner mark-paid, receipts, reminders, overdue visibility, and audit trail. Stripe Connect rent checkout must remain hidden or explicitly feature-flagged unless a later embedded rent-collection pilot is approved.
- Owner and tenant can create, review, confirm, decline, and preserve evidence for handover protocols, final settlement, deposit/refund records, documents, messages, calendar items, and audit logs.
- Owner can start a 30-day no-card trial, understand plan caps, subscribe through billing, change/cancel through supported billing surfaces, and fall back to read-only Archive when required.
- Users can export data, request account deletion when no active/pending lease blocks it, read current terms/privacy policy, and submit simple in-app problem reports.
- Admin/support can operate the paid pilot without database access: allowlist users, review pilot intake, inspect activation, triage problem reports, inspect processed webhooks, and replay dead Stripe webhooks.
The first release audience is landlords. Tenants are workflow participants, not buyers. Property managers, agencies, PRS operators, short-term rental operators, accounting-heavy portfolio teams, and custom large-customer builds are outside the launch scope.
Must-have before launch¶
Auth works¶
- Cognito user pools, hosted auth, redirect/logout URLs, mobile client IDs, web client IDs, JWT issuer/client validation, and admin Cognito settings are correct for integration and production.
- Sign-up, sign-in, logout, password recovery, hosted-auth callback, legal acceptance, role gate, onboarding gate, and invitation acceptance are tested on the deployed integration app.
- Owner and tenant route guards are verified: tenant deep links do not expose owner billing, payout, bank-account, property-mutation, or admin surfaces.
- External OAuth/email-code paths are either verified with real provider/inbox state or hidden from the launch path.
Main user flows work¶
- Owner flow works end to end on deployed integration: account setup, onboarding, bank account, property, lease, tenant, invitation, documents, rent schedule, payment request, mark-paid/proof, handover, move-out, final settlement, problem report, data export, and deletion blocked by active/pending leases.
- Tenant flow works end to end on deployed integration: invitation acceptance, assigned lease/property visibility, document access, proof upload, deferral request, messaging, handover confirmation/decline, final settlement response, support report, legal screens, and profile/preferences.
- Error states are exercised for empty accounts, invalid invitations, expired sessions, forbidden cross-user access, upload failure, offline/poor network, validation errors, disabled actions, and stale route params.
- Real-device or emulator verification exists for the launch workflows. Maestro Android coverage should reproduce any mobile breakage before code changes and should pass against the fixed behavior.
Payments/billing tested¶
- Stripe web subscription flow works for trial, plan listing, checkout, portal, plan change, cancellation, grace/Archive behavior, cap warnings, and cap blocks.
- Stripe webhook delivery is verified against
/v1/webhooks/stripewith the live event set in payment webhooks: subscription checkout, invoice paid/failed, subscription updates/deletes, Connect account updates, rent-payment checkout/payment-intent states, refunds, disputes, duplicate events, retryable events, and dead webhook replay. - Stripe Dashboard configuration is checked for endpoint URL, signing secret, selected events, Connect events, live/test separation, retry behavior, portal terms/privacy URLs, and price IDs.
- Off-ledger rent transfer/proof is the default tenant rent-payment UX.
Embedded rent checkout is not part of the ordinary launch path unless
EXPO_PUBLIC_RENT_STRIPE_CHECKOUT_ENABLED=trueis deliberately approved for a separate pilot. - If Google Play/native store subscriptions are enabled for the production Android release, purchase and restore are tested on a Play-capable tester device. These flows are not proven by the default CI path alone.
Backend deployed¶
- Latest
origin/integrationis reviewed, all release-affecting repos are clean or intentionally changed, and the integration pipeline is green at the release SHA. - Backend
mvn -B verify, security scans, OpenAPI compatibility checks, and deploy verification pass for the release SHA. - Integration deploy health is verified through
/actuator/health, logs, and the deployed app. Production rollout remains manual and must fast-forward from the verified integration commit only. - Production has no commits absent from integration before rollout:
git rev-list --count origin/integration..origin/productionis0, andorigin/productionis an ancestor oforigin/integration. - Production/integration runtime secrets and config are confirmed: Cognito, Stripe keys/webhook secrets/price IDs, S3, KMS, Firebase/FCM, New Relic, CloudWatch, SES, app URLs, and CORS/domain settings.
Mobile app production build works¶
- Mobile
pnpm check, Jest, CI helper tests, release config assertions, and relevant Playwright/Maestro suites pass. - Android release pipeline builds a signed
.aab, uploads it to Google Play internal, promotes the same artifact to closed alpha, and leaves production as a manual promotion. - Android production build uses production API/app URLs, release identity, Firebase config, New Relic release/dist, update policy, and the intended native billing flag.
- Native release dispatch alone is not enough evidence: Android Maestro and any required real-device checks must be run or explicitly recorded as blocked.
- iOS/TestFlight is not a Google Play launch blocker unless iOS is included in the same release promise. If included, iOS build and native E2E checks must be treated with the same standard.
.env.example, CI variable docs, and release docs match runtime config, including mobile Cognito client IDs and billing flags.
Data is backed up¶
- Production RDS recovery posture is accepted and current: 7-day automated
backups/PITR, Multi-AZ, final snapshot on deletion, deletion protection, and
Terraform
prevent_destroy. - Restore procedure is known before launch: restore to a new DB instance first, never overwrite the existing production instance during triage.
- A restore check or equivalent recovery evidence is recorded for the launch release window.
- Integration database backup job and
BackupSuccessvisibility are checked before relying on integration as evidence. - Data retention policy remains honest: automated expired-record cleanup is not active before paid release and must not be promised in product copy.
Basic monitoring exists¶
- New Relic is configured for backend, mobile, and web-admin with release, environment, privacy scrubbers, and error boundaries where applicable.
- CloudWatch alarms and dashboards cover backend health, deploy failures, ECS/ALB health, API 5xx, RDS CPU/storage/memory/connections/latency, Stripe webhook retry/dead states, and backup/deploy success signals.
- Alert delivery path is verified: CloudWatch alarm to SNS to Discord/alarm bridge, plus New Relic issue visibility for new/regressed release errors.
- The release signoff includes a 30-minute deploy watch for health, 5xx, unhealthy targets, New Relic issues, Stripe webhook dead/retryable states, and user/admin problem reports.
Privacy policy / terms ready¶
- Terms and privacy policy render in app and web routes used by Stripe portal, auth, account settings, and unauthenticated visitors.
- Data export, account deletion, active/pending lease deletion block, IBAN masking/encryption posture, retention policy, provider disclosures, and support-report handling match the written policy.
- Polish counsel review is complete. The legal review response log must contain counsel answers, Product Owner decisions, required docs/code changes, merged follow-up commits, and a passed charter gate.
- Launch copy must avoid legal advice, legal guarantees, fully digital occasional lease claims, official proof-of-delivery claims, statutory notice automation, eviction/enforcement claims, escrow/held-rent claims, and broad GDPR compliance overclaims unless counsel explicitly approves narrower wording.
Google Play production release ready¶
- Play Console app exists for
pl.mamnajem; internal and closed alpha tracks exist; production promotion is manual and available only after alpha succeeds. - GitLab CI/CD variables are configured: keystore, passwords, release build number fallback, Google Workload Identity Federation, package name, production app/API URLs, Cognito IDs, Firebase config, New Relic release/dist, and billing flags.
- Store listing, screenshots, privacy/data-safety form, account deletion link, support contact, terms/privacy links, and app access instructions match the launch scope.
- Production
.aabinstalls and opens on a real Android device or emulator, authenticates against production-intended config, and passes the required owner/tenant smoke checks before manual production promotion. - If native store billing is enabled, Google Play product IDs, backend verification credentials, store notification delivery, purchase, restore, cancellation/grace behavior, and support recovery are verified with a tester account.
Not required before launch¶
- Nice-to-have redesigns, visual polish, alternate landing layouts, theme changes, or broad brand work that does not affect the founding pilot promise.
- Advanced settings for agencies, teams, accountants, property managers, permissions, delegated workflows, or multi-operator portfolios.
- Extra dashboards beyond launch support needs: allowlist, pilot intake, activation overview, problem reports, processed webhooks, Stripe webhooks, and basic operational health.
- Non-critical refactors in backend, mobile, web-admin, infrastructure, navigation, styling, or test helpers when behavior is already covered and the launch path works.
- Broad public launch, large SEO/content program, paid ads, referral programs, annual plans, add-ons, case studies, and agency sales motion before the founding pilot proves activation and willingness to pay.
- Property-manager suite, marketplace/listing syndication, tenant screening, accounting/KSeF, direct legal advice, legal notice automation, eviction automation, statutory arrears workflows, debt collection, and custom builds.
- Lease-linked repair management, contractor assignment, responsibility resolution, and vendor maintenance suite. Launch scope is simple in-app problem reporting only.
- Embedded BLIK/P24/PayU/Tpay rent collection, rent take-rate, tenant fees, escrow/held-rent claims, and app-store-first commercial strategy.
- Full automated retention cleanup before paid pilot, as long as policy, support procedures, and product copy do not promise it.
Definition of done¶
A task is done only if all applicable evidence exists:
- Code is merged to the correct long-lived branch. Backend, architecture, docs,
and web-admin changes land on
integration; production is user-controlled and can only fast-forward from verified integration. - Tests pass for the changed surface: backend
mvn -B verify; mobilepnpm check, Jest, CI helper tests, and relevant Playwright/Maestro suites; web-admin tests/build; architecture build/tests/Terraform validation when infrastructure changes. - No TypeScript, Kotlin, Swift, lint, formatting, OpenAPI compatibility, security-scan, or release-config errors remain in the affected repo.
- Feature works on real device, emulator, or deployed browser against the real integration backend. Native app behavior needs Android/iOS device or emulator evidence; web/admin behavior needs deployed integration browser verification.
- Error states are handled and tested or smoke-checked: validation failure, auth expiry, 401/403, empty state, network failure, upload failure, payment cancel/failure, webhook retry/dead state, disabled action, and missing context.
- Docs, config, environment variables, CI variables, legal copy, runbooks, store-release docs, and support procedures are updated in the same change when behavior or operations changed.
- The integration pipeline is monitored to a terminal state after push. If it fails, the failing job is identified and classified as application, test, contract, security, deploy, infrastructure, or external-service failure.
- After successful integration CI/CD, the deployed integration environment is verified with the workflow affected by the change. Completion reports must say what was checked and any blocker that prevented browser/device verification.
- Launch-gate work is not done until evidence is linked from the relevant charter, pre-release, operation, runbook, or release-signoff document.