Skip to content

Pre-Release Delivery Epics And Tasks

Date: 2026-05-30

Source audit: Pre-Release Strategy And Scope Audit

Purpose: This is the execution backlog for the first paid MamNajem pilot and release. It is not a Jira export. Keep this file strict: every item needs a clear role, goal, requirements, and done condition.

Release decision: Narrow. Do not run a broad public paid release until the P0 gates are complete and the founding pilot proves real landlord usage and willingness to pay.

First ICP: Self-managing Polish landlords with 2-5 long-term residential units in Warsaw, Krakow, Wroclaw, Trojmiasto, and Poznan. Expand to 6-10 unit self-managers only if activation and willingness to pay hold.

First paid promise: MamNajem keeps every active lease organized: property and lease setup, tenant invite, document vault, rent schedule, payment proof, handover protocol, messages, reminders, and final settlement evidence.

Roles

Role Responsibility
Product Owner Scope, product decisions, legal review coordination, GTM requirements, pilot operations, support requirements, release gates, acceptance.
Designer UX flow, UI copy placement, landing structure, interaction design.
Frontend Developer Mobile app, landing page, web-admin UI, frontend analytics events, frontend tests.
Backend Developer Backend APIs, data models, services, integrations, backend analytics events, backend tests.
Infra Developer Production readiness, infrastructure, backups, auth configuration, alarms, release hygiene.

Priority

Priority Meaning
P0 Required before first paid public release.
P1 Required if included in public promise, otherwise can follow pilot signal.
P2 Useful after validation; do not block release.

Epic Order

Order Epic Priority
0 Release Charter And Scope Freeze P0
1 ICP Positioning, Landing, Pricing, Founder Pilot P0
2 Owner-First Activation And Analytics P0
3 Legal Workflow And Artifact Gate P0
4 Handover, Deposit, Final Settlement P0
5 Off-Ledger Rent Tracking P0
6 Email And Reminder Delivery P0
7 Admin And Support Readiness P0
8 Privacy, Retention, Security, Production Readiness P0
9 Maintenance-Lite P1, P0 if promised publicly
10 Pilot Operations And Validation Gate P0

Epic 0: Release Charter And Scope Freeze

Goal: Lock the first release scope before more implementation starts.

Primary role: Product Owner

Do not include: broad roadmap, investor narrative, feature wish list, post-launch ideas.

Tasks

  • [x] EP0-T1: Create docs/roadmap/pre-release-charter.md
  • Role: Product Owner
  • Goal: Create the release decision document.
  • Requirements:
    • Define first ICP.
    • Define first paid promise.
    • Define in-scope workflows.
    • Define out-of-scope workflows.
    • Define release gates.
    • Define owner-only activation.
    • Link to pre-release-strategy-scope-audit.md.
  • Done when:

    • The charter can be used to accept or reject every task in this backlog.
  • [x] EP0-T2: Write explicit non-goals

  • Role: Product Owner
  • Goal: Prevent scope drift.
  • Requirements:
    • Mark property-manager suite as out of scope.
    • Mark legal notice automation as out of scope.
    • Mark app-store-first billing as out of scope.
    • Mark rent take-rate as out of scope.
    • Mark tenant screening as out of scope.
    • Mark marketplace/listing syndication as out of scope.
  • Done when:

    • The charter has a non-goals section with each item above.
  • [x] EP0-T3: Create release gate table

  • Role: Product Owner
  • Supporting role: Infra Developer
  • Goal: Define what must be true before launch.
  • Requirements:
    • Gate for legal review.
    • Gate for privacy/retention alignment.
    • Gate for email delivery.
    • Gate for admin support.
    • Gate for billing/pricing.
    • Gate for production backups and alerts.
    • Gate for pilot validation.
    • Each gate has owner, evidence required, and status.
  • Done when:

    • A release reviewer can mark each gate pass/fail without interpretation.
  • [x] EP0-T4: Approve first-release scope

  • Role: Product Owner
  • Goal: Make a written go/no-go decision on scope.
  • Requirements:
    • Confirm the first release is a founding pilot, not a broad launch.
    • Confirm the first buyer is landlord, not tenant.
    • Confirm the first product promise.
    • Confirm the first pricing test.
  • Done when:
    • The charter has an approval note with date and approver.

Epic 1: ICP Positioning, Landing, Pricing, Founder Pilot

Goal: Make the public product speak to the first paying buyer and collect qualified pilot demand.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: brand redesign, broad SEO program, property-manager messaging, tenant acquisition campaign.

Evidence: LandingPage.tsx (mobile-frontend/components/landing/LandingPage.tsx), pl/common.json, poland-launch-validation-pack.md

Tasks

  • [x] EP1-T1: Write landing-page copy brief
  • Role: Product Owner
  • Supporting role: Designer
  • Goal: Define exact public message for the first ICP.
  • Requirements:
    • Hero targets self-managing Polish landlords with 2-10 units.
    • Tenant is described as workflow participant, not buyer.
    • Property managers are not a primary audience.
    • Copy includes lease operations, rent visibility, handover, deposit settlement, reminders, and evidence.
    • Copy uses Polish rental terms: najem okazjonalny, protokol zdawczo-odbiorczy, kaucja, rozliczenie, czynsz.
  • Done when:

    • Designer and Frontend Developer can update landing UI without asking what message to use.
  • [x] EP1-T2: Redesign landing-page structure

  • Role: Designer
  • Supporting role: Product Owner
  • Goal: Define page sections and CTA placement.
  • Requirements:
    • Hero section has one primary CTA for founding pilot or portfolio review.
    • Page includes proof blocks for documents, rent tracking, handover, deposit settlement.
    • Page includes who-this-is-for section.
    • Page includes who-this-is-not-for section.
    • Page includes legal-boundary language without promising legal advice.
  • Done when:

    • Landing structure is ready for implementation in mobile-frontend.
  • [x] EP1-T3: Implement landing-page copy and structure

  • Role: Frontend Developer
  • Supporting role: Designer
  • Goal: Replace broad public positioning with ICP-focused positioning.
  • Requirements:
    • Update landing translations in mobile-frontend/language/pl/common.json.
    • Update landing component if required in mobile-frontend/components/landing/LandingPage.tsx.
    • Remove primary positioning for property managers.
    • Keep tenant language only where it supports landlord workflow.
    • Keep existing sign-in/get-started paths working.
  • Done when:

    • Local landing page shows the new landlord-first message in Polish.
  • [x] EP1-T4: Create pricing page with trial + caps + paywall

  • Role: Product Owner
  • Supporting roles: Designer, Frontend Developer, Backend Developer
  • Goal: Show testable public pricing aligned with the trial-not-freemium model.
  • Requirements:
    • 30-day no-card trial as the only public acquisition CTA, with full Portfolio features during the trial.
    • Solo: 19.99 PLN gross/month — hard cap 3 active properties / 10 active tenants.
    • Portfolio: 49.99 PLN gross/month — hard cap 10 / 35.
    • Plus: 99.99 PLN gross/month — hard cap 25 / 100.
    • Archived properties / leases / tenants do NOT count toward caps.
    • Soft-warn at 80% of cap; hard-block new cap+1 creates immediately; apply 14-day grace only when migration or downgrade leaves an owner already over cap; never restrict already-created entities.
    • Post-trial fallback is read-only Archive state, not a perma-free tier.
    • Annual price note: roughly 10 months paid; annual not exposed until after pilot.
    • No rent take-rate language.
    • No app-store billing language; verify EXPO_PUBLIC_NATIVE_STORE_BILLING_ENABLED is correct for store builds (App Store 3.1.1 risk).
    • 26+ units: "Contact us" CTA only — no self-serve upgrade (handled in EP1-T8 / EP1-T9).
  • Done when:

    • A landlord can understand trial → plan → caps → upgrade trigger, and a 26+ unit visitor is routed to the contact path.
  • [x] EP1-T5: Create Founding Landlord Program offer

  • Role: Product Owner
  • Goal: Recruit qualified pilot users on a closed, conditional offer (NOT a permanent free tier).
  • Requirements:
    • Cohort capped at the first ~50 qualified landlords; close once filled and reflect "closing soon / cohort-limited" on the page.
    • Offer 90 days free.
    • Include migration help.
    • Include founding price-lock for 12 months after pilot ends.
    • Require 2-10 self-managed units.
    • Require activating at least two live units within 30 days.
    • Require weekly pilot check-in.
    • Require testimonial / case-study consent (short quote at minimum).
    • CTA asks for portfolio review or pilot application.
  • Done when:
    • The offer can be published on landing page and used in outreach, and the application captures the conditional commitments above.
  • Implementation note:

    • Public landing CTAs now open the Founding Pilot Intake form.
    • The form captures applicant name, email, optional phone, city, active rental units, management model, current tools, upcoming live workflow, artifact readiness, willingness to move one real lease, activation/check-in/testimonial/contact commitments, and a free-text message.
    • Admin can review submitted applicants in the Founding Pilot section, including qualification counters and per-applicant qualification details.
  • [x] EP1-T6: Create pilot intake form requirements

  • Role: Product Owner
  • Supporting roles: Frontend Developer, Backend Developer
  • Goal: Qualify pilot applicants.
  • Requirements:
    • Capture name and contact email.
    • Capture city.
    • Capture number of active rental units.
    • Capture self-managed vs agency-managed.
    • Capture current tools.
    • Capture upcoming move-in, move-out, renewal, late payment, simple support-report need, or other event.
    • Capture willingness to show real artifacts.
    • Capture willingness to move one real lease into pilot.
    • Score applicants using the 2-10 unit, self-managing, artifact-ready, pilot-ready criteria.
  • Done when:
    • Frontend Developer and Backend Developer can implement the form and Product Owner can rank applicants.
  • Implementation note:

    • The shipped public intake now collects the full qualification profile: contact details, city, unit count, management model, current tools, upcoming workflow, artifact readiness, real-lease readiness, two-unit activation commitment, weekly check-ins, testimonial/case-study consent, and pilot contact consent.
    • Backend persists the qualification fields, exposes them through the public intake response and admin list, and reports global self-managed, artifact-ready, pilot-committed, and fully qualified applicant counters in the admin validation summary.
    • Web-admin surfaces those counters and row-level qualification details so Product Owner can rank applicants without reading free-text messages first.
  • [x] EP1-T7: Create first SEO/content briefs

  • Role: Product Owner
  • Goal: Prepare launch acquisition assets.
  • Requirements:
    • Brief for occasional lease starter kit.
    • Brief for handover and settlement guide.
    • Brief for late rent reminder guide.
    • Brief for spreadsheet vs landlord system comparison.
    • Each brief includes target query, reader, CTA, product tie-in, and required screenshots/assets.
  • Done when:

    • Each content asset can be written without another strategy discussion.
  • [x] EP1-T8: Define >25-unit inbound policy and referral script

  • Role: Product Owner
  • Supporting role: Designer
  • Goal: Handle inbound that exceeds the Plus cap without breaking the narrow ICP scope.
  • Requirements:
    • "Contact us" wall replaces the self-serve upgrade button at Plus+1; no self-serve Enterprise tier.
    • Optional Plus+ design-partner tier at 199 PLN/month for 26–50 single-operator portfolios; max 2 customers in year 1; no SLA; explicit design-partner agreement; no custom feature builds.
    • 51+ units, or any team / accountant / agency need → "Not the right fit" path: politely decline, name-check Bidrento and casavi as alternatives, capture for the agency waiting list (EP1-T9).
    • Write a one-page "Not the right fit" script and save it under docs/operations/ so support and the founder say the same thing.
    • Track inbound that hit the wall: count, source, portfolio size, referred-out vs design-partner-accepted.
  • Done when:

    • A 60-unit inquiry can be handled in one reply from any team member using the script.
  • [x] EP1-T9: Build agency waiting list capture

  • Role: Frontend Developer
  • Supporting roles: Backend Developer, Product Owner
  • Goal: Collect demand signal for a future agency / portfolio product without committing to build it.
  • Requirements:
    • Email capture with optional unit count, role, and free-text message.
    • Reachable from the pricing page "Contact us" CTA and the "Not the right fit" referral path.
    • Stored separately from pilot intake — these are NOT pilot applicants.
    • Auto-reply confirms "we'll email you when we have an agency product"; does NOT promise a date.
    • Exported / queryable so Product Owner can review the list monthly.
  • Done when:
    • A 100-unit visitor can leave their email in one step and Product Owner can read the list.
  • Implementation note:

    • Public mobile pricing "Contact us" opens a dedicated agency waitlist form with email, optional unit count, role, and message.
    • Backend stores entries separately from pilot intake and admin can review/filter them in web-admin.
    • Transactional email auto-reply is deferred until the email sender work lands; the in-app confirmation states that MamNajem will contact them when large-portfolio access is ready and does not promise a date.
  • [x] EP1-T10: Implement trial, Archive, and cap enforcement

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Designer, Product Owner
  • Goal: Build the subscription state machine and cap logic the pricing page (EP1-T4) depends on.
  • Requirements:
    • Add trial state: 30-day no-card, full Portfolio features, trialEndsAt timestamp.
    • Add Archive (read-only) state: post-trial / post-cancel default; data readable, no new properties / leases / tenants / outbound notifications.
    • Rename / migrate existing DB plans (BASIC / Starter 9.99 / Standard 89.99 / Pro 249.99) to Solo 19.99 / Portfolio 49.99 / Plus 99.99 PLN gross monthly; old self-serve prices are not preserved.
    • Cap enforcement: count active properties and tenants only (archived excluded); separate property and tenant counters.
    • Paywall behavior: soft-warn at 80% of cap; hard-block new cap+1 creates immediately; apply 14-day grace only when migration or downgrade leaves an owner already over cap; never restrict access to already-created entities.
    • Cap applies on creation, not on existence.
    • Mobile / web surfaces: trial countdown badge, cap progress indicator, paywall modal with upgrade CTA, Archive-state empty states, ">25 units → contact us" routing.
    • Keep native IAP behind EXPO_PUBLIC_NATIVE_STORE_BILLING_ENABLED; verify the prod store-build value so digital subscriptions do not route to web checkout.
    • Ensure SubscriptionEnforcementFilter blocks new-entity writes per the above.
    • Tests cover: trial expiry, cap+1 block, archived-not-counted, grace timer, IAP flag fallback.
  • Done when:
    • A test landlord can start a no-card trial, fall back to Archive after trial/cancel, upgrade to Solo, and hit the immediate 4th-property block; migration/downgrade overages receive the 14-day grace without disrupting existing records.
  • Implementation note:
    • Backend, mobile/web, docs, and infrastructure changes shipped to integration on 2026-06-13.
    • Integration API verified Solo / Portfolio / Plus prices at 19.99 / 49.99 / 99.99 PLN and public web pricing verified with agent-browser.
    • Stripe live/test price IDs are wired through infrastructure; Google was updated manually by Product Owner.

Epic 2: Owner-First Activation And Analytics

Goal: Prove landlord value before tenant adoption is required.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: full analytics warehouse, complex reporting suite, tenant-first onboarding redesign.

Evidence: mobile routes, PropertiesController.java, LeaseController.java

Tasks

  • [x] EP2-T1: Define activation event taxonomy
  • Role: Product Owner
  • Goal: Define exactly what must be measured.
  • Requirements:
    • Include qualified_signup.
    • Include icp_units_selected.
    • Include property_created.
    • Include lease_created.
    • Include document_uploaded.
    • Include rent_schedule_created.
    • Include payment_request_sent.
    • Include payment_proof_uploaded.
    • Include handover_started.
    • Include handover_completed.
    • Include tenant_invited.
    • Include second_live_unit_activated.
    • Include subscription_started.
    • Include subscription_canceled.
    • Include pilot_case_study_approved.
    • Define allowed properties for each event.
    • Define which properties must never contain PII.
  • Done when:
    • Frontend Developer and Backend Developer have a complete event contract to implement.
  • Implementation note:

  • [x] EP2-T2: Add ICP capture to onboarding

  • Role: Frontend Developer
  • Supporting roles: Backend Developer, Product Owner, Designer
  • Goal: Store data needed to identify qualified users.
  • Requirements:
    • Capture role.
    • Capture city.
    • Capture unit count band.
    • Capture self-managed vs agency-managed.
    • Store values in a backend-supported user/profile/settings model.
    • Expose values to analytics without PII.
    • Do not block existing users from entering the app.
  • Done when:
    • New users can complete onboarding and the ICP fields are available for segmentation.
  • Implementation note:

    • Backend stores dedicated ICP fields on the user profile: city, unit count band, management model, and capture timestamp.
    • Mobile owner onboarding now shows an inline ICP capture step before subscription setup, with a skip path so existing or returning users are not blocked.
    • The backend exposes the non-PII unit band and management model in the user profile for EP2-T3 analytics segmentation. City is stored for product ops but must be banded or omitted before analytics emission.
  • [x] EP2-T3: Instrument activation events

  • Role: Frontend Developer
  • Supporting roles: Backend Developer, Product Owner
  • Goal: Track owner activation funnel.
  • Requirements:
    • Emit events from the action that proves completion, not from screen views.
    • Include environment.
    • Include role.
    • Include unit count band.
    • Include anonymized user/account identifier.
    • Do not send names, emails, phone numbers, addresses, IBAN, message content, document names, or lease descriptions.
  • Done when:
    • Events can be observed in the configured analytics destination for a test account.
  • Implementation note:

    • Backend now exposes POST /v1/activation-events and stores PII-safe activation records in activation_events.
    • User identity, role, and the salted anonymous user key are derived server-side; clients send only taxonomy event names and enum/band properties.
    • Mobile owner onboarding emits icp_units_selected after a successful ICP save and emits qualified_signup only when the saved ICP values match the first-release qualification rules.
    • EP2-T4 remains responsible for the weekly dashboard or query layer over the stored activation events.
  • [x] EP2-T4: Create activation dashboard or query doc

  • Role: Backend Developer
  • Supporting role: Product Owner
  • Goal: Let Product Owner review pilot activation.
  • Requirements:
    • Show qualified signups.
    • Show owner-only activation rate.
    • Show property created count.
    • Show lease created count.
    • Show rent schedule created count.
    • Show tenant invite rate.
    • Show second live unit activation.
    • Show subscription started and canceled.
    • Segment pilot cohort separately from organic users.
  • Done when:
    • Product Owner can review activation weekly without asking for raw logs.
  • Implementation note:

    • Backend now exposes GET /v1/admin/activation-overview for admin-only activation aggregates with date range and cohort filters.
    • Web-admin now includes a primary Activation page with qualified signups, owner-only activation rate, created workflow counts, tenant invite rate, second-live-unit count, and subscription started/canceled counts.
    • Qualified signup and cohort segmentation come from activation_events; workflow, second-unit, and subscription metrics are derived from backend tables for qualified owners until the remaining activation events are instrumented.
  • [x] EP2-T5: Polish owner setup path

  • Role: Designer
  • Supporting role: Frontend Developer
  • Goal: Make the first value path obvious.
  • Requirements:
    • Primary path is property -> lease -> document -> rent schedule.
    • Tenant invite appears after the owner has created core lease context.
    • Stripe Connect setup is not required for owner-only activation.
    • Native billing is not required for owner-only activation.
    • Empty states point to the next activation step.
  • Done when:
    • A new landlord can complete owner-only activation without tenant acceptance.
  • Implementation note:
    • Product Owner reviewed the existing owner setup path and accepted it as already implemented for the pilot.
    • Bank account setup remains required before lease/rent schedule creation; Stripe Connect and native billing remain outside owner-only activation.

Goal: Make product behavior legally honest and evidence-ready before paid launch.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: full e-signature integration, one-click legal notices, eviction automation, tenant screening, legal guarantees.

Evidence: polish-residential-lease-product-spec.md, e-signature-strategy-poland.md, polish-legal-review-checklist.md

Tasks

  • [x] EP3-T1: Create legal review packet
  • Role: Product Owner
  • Goal: Give Polish counsel exact product material to review.
  • Requirements:
    • Include current terms.
    • Include current privacy policy.
    • Include landlord onboarding copy.
    • Include lease setup screenshots or flow description.
    • Include handover confirmation wording.
    • Include final settlement wording.
    • Include rent reminder/payment proof wording.
    • Include Stripe Connect rent payment posture.
    • Ask explicit questions for ordinary lease.
    • Ask explicit questions for occasional lease.
    • Ask explicit questions for institutional lease.
    • Ask explicit questions for deposit handling.
    • Ask explicit questions for QES/notary/delivery proof.
    • Ask explicit questions for GDPR retention and IBAN handling.
  • Done when:
    • Product Owner can send the packet for legal review without needing another product walkthrough.
  • Implementation note:

    • Created Polish legal review packet with current terms/privacy links, onboarding and lease setup posture, handover and final settlement wording, rent proof/reminder posture, Stripe Connect rent payment posture, and explicit counsel questions.
    • Created Legal review response log as the Product Owner gate-control artifact for counsel answers, required changes, and final pass evidence. This does not complete the legal review gate until counsel answers are recorded and required changes are merged.
  • [x] EP3-T2: Add lease type model

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Product Owner
  • Goal: Track lease type without overclaiming support.
  • Requirements:
    • Add ordinary lease as supported/default.
    • Add occasional lease as tracked/hybrid unless Product Owner records legal approval for full support.
    • Add institutional lease as tracked/unsupported unless Product Owner records legal approval for support.
    • Store lease type on lease record.
    • Expose lease type in owner lease setup.
    • Do not show "guaranteed eviction" or equivalent language.
  • Done when:
    • Lease type is stored and visible without implying unsupported legal automation.
  • Implementation note:

    • Added backend lease type storage and API fields for ordinary, occasional, and institutional leases. New leases default to ordinary when the client omits the field.
    • Added owner-facing lease type selection in lease setup/edit screens and lease detail visibility.
    • Copy treats ordinary as pilot-supported, occasional as tracked/hybrid with offline notary/document requirements, and institutional as tracked-only/unsupported for the pilot.
    • Removed older in-app copy that implied ordinary/occasional legal setup was fully handled inside MamNajem.
  • [x] EP3-T3: Add execution method tracking

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Designer
  • Goal: Record how a document or lease was executed.
  • Requirements:
    • Support values: in-app acknowledgement, wet ink, external e-sign, QES, notary/hybrid, unknown.
    • Store execution method for relevant lease/document artifacts.
    • UI explains that in-app acknowledgement is evidence, not always written form.
    • Existing handover confirmation still works.
  • Done when:
    • Product can distinguish evidence acknowledgement from formal signature method.
  • Implementation note:

    • Backend and mobile now record execution method for legal artifacts so in-app acknowledgement, wet ink, external e-sign, QES, notary/hybrid, and unknown execution can be distinguished without implying a formal signature method.
  • [x] EP3-T4: Add legal artifact metadata

  • Role: Backend Developer
  • Goal: Create a durable record for generated or uploaded legal artifacts.
  • Requirements:
    • Store artifact type.
    • Store template or source version.
    • Store generated/uploaded timestamp.
    • Store related property id.
    • Store related lease id.
    • Store file/asset id where applicable.
    • Store hash or checksum where feasible.
    • Store execution method.
    • Store confirmation status.
  • Done when:
    • Handover, settlement, and future legal artifacts can share one metadata pattern.
  • Implementation note:

    • legal_artifacts stores type, source version, related property/lease links, optional asset and handover links, asset hash snapshot, execution method, confirmation status, audit timestamps, and creator metadata.
  • [x] EP3-T5: Add delivery proof path

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Designer
  • Goal: Let users store proof that an artifact was delivered.
  • Requirements:
    • Support proof type: registered mail, in person, e-delivery, external signing package, other.
    • Store address snapshot where relevant.
    • Store proof asset.
    • Store sent date.
    • Store delivered date when known.
    • Store failure/return reason when known.
    • Do not treat proof upload as legal service confirmation.
  • Done when:
    • Owner can attach delivery evidence to a lease-related artifact.
  • Implementation note:

    • Delivery proof storage, API, and mobile form now capture proof type, sent and delivered dates, address snapshot, failure reason, and optional proof asset without treating proof upload as legal service confirmation.
  • [x] EP3-T6: Update legal-boundary copy

  • Role: Product Owner
  • Supporting role: Designer
  • Goal: Remove unsafe claims.
  • Requirements:
    • No copy says the app replaces a lawyer.
    • No copy says in-app tap equals written form.
    • No copy says occasional lease is fully digital.
    • No copy says eviction is guaranteed.
    • No copy says rent increases can be made anytime.
    • No copy says legal notices are valid without proper form and delivery.
  • Done when:
    • Product Owner approves public and in-app legal-boundary copy.
  • Implementation note:
    • Handover and final settlement copy now frames confirmations as saved evidence or acknowledgement, not legal advice, a formal agreement replacement, or guaranteed legal validity.

Epic 4: Handover, Deposit, Final Settlement

Goal: Make handover, deposit, and final settlement credible as a paid evidence workflow.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: court pack automation, formal claims waiver generation, advanced accounting, repair cost estimation.

Evidence: HandoverProtocolService.java, FinalSettlementService.java

Tasks

  • [x] EP4-T1: Define handover release requirements
  • Role: Product Owner
  • Supporting role: Designer
  • Goal: Define exact handover behavior for launch.
  • Requirements:
    • Move-in protocol supported.
    • Move-out protocol supported.
    • Items supported.
    • Rooms/areas supported if already available or explicitly required.
    • Meter readings supported.
    • Key handover supported.
    • Photos supported.
    • Tenant confirmation supported.
    • Tenant decline with reason supported.
    • Confirmation copy has Product Owner approval after legal review.
  • Done when:
    • Backend Developer and Frontend Developer can compare current implementation against launch requirements.
  • Implementation note:

  • [x] EP4-T2: Enforce protocol immutability after confirmation

  • Role: Backend Developer
  • Goal: Prevent silent edits to confirmed evidence.
  • Requirements:
    • Confirmed protocol cannot be edited in place.
    • Replacement protocol references replaced protocol.
    • Replacement preserves original protocol.
    • Audit log records confirmation.
    • Audit log records decline.
    • Audit log records replacement.
  • Done when:
    • Tests prove confirmed protocol cannot be silently modified.
  • Implementation note:

    • Existing handover guards now have regression coverage for protocol notes, protocol deletion, item deletion, and replacement preserving the original declined protocol.
  • [x] EP4-T3: Add deposit ledger v1

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Product Owner, Designer
  • Goal: Track deposit lifecycle.
  • Requirements:
    • Track deposit due.
    • Track deposit collected.
    • Track deposit applied to deductions.
    • Track deposit refundable.
    • Track deposit returned.
    • Track deposit disputed.
    • Store deposit amount.
    • Store vacated date.
    • Store refund due date.
    • Store deduction items.
    • Store refund amount.
  • Done when:
    • Owner can see current deposit state for a lease.
  • Implementation note:

    • Backend deposit ledger v1 stores one ledger per lease, deduction rows, computed totals, refund due date, participant reads, owner-only writes, audit records, and OpenAPI-published API endpoints.
    • Deduction writes are serialized with a ledger row lock before aggregate reads so returned/refundable invariants cannot be bypassed by concurrent deduction changes.
    • Mobile final settlement now shows the deposit ledger, editable owner amounts, deduction create/update/delete controls, tenant read-only review state, and integration-smoked deployed UI coverage.
  • [x] EP4-T4: Add deposit refund deadline reminder

  • Role: Backend Developer
  • Supporting role: Product Owner
  • Goal: Remind owner about deposit return after move-out.
  • Requirements:
    • Refund deadline is derived from vacated date.
    • Owner dashboard or notifications show upcoming deadline.
    • Reminder uses in-app/push.
    • Reminder uses email after Epic 6 is complete.
    • Copy avoids legal certainty until reviewed.
  • Done when:
    • Test lease with move-out date produces visible refund deadline.
  • Implementation note:

    • Backend scans open deposit ledgers with refund deadlines due in the next seven days, creates an owner reminder through existing in-app/push notification channels, and skips duplicate reminders for the same lease and refund due date.
    • Email remains deferred until Epic 6 delivery work is complete.
  • [x] EP4-T5: Harden final settlement statement

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Designer, Product Owner
  • Goal: Make final settlement understandable and reviewable.
  • Requirements:
    • Show rent arrears.
    • Show repair/deduction items.
    • Show deposit offset.
    • Show final refund or payment due.
    • Show tenant acceptance.
    • Show tenant dispute/decline.
    • Store owner confirmation.
    • Store tenant confirmation.
    • Product Owner reviews wording around acceptance and settlement.
  • Done when:
    • Owner and tenant can review the same settlement record and its status.
  • Implementation note:

    • Backend publishes GET /v1/leases/{leaseId}/final-settlement/statement, shared by owner and tenant, with rent arrears, repair/deduction items, deposit offset, final refund/payment due, confirmation state, and dispute/decline metadata.
    • Mobile final settlement details load that shared statement and display the same computed rows for both roles.
  • [x] EP4-T6: Add settlement evidence export

  • Role: Backend Developer
  • Supporting role: Frontend Developer
  • Goal: Let owner collect settlement evidence.
  • Requirements:
    • Export or evidence view includes handover protocol.
    • Includes photos/assets linked to protocol.
    • Includes final settlement statement.
    • Includes tenant acceptance or decline.
    • Includes relevant payment proof where linked.
    • Includes timestamps.
  • Done when:
    • Owner can gather settlement evidence without manually searching multiple screens.
  • Implementation note:
    • Backend publishes owner-only GET /v1/leases/{leaseId}/final-settlement/evidence with the final settlement statement, handover protocols and item photo asset metadata, tenant confirmation/decline state, linked payment receipts, and timestamps.
    • Mobile final settlement details adds an owner action to open a settlement evidence view that renders the aggregate package in one screen.

Epic 5: Off-Ledger Rent Tracking

Goal: Make bank-transfer and proof-based rent tracking the default launch payment workflow.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: BLIK/P24/PayU/Tpay integration, wallet, escrow, rent take-rate, automatic recurring collection.

Evidence: PaymentRequestService.java, PaymentReceiptService.java, RentPaymentsController.java, mobile route mobile-frontend/app/(app)/property/[propertyId]/leases/[leaseId]/payments/[requestId]/index.tsx, polish-rent-collection-payments-strategy.md

Tasks

  • [x] EP5-T1: Decide launch payment posture
  • Role: Product Owner
  • Supporting roles: Frontend Developer, Backend Developer
  • Goal: Decide what rent payment flow is public.
  • Requirements:
    • Choose one: off-ledger only, off-ledger default with Stripe optional, or Stripe default.
    • Document decision in docs/roadmap/pre-release-charter.md.
    • If Stripe remains visible, require legal/payment review.
    • If Stripe is hidden, define feature flag or UI removal.
  • Done when:
    • Frontend Developer and Backend Developer know whether to hide, flag, or keep Stripe rent checkout.
  • Implementation note:

    • Decision recorded in docs/roadmap/pre-release-charter.md: the first paid pilot is off-ledger rent tracking only for tenant rent. Stripe remains for landlord SaaS subscription billing and future optional embedded-collection pilots, but ordinary tenant rent-payment UX must prioritize bank transfer instructions, proof upload, owner mark-paid, reminders, overdue visibility, audit trail, and final settlement evidence.
    • Follow-up implementation: EP5-T2 makes bank transfer/proof primary in payment request UI, and EP5-T6 hides or feature-flags Stripe rent checkout from public launch surfaces.
  • [x] EP5-T2: Make bank transfer default in payment request UI

  • Role: Designer
  • Supporting role: Frontend Developer
  • Goal: Present transfer/proof flow as primary.
  • Requirements:
    • Tenant sees amount.
    • Tenant sees due date.
    • Tenant sees landlord IBAN.
    • Tenant sees payment reference.
    • Tenant sees proof upload action.
    • Stripe checkout is not the primary CTA unless explicitly approved.
  • Done when:
    • Tenant can understand how to pay by bank transfer from the payment request screen.
  • Implementation note:

    • Payment request details now make bank transfer instructions and proof upload the tenant launch path. The screen shows amount, due date, payment title/reference, landlord bank account/IBAN, and an upload-proof action for eligible tenant requests.
    • Rent Stripe checkout is not shown by default on the payment-request surface; it appears only when EXPO_PUBLIC_RENT_STRIPE_CHECKOUT_ENABLED=true.
  • [x] EP5-T3: Add or verify payment proof upload

  • Role: Backend Developer
  • Supporting role: Frontend Developer
  • Goal: Link proof to a payment request.
  • Requirements:
    • Tenant can upload proof asset.
    • Proof is attached to the payment request.
    • Owner can view proof.
    • Owner can mark request paid.
    • Owner can reject/ask for correction if supported by current scope.
    • Audit log records proof upload and status change.
  • Done when:
    • A test payment request can move from pending to proof uploaded to paid.
  • Implementation note:

    • Tenant proof upload uses the existing payment receipt API and attachment flow. A tenant may attach only their own new PRIVATE, lease-key-scoped asset to the receipt they created on the same ACTIVE or ENDED lease; legacy receipts without creator provenance stay tenant-attach denied. Owner attachment is unchanged.
    • Owner and tenant can view receipt proof through the payment receipt list, and owner mark-paid remains the status confirmation step. Receipt creation writes the existing audit entry and status updater path; tenant-created proof also notifies the owner.
    • Separate reject/correction workflow is not a launch-scope control; owners can leave the request unpaid and use existing messaging/support paths if the proof is wrong.
  • [x] EP5-T4: Add overdue visibility

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Product Owner
  • Goal: Show owner which rent items need action.
  • Requirements:
    • Owner dashboard shows overdue payment requests.
    • Lease detail shows overdue payment requests.
    • Tenant sees overdue state.
    • Overdue state does not generate legal warning language.
  • Done when:
    • Overdue request is visible to owner and tenant in test data.
  • Implementation note:

    • Backend computes overdue status at read time from unpaid payment requests whose effective due date is past, using tenantWindowTo or an approved deferredUntil date, without storing OVERDUE as the canonical database state.
    • Owner dashboard aggregates overdue payment count and amount by property/current month; lease payment lists and payment detail responses expose overdue items through the existing payment request APIs.
    • Tenant dashboard, lease payment sections, payment lists, and payment detail screens show overdue state with neutral action wording such as "overdue" / "requires attention"; no legal warning, termination, penalty, or arrears-notice language is introduced.
    • Coverage exists in backend overdue/list/detail/dashboard tests and mobile dashboard/payment-list/payment-detail tests; focused verification on 2026-06-25 passed for those suites.
  • [x] EP5-T5: Add rent reminder rules

  • Role: Product Owner
  • Supporting roles: Backend Developer, Frontend Developer
  • Goal: Define non-legal reminder behavior.
  • Requirements:
    • Define reminder timing before due date.
    • Define reminder timing after due date.
    • Define channels: in-app, push, email after Epic 6.
    • Define message copy.
    • Copy must not be an arrears warning or termination notice.
  • Done when:
    • Backend Developer and Frontend Developer can implement reminders without writing legal copy.
  • Implementation note:

    • Reminder timing, channels, payload fields, deduplication behavior, and safe English/Polish copy are defined in Rent reminder rules.
    • The launch rule is in-app plus push only; email is added after Epic 6 delivery verification. Reminder copy stays operational and explicitly excludes statutory arrears warning, termination, enforcement, penalty, and debt-collection language.
  • [x] EP5-T6: Hide or feature-flag Stripe rent checkout if required

  • Role: Frontend Developer
  • Supporting roles: Backend Developer, Product Owner
  • Goal: Prevent payment overreach at launch.
  • Requirements:
    • Add config flag or existing flag usage for Stripe rent checkout visibility.
    • Default Polish launch environment follows EP5-T1 decision.
    • Subscription Stripe checkout remains unaffected.
    • Tests verify rent checkout visibility follows config.
  • Done when:
    • Rent checkout can be disabled without breaking rent tracking.
  • Implementation note:
    • Mobile rent checkout visibility is gated by EXPO_PUBLIC_RENT_STRIPE_CHECKOUT_ENABLED=true; default launch behavior hides checkout while keeping subscription Stripe checkout unaffected.
    • Tests cover default hidden checkout, explicit flag-enabled checkout, and tenant proof upload.

Epic 6: Email And Reminder Delivery

Goal: Send critical transactional emails for invites, reminders, billing, handover, and settlement.

Primary role: Backend Developer

Supporting roles: Product Owner, Designer, Infra Developer

Do not include: newsletter, marketing automation, CRM nurture, complex email builder.

Evidence: NotificationService.java, architecture README

Tasks

  • [x] EP6-T1: Define transactional email scope
  • Role: Product Owner
  • Goal: List emails required for launch.
  • Requirements:
    • Tenant invitation email.
    • Rent reminder email.
    • Payment proof received email.
    • Handover confirmation request email.
    • Final settlement request email.
    • Subscription/billing email where not already handled by Stripe.
    • Account/legal transactional email where required.
  • Done when:
    • Backend Developer has exact email event list and no marketing emails are included.
  • Implementation note:

    • Launch email event keys, triggers, recipient sources, preference behavior, and out-of-scope marketing/legal boundaries are defined in Transactional email scope.
  • [x] EP6-T2: Verify email infrastructure

  • Role: Infra Developer
  • Supporting role: Backend Developer
  • Goal: Confirm SES or chosen provider can send app transactional email.
  • Requirements:
    • Confirm sender domain.
    • Confirm sender address.
    • Confirm environment variables/secrets.
    • Confirm sandbox/production sending status.
    • Confirm bounce/complaint handling requirement.
  • Done when:
    • Backend Developer can send a test email from integration environment.
  • Implementation note:

    • SES provider readiness is documented in Email infrastructure verification: mamnajem.pl is verified for sending, DKIM and custom MAIL FROM are green, SES production sending is enabled, bounce/complaint account suppression is enabled, and a simulator test send from [email protected] succeeded.
    • The backend app email sender is still EP6-T3. No SES secret is needed; EP6-T3 should add non-secret sender config and use the integration runtime AWS credential chain.
  • [x] EP6-T3: Implement backend email sender

  • Role: Backend Developer
  • Goal: Make EMAIL notification channel send real email.
  • Requirements:
    • Integrate with SES or chosen provider.
    • Use template-based messages.
    • Support Polish copy for launch events.
    • Log delivery attempt without PII in structured logs.
    • Handle provider errors without failing unrelated workflow transaction unless required.
  • Done when:
    • Backend test or integration check confirms email sender is called for EMAIL notifications.
  • Implementation note:

    • Backend NotificationChannel.EMAIL delivery is implemented through the SES v2 async sender and documented in Email delivery implementation.
    • The sender saves the notification row first, renders Polish/English text templates, submits through SES when enabled, logs provider message ids without recipient/body PII, and suppresses provider failures so unrelated workflow transactions are not rolled back.
    • Local mvn -q verify and backend pipeline 2628220111 passed; integration API health returned UP after deploy. Workflow-level email wiring was completed later in EP6-T5.
  • [x] EP6-T4: Create email templates

  • Role: Designer
  • Supporting roles: Product Owner, Backend Developer
  • Goal: Define copy and layout for launch emails.
  • Requirements:
    • Polish tenant invitation template.
    • Polish rent reminder template.
    • Polish payment proof notification template.
    • Polish handover confirmation request template.
    • Polish final settlement request template.
    • Plain-text fallback for each template.
    • No legal overstatement.
  • Done when:
    • Templates are ready for implementation and Product Owner approves copy.
  • Implementation note:

    • Polish launch templates, plain-text fallbacks, legal-boundary notes, and backend mapping are documented in Launch email templates.
    • Template scope covers tenant invitations, rent reminders, payment proof notifications, handover confirmation requests, and final settlement requests.
    • Copy is approved for EP6-T5 implementation under delegated Product Owner approval; counsel review can still amend wording before production rollout.
  • [x] EP6-T5: Wire invite and reminder emails

  • Role: Backend Developer
  • Goal: Send email from critical workflows.
  • Requirements:
    • Invitation creation sends tenant invite email.
    • Rent reminder event sends rent reminder email.
    • Handover confirmation request sends email.
    • Final settlement request sends email.
    • User email preferences are respected where applicable.
    • Tests cover recipient selection.
  • Done when:
    • Integration test or manual integration check verifies each email event.
  • Implementation note:
    • Backend workflow wiring is documented in Email workflow wiring.
    • Invitation creation now sends direct SES email to the invitation address; invitees do not need a pre-existing account.
    • Rent reminders run through RentReminderService with EMAIL, in-app, and push channels, deduped per recipient/request/rule.
    • Payment proof, handover pending-confirmation, and final settlement notifications include NotificationChannel.EMAIL and respect notifyEmail.
    • Local mvn -q verify and backend pipeline 2628301591 passed; integration API health returned UP after deploy.
    • The 2026-06-26 live workflow smoke in Email workflow wiring verified the SES tenant-invitation path on integration with CloudWatch providerMessageId evidence after the runtime IAM permission fix.

Epic 7: Admin And Support Readiness

Goal: Support paid pilot users without manual database edits or unclear recovery steps.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: full CRM, user impersonation, internal analytics suite, admin-side property management.

Evidence: AdminProblemReportController.java, StripeWebhookOpsController.java, web-admin App.tsx

Tasks

  • [x] EP7-T1: Verify admin allowlist contract
  • Role: Backend Developer
  • Supporting role: Frontend Developer
  • Goal: Prove web-admin and the launch backend agree.
  • Requirements:
    • Confirm local backend exposes /v1/admin/access-allowlist.
    • Confirm generated OpenAPI includes the endpoint.
    • Confirm integration backend exposes /v1/admin/access-allowlist.
    • Confirm web-admin calls the same contract for list, create, and update.
    • Fix backend, web-admin, OpenAPI, or environment config if any check differs.
  • Done when:
    • A release reviewer can list, create, and update an allowlist entry from web-admin against integration.
  • Evidence:

  • [x] EP7-T2: Verify problem report triage UI

  • Role: Frontend Developer
  • Supporting roles: Backend Developer, Designer
  • Goal: Prove support can triage submitted app problems.
  • Requirements:
    • Confirm web-admin can list problem reports.
    • Confirm filtering by status works.
    • Confirm report detail opens.
    • Confirm status changes persist.
    • Confirm attached photo viewing/download works if a report has an attachment.
    • Confirm reporter, topic, created date, and status are visible.
    • Fix any backend/web-admin gap found during the smoke check.
  • Done when:
    • Product Owner can process a test problem report from web-admin against integration.
  • Evidence:

  • [x] EP7-T3: Verify Stripe webhook recovery path

  • Role: Backend Developer
  • Supporting roles: Frontend Developer, Infra Developer, Product Owner
  • Goal: Prove stuck webhook events can be recovered safely.
  • Requirements:
    • Confirm admin can list dead/retryable webhook events from web-admin or a documented API call.
    • Confirm admin can replay an event.
    • Confirm replay requires admin auth.
    • Confirm replay result is visible.
    • Confirm processed-webhook idempotency records are visible.
    • Confirm runbook states when not to replay.
    • Fix any backend/web-admin/runbook gap found during the smoke check.
  • Done when:
    • Product Owner can recover a test dead webhook without database access in integration.
  • Evidence:

    • Stripe webhook recovery verification records backend fixture/replay changes, local backend verification, integration pipeline results, API smoke, and web-admin browser smoke evidence from 2026-06-25.
  • [x] EP7-T4: Write support macros

  • Role: Product Owner
  • Goal: Prepare repeatable first-line support.
  • Requirements:
    • Macro for failed tenant invite.
    • Macro for payment proof confusion.
    • Macro for handover decline.
    • Macro for billing issue.
    • Macro for account export.
    • Macro for account deletion.
    • Macro for Stripe rent payment issue if Stripe remains visible.
  • Done when:
    • Product Owner can answer each issue without writing a new response from scratch.
  • Evidence:

    • Pilot support macros provides first-line Polish replies, internal checks, escalation triggers, and wording guardrails for all required EP7-T4 support cases.
  • [x] EP7-T5: Write pilot support operating procedure

  • Role: Product Owner
  • Goal: Define how pilot support runs.
  • Requirements:
    • Define support channel.
    • Define response target.
    • Define escalation path.
    • Define incident owner.
    • Define what gets logged.
    • Define stop conditions for pilot if support load is too high.
  • Done when:
    • Product Owner can run pilot support for one week using the procedure.
  • Evidence:
    • Pilot support operating procedure defines channels, response targets, escalation, incident ownership, logging fields, daily/weekly operating rhythm, and pilot stop conditions.

Epic 8: Privacy, Retention, Security, Production Readiness

Goal: Make privacy, data handling, and production operation safe enough for paid users.

Primary role: Infra Developer

Supporting roles: Backend Developer, Product Owner

Do not include: SOC 2 program, multi-region architecture, broad infrastructure rebuild, enterprise compliance project.

Evidence: privacy-policy-v1.md, DATA_RETENTION.md, BankAccountService.java, aws-production main.tf

Tasks

  • [x] EP8-T1: Decide IBAN storage policy
  • Role: Product Owner
  • Supporting role: Backend Developer
  • Goal: Resolve privacy/code mismatch.
  • Requirements:
    • Decide whether to implement field-level encryption now.
    • Decide whether privacy policy must be changed.
    • Decide whether data export returns full or masked IBAN.
    • Decide whether existing IBAN values need migration.
  • Done when:
    • Decision is recorded in docs/roadmap/pre-release-charter.md or a linked privacy decision doc.
  • Evidence:

    • IBAN storage policy decision decides no new server-side KMS field-level encryption before pilot, requires privacy-policy updates, keeps backend export from adding raw full IBAN for protected bank accounts, and requires plaintext-row inventory/migration before paid production.
  • [x] EP8-T2: Execute IBAN decision

  • Role: Backend Developer
  • Supporting role: Product Owner
  • Goal: Make implementation and policy match.
  • Requirements if implementing encryption:
    • Encrypt IBAN at rest before persistence.
    • Decrypt only where business flow requires full IBAN.
    • Mask IBAN in list views where full value is not required.
    • Update tests for create, read, export, payment request display.
  • Requirements if changing policy instead:
    • Remove KMS field-encryption claim from privacy policy.
    • State actual controls accurately.
    • Product Owner approves final text.
  • Done when:
    • No product/legal doc promises a control the code does not provide.
  • Evidence:

    • Backend stores payment request and schedule transfer-instruction snapshots for tenant-visible bank-transfer display while keeping owner bank account profile writes client-protected.
    • Mobile sends bankTransferDetails from the selected decrypted account for request, lease setup, and schedule edit flows.
    • Privacy policy v1 now describes lease-participant IBAN sharing and actual controls without a new KMS field-encryption claim.
    • See IBAN storage policy decision.
  • [x] EP8-T3: Align retention policy and implementation

  • Role: Product Owner
  • Supporting role: Backend Developer
  • Goal: Resolve automated retention mismatch.
  • Requirements:
    • Compare DATA_RETENTION.md to privacy policy.
    • Choose which categories require automated cleanup before release.
    • Remove automated cleanup claims if not implemented.
    • Define lease/legal/tax evidence retention exceptions.
    • Define account deletion behavior when active leases or legal records exist.
  • Done when:
    • Retention docs and product behavior no longer conflict.
  • Evidence:

    • Retention policy alignment compares DATA_RETENTION.md to the privacy policy, decides that no new automated expired-record cleanup is required before the first paid pilot, defines lease/legal/tax/payment/audit evidence exceptions, and records the active/pending lease account deletion block.
    • Backend DATA_RETENTION.md and privacy-policy-v1.md now use matching retention periods and avoid claiming configured automated cleanup.
    • Backend RetentionPolicyConsistencyTest guards the alignment.
  • [x] EP8-T4: Harden production database recovery

  • Role: Infra Developer
  • Goal: Reduce paid-launch data-loss risk.
  • Requirements:
    • Review RDS backup retention.
    • Review final snapshot behavior.
    • Review deletion protection.
    • Define recovery objective.
    • Document restore check procedure.
  • Done when:
    • Production database backup policy is approved for paid pilot.
  • Evidence:

    • Production database recovery policy approves the paid-pilot RDS recovery posture: 7-day automated backup/PITR retention, final snapshot on intentional destroy, RDS deletion protection, Terraform prevent_destroy, Multi-AZ, and RPO/RTO targets.
    • Architecture production-database-recovery.md documents the restore-check procedure and requires restore to a new DB instance before any production cutover.
    • Architecture Jest guard documents production database recovery objectives and restore checks protects the runbook/signoff/incident-response links.
  • [x] EP8-T5: Add or verify RDS alarms

  • Role: Infra Developer
  • Goal: Detect database incidents.
  • Requirements:
    • Alarm or dashboard for CPU.
    • Alarm or dashboard for storage.
    • Alarm or dashboard for memory.
    • Alarm or dashboard for connections.
    • Alarm or dashboard for latency.
    • Incident runbook references actual alarms.
  • Done when:
    • Product Owner and Infra Developer can find database health from the runbook.
  • Evidence:

    • RDS alarm verification accepts the production RDS alarm set for paid pilot coverage.
    • Architecture aws-alerts.md now includes the direct CloudWatch lookup command and actual alarm names for CPU, storage, memory, connections, read latency, write latency, disk queue depth, and burst balance.
    • Architecture Jest guard documents new alarm meanings, integration traffic checks, and remaining risks protects the runbook lookup path and alarm names.
  • [x] EP8-T6: Harden admin Cognito config

  • Role: Infra Developer
  • Goal: Reduce admin auth risk.
  • Requirements:
    • Review admin MFA setting.
    • Remove placeholder callback URLs from production.
    • Review OAuth flow settings.
    • Verify logout URLs.
    • Verify admin group requirements.
  • Done when:
    • Production admin auth config has no placeholder URLs and required access controls are documented.
  • Evidence:

    • Admin Cognito hardening accepts the production admin Cognito posture for the paid pilot.
    • Architecture admin-cognito-auth.md documents software-token MFA, operator-only user creation, no hosted admin OAuth redirects, empty admin callback/logout URLs, Cognito-only identity provider use, and ADMIN group requirements.
    • Architecture Jest guard documents admin Cognito access controls and production redirect posture protects the runbook and production release signoff link.
  • [x] EP8-T7: Resolve integration domain inconsistency

  • Role: Infra Developer
  • Supporting roles: Frontend Developer, Backend Developer
  • Goal: Make integration URLs consistent.
  • Requirements:
    • Decide canonical integration API domain.
    • Decide canonical integration web domain.
    • Align docs.
    • Align mobile CI defaults.
    • Align web-admin env examples.
    • Align Cognito callbacks.
    • Align Playwright defaults.
    • Align Terraform values.
  • Done when:
    • No release-critical config points at the wrong integration domain.
  • Evidence:

    • Integration domain consistency records .pl as the canonical integration API, web, and admin domain family.
    • Architecture integration Terraform, Cognito callbacks, Stripe/Google integration URLs, and tests use integration.mamnajem.pl and web-integration.mamnajem.pl.
    • Mobile CI and Playwright defaults already use https://integration.mamnajem.pl/v1 and https://web-integration.mamnajem.pl.
    • Web-admin .env.example uses https://integration.mamnajem.pl/v1.
    • Backend integration email app URL fallback now uses https://web-integration.mamnajem.pl and is guarded by IntegrationDomainConfigTest.
    • Superseded 2026-11-08: integration moved to mamnajem.win (API https://api.mamnajem.win/v1, web https://www.mamnajem.win, admin https://admin.mamnajem.win, docs https://docs.mamnajem.win); the evidence above records the state when this task was closed.
  • [x] EP8-T8: Write release worktree checklist

  • Role: Infra Developer
  • Goal: Prevent bad branch/release operations.
  • Requirements:
    • Check each repo worktree status.
    • Check current branch.
    • Check integration/production ancestry.
    • Check no production-only commits.
    • Check fast-forward-only promotion path.
    • Check pipeline monitoring requirement after push.
  • Done when:
    • Release operator can verify branch safety without asking for git instructions.
  • Evidence:
    • Release worktree checklist accepts the EP8-T8 release-hygiene gate for the paid pilot.
    • Published runbook release-worktree-checklist.md gives exact commands for per-repo status, current branch, ancestry, production-only commit detection, fast-forward-only promotion, pipeline monitoring, and agent-browser integration verification.
    • Architecture runbook release-worktree-checklist.md and Jest guard release worktree checklist protect the operator checklist and production signoff link.

Epic 9: Simple Issue Reporting

Goal: Verify and harden the existing in-app problem report flow as the launch issue-reporting surface.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer, QA

Do not include: vendor marketplace, contractor assignment, SLA engine, quotes, invoices, property-manager work orders.

Evidence: ProblemReportService.java, useSubmitReportProblem.ts, AdminProblemReportController.java, support-problem-report.real.spec.ts, polish-maintenance-workflow.md

Tasks

  • [x] EP9-T1: Confirm launch issue-reporting promise
  • Role: Product Owner
  • Goal: Keep the public promise aligned with the existing simple report flow.
  • Requirements:
    • Promise only simple issue/problem submission from inside the app.
    • Treat existing topic as the simple title/category.
    • Treat existing message as the description.
    • Map internal OPEN and IN_PROGRESS to open support work.
    • Map internal RESOLVED and DISMISSED to closed support work.
    • Do not promise lease-linked repair management, timelines, contractor assignment, or owner/tenant responsibility resolution.
  • Done when:
    • Public copy, product copy, and backlog wording all describe the same simple issue-reporting scope.
  • Evidence:

    • Simple issue reporting promise accepts the EP9-T1 launch copy boundary for the paid pilot.
    • Mobile tenant landing copy promises "simple issues"; tenant-invite copy now promises "simple in-app reports" in English, Polish, and Ukrainian.
    • Mobile guard language utilities > keeps launch issue-reporting copy scoped to simple in-app reports protects the copy boundary.
    • Charter and backlog wording map topic, message, optional photoAssetId, open states, and closed states without promising repair management, contractor assignment, timelines, or responsibility resolution.
  • [x] EP9-T2: Verify plaintext problem report contract

  • Role: Backend Developer
  • Supporting role: Frontend Developer
  • Goal: Keep mobile submissions and backend configuration aligned on plaintext support reports.
  • Requirements:
    • Keep PROBLEM_REPORTS_REQUIRE_ENCRYPTED_CONTENT=false unless a future privacy decision changes support-report handling.
    • Confirm mobile submits topic, plaintext message, and optional photoAssetId.
    • Confirm backend creates plaintext reports by default.
    • Keep encrypted payload support tested as an optional compatibility path.
  • Done when:
    • Owner and tenant problem reports are accepted in the target environment with plaintext descriptions.
  • Evidence:

    • Plaintext problem report contract accepts the EP9-T2 plaintext support-report posture for the paid pilot.
    • Backend config keeps PROBLEM_REPORTS_REQUIRE_ENCRYPTED_CONTENT=false by default.
    • Backend ProblemReportsIntegrationTest verifies plaintext report creation by default and encrypted payload support as an optional compatibility path.
    • Mobile useSubmitReportProblem test verifies topic, plaintext message, and optional photoAssetId submission.
    • 2026-11-08: end-to-end encryption was removed; the encrypted variant and the PROBLEM_REPORTS_REQUIRE_ENCRYPTED_CONTENT setting no longer exist.
    • Mobile integration pipeline 2629177853 passed app_test and e2e_test; the real E2E support spec covers owner and tenant plaintext submissions in the target environment.
  • [x] EP9-T3: Smoke owner and tenant report submission

  • Role: QA
  • Supporting role: Frontend Developer
  • Goal: Prove the existing app flow works for both roles.
  • Requirements:
    • Owner can open account support and submit a report.
    • Tenant can open account support and submit a report.
    • Required-field validation works.
    • Optional screenshot upload works.
    • Created reports start as OPEN.
  • Done when:
    • Integration smoke evidence covers owner and tenant submissions.
  • Evidence:

    • Problem report submission smoke accepts the EP9-T3 owner/tenant smoke gate for the paid pilot.
    • Mobile integration pipeline 2629177853 passed app_test and e2e_test on commit 7a27fdd0.
    • Real E2E support-problem-report.real.spec.ts covers owner support navigation, required-field validation, screenshot upload, plaintext report creation, OPEN status, and tenant report creation without screenshot.
  • [x] EP9-T4: Smoke admin report triage

  • Role: QA
  • Supporting role: Backend Developer
  • Goal: Prove support can process submitted reports.
  • Requirements:
    • Admin can list problem reports.
    • Admin can view report details.
    • Admin can move OPEN to IN_PROGRESS.
    • Admin can move a report to RESOLVED.
    • Support procedure explains that RESOLVED and DISMISSED are closed states.
  • Done when:
    • Support can triage a test report without direct database access.
  • Evidence:

    • Admin problem report triage smoke accepts the EP9-T4 admin triage smoke gate for the paid pilot.
    • Existing integration smoke verified admin list, detail, photo download, OPEN to IN_PROGRESS, and RESOLVED status update without direct DB access.
    • Backend ProblemReportsIntegrationTest and web-admin App/api tests now guard the RESOLVED path.
    • Pilot support operating procedure maps OPEN/IN_PROGRESS to open support work and RESOLVED/DISMISSED to closed support work.
  • [x] EP9-T5: Remove broader maintenance promises

  • Role: Product Owner
  • Supporting role: Designer
  • Goal: Avoid selling a workflow the product does not yet implement.
  • Requirements:
    • Audit landing, app, onboarding, and help copy for maintenance/repair wording.
    • Keep only simple issue reporting unless a separate post-launch epic is approved.
    • Move lease-linked repair workflows to post-launch backlog.
  • Done when:
    • Launch materials no longer imply lease-linked maintenance management.
  • Evidence:
    • Maintenance promise audit accepts the EP9-T5 launch-copy boundary for the paid pilot.
    • Mobile role-onboarding copy in English, Polish, and Ukrainian no longer promises fixing, repairs, or maintenance from the service-provider role.
    • Mobile guard language utilities > does not promise repair or maintenance workflows in role onboarding copy protects the copy boundary.
    • Lease-linked maintenance workflow is documented as post-launch backlog only, pending pilot/interview evidence and a separate approved epic.

Epic 10: Pilot Operations And Validation Gate

Goal: Decide go, narrow, or stop based on real landlord behavior and willingness to pay.

Primary role: Product Owner

Supporting roles: Designer, Frontend Developer, Backend Developer

Do not include: generic survey, vanity waitlist, broad PR launch, free beta with no conversion pressure.

Evidence: poland-launch-validation-pack.md, polish-landlord-tenant-validation-plan.md, poland-90-day-launch-plan.md

Tasks

  • [x] EP10-T1: Create founding pilot ops doc
  • Role: Product Owner
  • Goal: Define how the pilot runs.
  • Requirements:
    • Define offer.
    • Define eligibility.
    • Define onboarding process.
    • Define participant obligations.
    • Define support channel.
    • Define weekly check-in process.
    • Define price-lock terms.
  • Done when:
    • A qualified landlord can be onboarded without a custom process.
  • Evidence:

    • Founding pilot ops defines the Founding Landlord Program offer, eligibility, intake decision, onboarding steps, participant obligations, support channel, weekly check-in process, price-lock terms, legal boundary, and exit rules.
  • [x] EP10-T2: Create landlord interview script

  • Role: Product Owner
  • Goal: Validate real workflow pain.
  • Requirements:
    • Ask landlord to show last lease.
    • Ask landlord to show last handover/protocol/photos.
    • Ask landlord to show rent tracker or bank proof process.
    • Ask landlord to show last deposit settlement.
    • Ask landlord to show last repair/issue thread.
    • Ask whether they will move one real lease into pilot.
    • Record exact blocker if they refuse.
  • Done when:
    • Interviewer can run the call and capture comparable evidence.
  • Evidence:

    • Landlord interview script gives the interviewer a prep note, opening script, fit screen, exact artifact walkthrough prompts, product reaction and pilot commitment tests, price probe, blocker taxonomy, notes template, and lead classification rules.
  • [x] EP10-T3: Create tenant interview script

  • Role: Product Owner
  • Goal: Validate tenant adoption gates.
  • Requirements:
    • Ask tenant about document access.
    • Ask tenant about handover confirmation.
    • Ask tenant about payment proof.
    • Ask tenant about issue reporting.
    • Ask tenant about final settlement/deposit discussion.
    • Ask which tasks they would actually complete in an app.
  • Done when:
    • Interviewer can identify which tenant tasks block landlord value.
  • Evidence:

    • Tenant interview script gives the interviewer a prep note, opening script, fit screen, tenant workflow walkthrough prompts, app adoption test, rejection test, pilot task test, adoption blocker taxonomy, notes template, and landlord-value interpretation rules.
  • [x] EP10-T4: Create pilot scorecard

  • Role: Product Owner
  • Goal: Measure pilot outcome.
  • Requirements:
    • Track qualified applicants.
    • Track accepted pilots.
    • Track activated landlords.
    • Track activated units.
    • Track owner-only activation.
    • Track tenant task completion.
    • Track number of workflows completed.
    • Track support requests per landlord.
    • Track price acceptance.
    • Track churn/refusal reason.
  • Done when:
    • Product Owner can make weekly pilot decisions from one scorecard.
  • Evidence:

    • Pilot scorecard defines the weekly cohort summary, participant row template, activation definitions, workflow completion matrix, price signal fields, support load fields, and continue/narrow/pause/stop review rules.
  • [x] EP10-T5: Build outreach list

  • Role: Product Owner
  • Goal: Recruit target landlords.
  • Requirements:
    • 50 self-managing landlord leads or community contacts.
    • Segment by city.
    • Segment by estimated unit count where known.
    • Include landlord educators/community owners.
    • Include warm referral source where available.
    • Exclude agencies unless separately marked.
  • Done when:
    • Outreach can start without more lead research.
  • Evidence:

    • Founding pilot outreach list provides 50 community contacts or direct-owner lead slots segmented by city, source, estimated unit-count knowledge, warm path, and first action, with agency-managed leads excluded unless separately marked.
  • [ ] EP10-T6: Run first pilot onboarding batch

  • Role: Product Owner
  • Goal: Move real leases into the product.
  • Requirements:
    • Start with 3-5 landlords if support capacity is limited.
    • Each landlord brings at least one real lease.
    • Each landlord completes property setup.
    • Each landlord completes lease setup.
    • Each landlord uploads at least one document.
    • Each landlord creates rent schedule.
    • Each landlord completes at least three target workflows during pilot.
  • Done when:
    • First batch has measurable activation and blocker notes.
  • Execution aid:

    • Pilot onboarding batch log is ready for the first 3-5 landlord batch.
    • web-admin integration commit f8c411b adds Founding Pilot batch-readiness metrics and row-level readiness labels to help select accepted pilot candidates from the admin intake list.
    • backend integration commit f42e9cf and web-admin integration commit 75fe580 add persistent applicant review state, accepted-count visibility, and admin controls for recording ACCEPTED, WAITLIST, NURTURE, DECLINED, or NOT_FIT decisions before copying approved landlords into the Batch 1 log.
    • backend integration commit 2babd1f and web-admin integration commit a97825a add review-decision filtering so the Product Owner can isolate accepted applicants before building Batch 1.
    • backend integration commit 12de0d8 and web-admin integration commit 1dc76b7 add a global validation summary so Batch 1 readiness is not inferred from only the current admin table page.
    • backend integration commit 0fd5f95 and web-admin integration commit 0c74ae2 add per-applicant activation evidence for matched account, owner-only readiness, app-backed workflow counts, and blocker signals before anonymized participant counts are copied into the Batch 1 log.
    • backend integration commit 3a5302c and web-admin integration commit 41144cc extend per-applicant evidence with in-app support-load status counts for the matched owner account and linked tenant accounts.
    • backend integration commit 198b293 and web-admin integration commit 9a6ac48 add admin outcome/support capture for pilot outcome, refusal/churn blocker, P0/P1 incident counts, support hours, and final support status after the support log is reviewed.
    • backend integration commit 5f5ee63 and web-admin integration commit 8eb3ad8 add persistent Batch 1 onboarding state to each intake row, the admin PATCH /v1/admin/founding-pilot-intake/{id}/batch endpoint, OpenAPI coverage, batch-status summary counters, and web-admin controls for participant ID, accepted/kickoff timestamps, first workflow, current blocker, and next action.
    • web-admin integration commit 70ebd60 adds Copy batch log, an anonymized Markdown snapshot action for loaded batch rows, so the Product Owner can update Batch 1 docs from participant ID, source row, city/unit bands, accepted/kickoff dates, first workflow, batch status, blocker, and next action without copying applicant PII.
    • web-admin integration commit 15eb1cf makes Copy batch log include accepted applicants with no saved Batch 1 status as empty rows, so Needs batch gaps can be copied into the onboarding log instead of disappearing from the snapshot. It also normalizes Wrocław to the wroclaw city band. Web-admin pipeline 2631905926 and AWS Amplify job 56 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the batch snapshot strings and the protected backend summary route returns 401 without admin auth. This reduces manual reconciliation, but it does not mark EP10-T6 complete without real accepted/onboarded pilot landlords.
    • web-admin integration commit 34550f3 makes Copy batch log fetch every matching founding-pilot page and include Rows exported, so Batch 1 onboarding logs are not capped at the visible admin page. Web-admin pipeline 2632108038 and AWS Amplify job 62 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the batch full-export markers and the protected backend list route returns 401 without admin auth. This reduces missed onboarding evidence risk, but EP10-T6 still requires real accepted/onboarded pilot landlords.
    • web-admin integration commit 5f3de7d adds Copy activation log, an anonymized Markdown snapshot action for loaded activation evidence, so the Product Owner can update Activation Log rows from participant IDs and measured app-backed counts without copying applicant PII or matched user IDs.
    • web-admin integration commit d43ccac adds Load evidence, a toolbar action that bulk-loads activation evidence for visible Founding Pilot rows before Copy activation log, so the Product Owner can refresh the Activation Log without clicking Evidence on every row. Web-admin pipeline 2631853329 and AWS Amplify job 54 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the bulk evidence labels and the protected backend summary route returns 401 without admin auth. This reduces manual reconciliation, but it does not mark EP10-T6 complete without real accepted/onboarded pilot landlords.
    • web-admin integration commit 5fd6e6e makes Copy activation log fetch every matching founding-pilot page, load missing activation evidence, and include Rows exported, so Activation Log rows are not capped at the visible admin page. Web-admin pipeline 2632137296 and AWS Amplify job 63 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the activation full-export markers and the protected backend list and activation-evidence routes return 401 without admin auth. This reduces missed activation evidence risk, but EP10-T6 still requires real accepted/onboarded pilot landlords.
    • backend integration commit 81f24bc adds measured deposit/settlement and message/reminder counters to per-applicant activation evidence, and includes those categories in the activation workflow count.
    • web-admin integration commit f039241 exports those measured deposit/settlement and message/reminder counts from Copy activation log while retaining not_measured fallback cells for older backend responses.
    • backend integration commit d2529ed and web-admin integration commit 6f6f2be add app-backed tenant-task completion counts, split activation log tenant invite volume from tenant task completion volume, and expose memo tenant-task participant/completion counters. Backend pipeline 2631162540 and web-admin pipeline 2631162539 succeeded on integration.
    • backend integration commit 63565bc and web-admin integration commit e3e3f20 add Batch 1 activation-gap counters for batched pilots missing matched users, owner-only readiness, 3+ workflows, or tenant-task evidence to the validation summary and memo snapshot. Backend pipeline 2631248886 and web-admin pipeline 2631248812 succeeded on integration.
    • backend integration commit 2dd46e4 and web-admin integration commit 8cc0ecf add a Founding Pilot action queue filter. Use Needs batch to find accepted applicants without saved Batch 1 status, then use the other action queues to clear pricing, post-pilot, outcome, and refusal blocker gaps. Backend pipeline 2631380073 and web-admin pipeline 2631380022 succeeded on integration.
    • backend integration commit 4e794be and web-admin integration commit 36bc273 add a Needs interview action queue for accepted applicants missing landlord interview evidence. Backend pipeline 2632706952, web-admin pipeline 2632706932, and AWS Amplify job 65 succeeded on integration. Smoke verification confirmed deployed bundle index-BpjH9HBy.js contains NEEDS_INTERVIEW, Needs interview, and the queue reason, and the protected backend list route with pilotAction=NEEDS_INTERVIEW returns 401 without admin auth. This reduces missed interview evidence risk, but EP10-T6 still requires real accepted/onboarded pilot landlords.
    • web-admin integration commit 07d4e13 adds Copy action queue, an anonymized Markdown snapshot for the selected Founding Pilot action queue. It copies participant ID, queue reason, review decision, batch status, pricing response, post-pilot next step, outcome, blocker code, and next action while excluding applicant PII, free-form intake messages, review notes, and support case identifiers. web-admin pipeline 2631996084 and AWS Amplify job 58 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the action-queue snapshot strings and the protected backend summary route returns 401 without admin auth. This reduces queue cleanup drift, but EP10-T6 still requires real accepted/onboarded pilot landlords.
    • web-admin integration commit 0bbbd74 makes Copy action queue reload all pages for the selected action queue at the backend's 100-row page cap and add a Rows exported count to the copied Markdown. web-admin pipeline 2632024385 and AWS Amplify job 59 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the full-export marker and the protected backend summary route returns 401 without admin auth. This prevents oversized queues from being copied as partial visible-page worklists, but EP10-T6 still requires real accepted/onboarded pilot landlords.
    • web-admin integration commit 9631990 adds Copy scorecard, a privacy-safe Markdown snapshot action for the weekly scorecard. Pipeline 2631570060 succeeded on integration. AWS Amplify job 51 for the F9-managed admin app published the same commit to the integration admin branch. Integration browser smoke confirmed the admin shell, the protected summary route behavior, and the deployed bundle containing Copy scorecard and Pilot Scorecard Snapshot.
    • backend integration commit cd5a697, backend coverage follow-up c6d1406, and web-admin integration commit 39b5d29 record per-applicant landlord/tenant interview completion timestamps, expose global and Batch 1 interview counters in the validation summary, and fill the scorecard interview rows from those counters. Backend pipeline 2631782983, web-admin pipeline 2631761550, and AWS Amplify job 52 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the interview controls and the protected backend summary route returns 401 without admin auth. This removes manual interview counting, but it does not mark EP10-T6 complete without real accepted/onboarded pilot landlords.
    • web-admin integration commit 60ee151 adds Copy interview log, an anonymized full-export snapshot for row-level landlord/tenant interview evidence. web-admin pipeline 2632684605 and AWS Amplify job 64 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains Copy interview log, Copy founding pilot interview log snapshot, and Pilot Interview Log Snapshot, and the protected backend summary route returns 401 without admin auth. This reduces interview reconciliation risk, but it does not mark EP10-T6 complete without real accepted/onboarded pilot landlords.
    • EP10-T6 remains open until real pilot landlords are accepted, onboarded with real leases, measured, and blocker notes are recorded.
  • [ ] EP10-T7: Run pricing test

  • Role: Product Owner
  • Goal: Validate willingness to pay.
  • Requirements:
    • Validate the 19.99 / 49.99 / 99.99 PLN gross monthly pilot ladder, or use a documented equivalent.
    • Ask price for actual portfolio size.
    • Ask post-pilot plan choice.
    • Do not test percent-of-rent pricing.
    • Record exact objection for rejected prices.
  • Done when:
    • At least 30% of qualified pilot landlords accept or pre-commit to a realistic fixed monthly price, or the reason they do not is documented.
  • Execution aid:

    • Pilot pricing test log defines the fixed monthly ladder, script, response log, objection codes, calculation, and completion rule.
    • Backend integration commit 8358992 and web-admin integration commit 646ee0e add persistent pricing-test capture on accepted founding-pilot applicants, including qualified-pilot flag, plan asked, tested price, response, accepted plan, objection code/note, post-pilot next step, and pricing timestamp.
    • Backend integration commit 12de0d8 and web-admin integration commit 1dc76b7 add global pricing-test counts, acceptance rate, and rejected responses missing an objection so the scorecard can be copied from a full-cohort summary.
    • Backend integration commit ea0db65 and web-admin integration commit 52b2bea add Batch 1 pricing-progress summary metrics so the EP10-T7 calculation can use accepted/onboarded pilot participants instead of the full intake list.
    • web-admin integration commit 4154546 adds Copy pricing log, an anonymized Markdown snapshot action for loaded pricing-test rows, so the Product Owner can update the response log from participant IDs, unit bands, pricing response fields, and scrubbed objection notes without copying applicant PII.
    • backend integration commit 7dc11bd and web-admin integration commit bdb4806 add Batch 1 pricing rejected, rejected-with-objection, and rejected-missing-objection counters to the validation summary and memo snapshot so EP10-T7 is evaluated from the accepted/onboarded cohort instead of global intake rejection counts.
    • backend integration commit fef70d6 and web-admin integration commit 1435272 add Batch 1 post-pilot next-step counters for start-paid, extend, downgrade, archive, churn, not-decided, and missing follow-up to the validation summary and memo snapshot. Backend pipeline 2631197648 and web-admin pipeline 2631197649 succeeded on integration.
    • backend integration commit 2dd46e4 and web-admin integration commit 8cc0ecf add row-level Needs pricing, Needs post-pilot, and Needs refusal blocker queues so the Product Owner can resolve EP10-T7 missing counters from the admin intake list. Backend pipeline 2631380073 and web-admin pipeline 2631380022 succeeded on integration.
    • web-admin integration commit f89df80 makes Copy pricing log include Batch 1 participants with no pricing response yet as not_asked rows, so Needs pricing gaps can be copied into the response log instead of disappearing from the snapshot. Web-admin pipeline 2631878561 and AWS Amplify job 55 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the pricing snapshot strings and the protected backend summary route returns 401 without admin auth. This reduces manual reconciliation, but EP10-T7 still requires real pricing answers from qualified pilot landlords.
    • web-admin integration commit 07d4e13 adds Copy action queue, so the Product Owner can copy selected pricing, post-pilot, and refusal-blocker queue rows as an anonymized Markdown worklist. web-admin pipeline 2631996084 and AWS Amplify job 58 succeeded on integration. Smoke verification confirmed the deployed bundle contains the action-queue snapshot strings and the protected backend summary route returns 401 without admin auth. This reduces manual queue reconciliation, but EP10-T7 still requires real pricing answers from qualified pilot landlords.
    • web-admin integration commit 0bbbd74 makes the action-queue export fetch every selected queue page and include Rows exported, so pricing and post-pilot worklists are not capped at the visible admin page. web-admin pipeline 2632024385 and AWS Amplify job 59 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the full-export marker and the protected backend summary route returns 401 without admin auth. This reduces missed pricing follow-up risk, but EP10-T7 still requires real pricing answers from qualified pilot landlords.
    • web-admin integration commit 98ff1bc makes the pricing-log export fetch every matching founding-pilot page and include Rows exported, so pricing response logs are not capped at the visible admin page. web-admin pipeline 2632061405 and AWS Amplify job 60 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the pricing full-export markers and the protected backend list route returns 401 without admin auth. This reduces missed pricing response evidence risk, but EP10-T7 still requires real pricing answers from qualified pilot landlords.
    • EP10-T7 remains open until qualified pilot landlords are asked the price for their actual portfolio and responses are recorded.
  • [ ] EP10-T8: Write go / narrow / stop memo

  • Role: Product Owner
  • Goal: Decide launch path.
  • Requirements:
    • Go requires real workflows moved into product.
    • Go requires owner-only activation evidence.
    • Go requires realistic price acceptance.
    • Go requires manageable support load.
    • Narrow is allowed if one wedge works but scope or price needs adjustment.
    • Stop is required if landlords will not move real workflows or only accept free.
  • Done when:
    • Memo states go, narrow, or stop with evidence from the scorecard.
  • Execution aid:
    • Pilot go narrow stop memo defines the final decision template, required scorecard evidence, stop conditions, and completion rule.
    • Backend integration commit 12de0d8 and web-admin integration commit 1dc76b7 provide global validation summary inputs for the memo snapshot, but EP10-T8 still requires real pilot activation, pricing, support, and refusal/churn evidence before a decision can be made.
    • Backend integration commit 0fd5f95 and web-admin integration commit 0c74ae2 provide per-applicant activation evidence inputs for the memo, but the memo still cannot be completed until those inputs contain real pilot landlord data.
    • Backend integration commit 3a5302c and web-admin integration commit 41144cc add in-app support-load status counts to those per-applicant evidence inputs.
    • Backend integration commit 198b293 and web-admin integration commit 9a6ac48 add final outcome/support evidence fields for the memo: outcome, blocker code, outcome note, support status, P0/P1 counts, and support hours. These fields make the scorecard/memo inputs queryable, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit e8e874e and web-admin integration commit 8923ba3 add cohort-level memo evidence counters to the validation summary for batched pilots matched to users, owner-only-ready batched participants, and batched participants with at least three app-backed workflows. These counters reduce manual reconciliation for the memo, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit a17a79e aligns the cohort-level Memo 3+ workflows counter with row-level activation evidence by including deposit/settlement and message/reminder workflow categories. This prevents the final memo snapshot from undercounting real pilot usage in those areas, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit 3a14d26 and web-admin integration commit 63d8f20 add batch-scoped final outcome/support counters and memo snapshot rows for outcomes recorded, outcomes missing, refused/churned participants, support watch/stop status, P0/P1 incidents, and support hours. This keeps the go/narrow/stop decision tied to the actual Batch 1 cohort, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit d2529ed and web-admin integration commit 6f6f2be add tenant-task participant/completion counters and split tenant invites from tenant task completions in activation snapshots. This keeps the memo from treating owner-created invites as tenant adoption, but EP10-T8 still requires real pilot entries before a decision can be made.
    • web-admin integration commit 5a7d2a0 adds a Copy memo snapshot action that formats the aggregate Founding Pilot validation summary as a Markdown table for the memo. It reduces copy/paste errors, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit 7e70f61 and web-admin integration commit 9d2f528 add Batch 1 refusal/churn blocker completeness counters and memo snapshot rows for blockers complete and blockers missing. This prevents a go/narrow/stop memo from passing with undocumented churn or refusal reasons, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit 2dd46e4 and web-admin integration commit 8cc0ecf add row-level action queues for batch, pricing, post-pilot, outcome, and refusal-blocker follow-up. This lets the Product Owner drill from aggregate memo gaps to exact admin rows, but EP10-T8 still requires real pilot entries before a decision can be made.
    • Backend integration commit 4e794be and web-admin integration commit 36bc273 add a Needs interview action queue for accepted applicants missing landlord interview evidence. Backend pipeline 2632706952, web-admin pipeline 2632706932, and AWS Amplify job 65 succeeded on integration. Smoke verification confirmed deployed bundle index-BpjH9HBy.js contains the queue labels and the protected backend list route with pilotAction=NEEDS_INTERVIEW returns 401 without admin auth. This reduces scorecard/memo interview cleanup risk, but EP10-T8 still requires real activation, pricing, support, and refusal/churn evidence before a decision can be made.
    • backend integration commit cd5a697, backend coverage follow-up c6d1406, and web-admin integration commit 39b5d29 add completed landlord/tenant interview counters and Batch 1 interview counters to the scorecard/memo evidence path. Backend pipeline 2631782983, web-admin pipeline 2631761550, and AWS Amplify job 52 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the interview labels and the protected backend summary route returns 401 without admin auth. This keeps interview evidence queryable, but EP10-T8 still requires real activation, pricing, support, and refusal/churn evidence before a decision can be made.
    • web-admin integration commit 98eca3b adds a computed Memo readiness metric and Memo Readiness table to the copied memo snapshot. The table turns existing Batch 1, activation, pricing, support, tenant-task, outcome, and refusal/churn counters into missing, review, or ready rows with concrete next actions, plus an overall memo readiness state. web-admin pipeline 2631817891 and AWS Amplify job 53 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the readiness labels and the protected backend summary route returns 401 without admin auth. This reduces manual memo reconciliation, but EP10-T8 still requires real pilot evidence before a decision can be made.
    • web-admin integration commit 2611d67 adds Copy outcome log, an anonymized Markdown snapshot for Batch 1 final outcome/support rows. It preserves participant ID, batch status, post-pilot next step, final outcome, refusal/churn blocker, outcome note, support status, P0/P1 counts, support hours, and outcome recorded date while excluding applicant PII, free-form intake messages, review notes, and support case identifiers. web-admin pipeline 2631937361 and AWS Amplify job 57 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the outcome snapshot strings and the protected backend summary route returns 401 without admin auth. This reduces final memo copy/paste risk, but EP10-T8 still requires real pilot evidence before a decision can be made.
    • web-admin integration commit 07d4e13 adds Copy action queue, an anonymized Markdown snapshot for selected row-level memo cleanup queues. It makes missing outcome and refusal/churn blocker worklists copyable without applicant PII or support case identifiers. web-admin pipeline 2631996084 and AWS Amplify job 58 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the action-queue snapshot strings and the protected backend summary route returns 401 without admin auth. This reduces final memo cleanup drift, but EP10-T8 still requires real pilot evidence before a decision can be made.
    • web-admin integration commit 0bbbd74 makes selected action-queue exports include every queue page plus a Rows exported count, so missing outcome and refusal/churn blocker worklists are not silently limited to the visible admin page. web-admin pipeline 2632024385 and AWS Amplify job 59 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the full-export marker and the protected backend summary route returns 401 without admin auth. This reduces final memo cleanup risk, but EP10-T8 still requires real pilot evidence before a decision can be made.
    • web-admin integration commit 0db165b makes Copy outcome log fetch every matching founding-pilot page and include Rows exported, so final outcome/support reconciliation is not capped at the visible admin page. web-admin pipeline 2632085157 and AWS Amplify job 61 succeeded on integration. Smoke verification confirmed the deployed admin bundle contains the outcome full-export markers and the protected backend list route returns 401 without admin auth. This reduces final memo evidence omission risk, but EP10-T8 still requires real pilot evidence before a decision can be made.
    • EP10-T8 remains open until scorecard, onboarding, pricing, support, and refusal/churn evidence supports a real go, narrow, or stop decision.

Release Gate Checklist

Gate Owner role Required evidence
Release charter approved Product Owner docs/roadmap/pre-release-charter.md exists and has approval note.
Public positioning narrowed Product Owner Landing targets self-managing Polish landlords.
Pricing and founder offer live Product Owner Pricing and Founding Landlord Program are published or ready to publish.
Owner activation measurable Product Owner Activation events and dashboard/query verified.
Legal review complete Product Owner Counsel answers are recorded in Legal review response log, required copy/workflow changes are merged, and the charter gate is updated.
Handover/deposit/settlement release-ready Product Owner Requirements from Epic 4 accepted.
Off-ledger rent tracking default decided Product Owner EP5-T1 decision recorded and implemented.
Email delivery working Backend Developer Invite and reminder emails verified in integration.
Admin support usable Product Owner Problem report and webhook recovery paths verified.
Privacy/retention aligned Product Owner Policy and implementation mismatch closed.
Production readiness checked Infra Developer EP8-T4 through EP8-T8 accepted for DB recovery, RDS alarms, admin auth, integration domains, and release hygiene.
Pilot completed Product Owner Scorecard and go/narrow/stop memo completed.

First Execution Batch

Do these first, in this order:

  1. EP0-T1 through EP0-T4: release charter and scope freeze.
  2. EP1-T1, EP1-T4, EP1-T5, EP1-T6, EP1-T8, EP1-T9: public message, pricing, pilot offer, intake, >25-unit policy, agency waitlist.
  3. EP1-T10: trial / Archive / cap enforcement engineering (unblocks the pricing page).
  4. EP2-T1: activation event taxonomy.
  5. EP3-T1: legal review packet.
  6. EP8-T1 and EP8-T3: IBAN and retention decisions.
  7. EP7-T1 and EP7-T2: admin allowlist contract and problem report triage verification.
  8. EP10-T1 through EP10-T5: pilot ops, interviews, scorecard, outreach.

Do not start embedded payment expansion, marketplace/pre-lease syndication, tenant screening, property-manager roles, app-store billing refinement, or full e-signature integration before the first execution batch is complete.