Skip to content

MamNajem feature-parity matrix

This matrix is the versioned acceptance inventory for the immutable MamNajem candidate. Each workflow is represented once and binds existing source coverage to one repeatable command, one concrete deployed state transition, and one exact evidence record.

Result contract

A result cell reads PENDING, PASS — <UTC timestamp> — <candidate SHA>, or FAIL — <UTC timestamp> — <candidate SHA> — <finding ID>. A blocked check is a failure for candidate acceptance. Evidence JSON records the environment, full candidate matrix hash, actor role, route, action, expected state, observed state, terminal result, UTC timestamps, and sanitized artifact references. It never contains credentials, signing material, session data, or user data.

Until 2026-07-29 the guarding test required every cell to read exactly PENDING, so recording any acceptance result broke the build. The matrix could not be filled in without deleting the test that protects it, which is why every cell was still empty months after the deployment it describes. The test now enforces the grammar above instead.

A PENDING cell on its own says nothing about whether anyone tried. Every workflow that is still PENDING is therefore named in the register below with the specific thing that prevents the check from running, and the register is kept in step with the matrix by test.

Current interpretation: dated PASS and FAIL cells are candidate-specific evidence for the SHA in the cell. They do not automatically describe current deployed state after later integration work. When release-gate evidence and a dated matrix verdict disagree, the matrix row needs a fresh acceptance rerun or an explicit replacement verdict before the candidate can be accepted.

Commands run from the exact repository paths shown. Deployed route placeholders such as {propertyId} are replaced with IDs belonging to disposable acceptance fixtures. Integration runs precede production runs; production checks use the same sealed candidate and the separately recorded user promotion authority.

Source coverage below points to committed Espresso tests. Some tests cover UI boundaries rather than the complete deployed transition. Stripe completion, Google Play purchase/restore and physical-device push checks still require their stated deployed acceptance evidence. Updating a source reference does not change a candidate verdict.

Acceptance inventory

workflow role source automated coverage MamNajem automated command deployed check evidence path integration result production result
public marketing Anonymous visitor landing-frontend/e2e/smoke.spec.ts cd /home/szymek/pro/mamnajem/landing-frontend && pnpm exec playwright test e2e/smoke.spec.ts --grep "landing page" Route: /
Role: anonymous Polish and English visitor
Action: load the landing page, switch locale, follow every primary section link, and reload
Expected: localized MamNajem copy, reachable anchors, persisted locale, correct metadata, and no console or network failure
$mamnajem_evidence_root/web/public-marketing.json PENDING PENDING
legal Anonymous visitor and authenticated user landing-frontend/components/legal/LegalDocumentPage.test.tsx cd /home/szymek/pro/mamnajem/landing-frontend && pnpm exec vitest run components/legal/LegalDocumentPage.test.tsx Route: /auth/terms-of-service and /auth/privacy-policy
Role: anonymous visitor, then authenticated owner
Action: load both documents, force one API retry, and open the account legal copies
Expected: current MamNajem versions render after loading or retry and authenticated copies match public content
$mamnajem_evidence_root/web/legal.json PENDING PENDING
support Anonymous visitor and authenticated user mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/AuthenticationTests.kt
mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/AccountTests.kt
cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PublicAuthBoundariesTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.AccountSupportTest Route: /support and /auth/support
Role: anonymous visitor, then authenticated tenant
Action: open support topics and activate the contact action
Expected: both routes expose the same localized topics and an encoded support@mamnajem.pl action
$mamnajem_evidence_root/web/support.json PENDING PENDING
public intake Prospective owner and agency representative landing-frontend/components/forms/PublicForms.test.tsx cd /home/szymek/pro/mamnajem/landing-frontend && pnpm exec vitest run components/forms/PublicForms.test.tsx Route: /auth/founding-pilot-intake and /auth/agency-waitlist
Role: anonymous prospective owner, then agency representative
Action: submit valid Turnstile-backed forms and repeat one submission
Expected: one normalized record per form, success state, duplicate protection, bounded timeout recovery, and no token disclosure
$mamnajem_evidence_root/web/public-intake.json PENDING PENDING
sign-up New owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/AuthenticationTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PublicAuthBoundariesTest Route: /auth/sign-up
Role: unauthenticated disposable owner
Action: validate email and password, submit, request confirmation, and confirm the fresh account
Expected: invalid input remains local, confirmation succeeds once, and the new account reaches the legal or role gate
$mamnajem_evidence_root/mobile/android/sign-up.json PENDING PENDING
sign-in Existing owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/AuthenticationTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.AuthenticationTest Route: /auth/sign-in
Role: disposable owner, then disposable tenant
Action: authenticate, background and relaunch the app, then sign out
Expected: each role reaches its authorized dashboard, session refresh survives relaunch, and sign-out returns to sign-in
$mamnajem_evidence_root/mobile/android/sign-in.json PENDING PENDING
password reset Existing owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/AuthenticationTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PublicAuthBoundariesTest Route: /auth/forgot-password
Role: unauthenticated disposable owner
Action: request a reset code, submit the received code and a valid new password, then sign in with it
Expected: validation is non-enumerating, reset completes once, old password fails, and new password authenticates
$mamnajem_evidence_root/mobile/android/password-reset.json PENDING PENDING
owner onboarding New owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/OnboardingTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.OnboardingNavigationTest Route: /onboarding
Role: newly confirmed disposable owner
Action: choose owner role, complete profile steps, add the first property, and resume after relaunch
Expected: progress persists, completed steps do not repeat, and the dashboard shows the created property
$mamnajem_evidence_root/mobile/android/owner-onboarding.json PENDING PENDING
tenant invitation Owner and invited tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/LeaseTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.InvitationManagementTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.InvitationAcceptanceTest Route: /property/{propertyId}/leases/{leaseId}/invitations then /invitations/accept/{code}
Role: disposable owner, then invited disposable tenant
Action: create an invitation, open its deep link as tenant, and accept it once
Expected: invitation becomes accepted, tenant gains only the linked lease, and reuse is rejected
$mamnajem_evidence_root/mobile/android/tenant-invitation.json PENDING PENDING
property Owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/PropertyTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PropertyCreateTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PropertyEditTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PropertyLifecycleTest Route: /property then /property/{propertyId}
Role: disposable owner
Action: create, edit, reopen, and archive a property
Expected: normalized details persist, list and detail agree, tenant access is absent, and the terminal status is visible
$mamnajem_evidence_root/mobile/android/property.json PENDING PENDING
lease Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/LeaseTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.LeaseCreationTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.LeaseEditAndRenewalTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.LeaseStatusTest Route: /property/{propertyId}/leases/{leaseId}
Role: disposable owner, then linked tenant
Action: create and activate a lease, reopen its detail, and verify the tenant view
Expected: dates, rent, deposit, parties, status, and role-specific actions match the saved lease
$mamnajem_evidence_root/mobile/android/lease.json PENDING PENDING
document upload/download Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/LeaseTests.kt
mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/PropertyTests.kt
cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.LeaseDocumentsTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.PropertyAssetsTest Route: /property/{propertyId}/leases/{leaseId}/documents
Role: disposable owner, then linked tenant
Action: upload the fixture document, reopen the list, download it as each authorized role, and try an unrelated tenant
Expected: metadata and bytes round-trip, authorized downloads succeed, and unrelated access is denied
$mamnajem_evidence_root/mobile/android/document-upload-download.json PENDING PENDING
messaging Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/MessagingHandoverTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.MessagingTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.MessagingDeepLinkTest Route: /messaging/{leaseId}
Role: linked disposable owner and tenant
Action: exchange text and action-request messages, read them, and relaunch both sessions
Expected: both see the same ordered thread, unread state clears for the reader, and unrelated users cannot open it
$mamnajem_evidence_root/mobile/android/messaging.json PENDING PENDING
notification Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/PlatformTests.kt
mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/LeaseNotificationRedirectTest.kt
cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.NotificationsTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.LeaseNotificationRedirectTest Route: /notifications
Role: linked disposable owner and tenant
Action: trigger a workflow notification, open it, mark it read, and mark all remaining items read
Expected: correct recipient, localized content, destination route, unread count, and persisted read state
$mamnajem_evidence_root/mobile/android/notification.json PENDING PENDING
calendar Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/PropertyTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.OwnerCalendarEventTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.TenantCalendarEventTest Route: /calendar then /calendar/{eventId}
Role: linked disposable owner and tenant
Action: create, filter, edit, and delete a shared lease event
Expected: both roles see authorized updates in local date order and deletion removes the event
$mamnajem_evidence_root/mobile/android/calendar.json PENDING PENDING
rent schedule Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/LeaseTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.LeaseScheduleTest Route: /property/{propertyId}/leases/{leaseId}/schedules/{scheduleId}/edit
Role: disposable owner, then linked tenant
Action: edit amount, due day, label, and reminder settings, then reopen the generated requests
Expected: schedule persists exactly and creates the expected tenant-visible rent request without duplicates
$mamnajem_evidence_root/mobile/android/rent-schedule.json PENDING PENDING
payment proof Tenant and owner mobile-frontend/components/payment/PaymentReceiptForm.test.tsx cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm exec jest --runInBand components/payment/PaymentReceiptForm.test.tsx Route: /property/{propertyId}/leases/{leaseId}/payments/{requestId}
Role: linked disposable tenant, then owner
Action: attach proof, submit amount, date, method, and reference, then open the receipt as owner
Expected: one receipt and attachment are stored, request balance updates, and owner sees matching proof metadata
$mamnajem_evidence_root/mobile/android/payment-proof.json PENDING PENDING
hosted rent payment Tenant and owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/PaymentTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.HostedStripeRentPaymentTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.RentCheckoutTest Route: /property/{propertyId}/leases/{leaseId}/payments/{requestId}
Role: linked disposable tenant, then owner
Action: launch hosted checkout, complete a Stripe test payment, return through /rent-payment/success, and reopen the request
Expected: one successful attempt and receipt exist, request reaches paid state, and both roles see the same outcome
$mamnajem_evidence_root/mobile/android/hosted-rent-payment.json PENDING PENDING
subscription purchase/restore Owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/GooglePlayBillingTest.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.GooglePlayBillingTest Route: /subscription/plans
Role: disposable owner with store test account
Action: purchase a MamNajem plan, reinstall or clear state, then restore the purchase
Expected: entitlement activates once, survives restore without duplicate subscription, and the selected plan matches the store product
$mamnajem_evidence_root/external/subscription-purchase-restore.json PENDING PENDING
Stripe Connect Owner mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/AccountTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.StripeConnectTest Route: /account/payment then /connect/return
Role: disposable owner
Action: start onboarding, complete the Stripe test account, return to the app, and refresh readiness
Expected: charges, payouts, transfers, and rent-payment readiness match Stripe and remain attached to the owner
$mamnajem_evidence_root/external/stripe-connect.json PENDING PENDING
handover Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/MessagingHandoverTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.HandoverProtocolTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.HandoverDraftTest Route: /property/{propertyId}/leases/{leaseId}/handovers/{protocolId}
Role: linked disposable owner and tenant
Action: create items and evidence, submit, decline once, replace the protocol, and confirm both sides
Expected: immutable decision history remains visible and the replacement reaches confirmed terminal state
$mamnajem_evidence_root/mobile/android/handover.json PENDING PENDING
deposit/final settlement Owner and tenant mobile-frontend/android-e2e/androidTest/java/pl/mamnajem/e2e/tests/MessagingHandoverTests.kt cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.FinalSettlementTest && pnpm android-e2e:test:class pl.mamnajem.e2e.tests.SettlementDeclineAndResendTest Route: /property/{propertyId}/leases/{leaseId}/final-settlement
Role: linked disposable owner and tenant
Action: add deposit deductions and evidence, advance settlement, confirm both parties, and reopen details
Expected: totals reconcile to the deposit ledger, evidence remains accessible, and settlement reaches confirmed state
$mamnajem_evidence_root/mobile/android/deposit-final-settlement.json PENDING PENDING
data export Authenticated user backend/src/test/java/pl/mamnajem/integration/DataExportArchiveDownloadIntegrationTest.java cd /home/szymek/pro/mamnajem/backend && mvn -Dtest=DataExportArchiveDownloadIntegrationTest test Route: /account/data-export
Role: disposable owner, then disposable tenant
Action: request an export, wait for completion, download once, and inspect the archive inventory
Expected: each archive contains only that user’s authorized fresh-platform data and the download authorization expires as specified
$mamnajem_evidence_root/backend/data-export.json PENDING PENDING
problem report Authenticated user and admin mobile-frontend/screens/support/ReportProblemScreen.test.tsx cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm exec jest --runInBand screens/support/ReportProblemScreen.test.tsx Route: /report-problem then admin #problem-reports
Role: disposable tenant, then MamNajem admin
Action: submit a report with diagnostics and photo, open it in admin, download the photo, and change status
Expected: reporter gets one reference, admin sees sanitized context and authorized attachment, and status history persists
$mamnajem_evidence_root/admin/problem-report.json PENDING PENDING
admin authentication MamNajem admin web-admin/src/__tests__/App.test.tsx cd /home/szymek/pro/mamnajem/web-admin && pnpm exec vitest run src/__tests__/App.test.tsx Route: /
Role: fresh allowlisted MamNajem admin
Action: sign in with temporary password, set a new password, enroll TOTP, sign out, and sign in with TOTP
Expected: each challenge is required in order, dashboard loads only after TOTP, and unauthenticated API calls return 401
$mamnajem_evidence_root/admin/admin-authentication.json PENDING PENDING
admin accounts MamNajem admin backend/src/test/java/pl/mamnajem/integration/AdminAccountsIntegrationTest.java cd /home/szymek/pro/mamnajem/backend && mvn -Dtest=AdminAccountsIntegrationTest test Route: #accounts
Role: authenticated MamNajem admin
Action: search a disposable owner, open diagnostics, suspend with a reason, and verify that owner’s access
Expected: account and related aggregates load, audit reason persists, and the suspended owner is denied
$mamnajem_evidence_root/admin/admin-accounts.json PENDING PENDING
admin activation funnel MamNajem admin backend/src/test/java/pl/mamnajem/integration/ProductReportsIntegrationTest.java
backend/src/test/java/pl/mamnajem/unit/service/ProductReportCalculatorTest.java
web-admin/src/__tests__/ProductReports.test.tsx
cd /home/szymek/pro/mamnajem/backend && mvn -Dtest=ProductReportsIntegrationTest,ProductReportCalculatorTest test Route: #product-outcomes
Role: authenticated MamNajem admin
Action: inspect shared reports and selected Warsaw business periods with deterministic integration TEST fixtures
Expected: Q7 counts, maturity, classification exclusions, coverage, and current publication status match backend results; invalid current results remain unavailable
$mamnajem_evidence_root/admin/admin-activation-funnel.json PENDING PENDING
webhook recovery MamNajem admin backend/src/test/java/pl/mamnajem/integration/StripeWebhookReconciliationIntegrationTest.java cd /home/szymek/pro/mamnajem/backend && mvn -Dtest=StripeWebhookReconciliationIntegrationTest test Route: #stripe-webhooks then #processed-webhooks
Role: authenticated MamNajem admin
Action: reveal a dead Stripe event with a reason, replay it once, and filter its processed idempotency record
Expected: replay reaches processed state once, system mutation is not duplicated, and reveal and replay reasons are audited
$mamnajem_evidence_root/admin/webhook-recovery.json PENDING PENDING
health/OpenAPI Anonymous probe and operator backend/src/test/java/pl/mamnajem/e2e/MamNajemDeploySmokeE2E.java cd /home/szymek/pro/mamnajem/backend && mvn -Dtest=MamNajemDeploySmokeE2E test Route: /actuator/health then /v3/api-docs
Role: anonymous probe, then release operator
Action: request health and parse the OpenAPI document from the sealed deployment
Expected: health is UP, title is MamNajem API, canonical servers are environment-correct, and no donor namespace is exposed
$mamnajem_evidence_root/backend/health-openapi.json FAIL — 20260729T112444Z — 03c933eaa2aa8f0de4a6860cb6a55fc44d16cbc1 — MNJ-1 FAIL — 20260729T112444Z — 03c933eaa2aa8f0de4a6860cb6a55fc44d16cbc1 — MNJ-1
email New user and owner backend/src/test/java/pl/mamnajem/service/TransactionalEmailTemplateTest.java cd /home/szymek/pro/mamnajem/backend && mvn -Dtest=TransactionalEmailTemplateTest test Route: /auth/sign-up then /property/{propertyId}/leases/{leaseId}/invitations
Role: new disposable user, then disposable owner
Action: trigger confirmation and tenant-invitation mail and follow both links
Expected: verified MamNajem sender, subject, body, support address, DKIM, SPF, DMARC, and environment-correct links are present
$mamnajem_evidence_root/external/email.json FAIL — 20260729T112444Z — 03c933eaa2aa8f0de4a6860cb6a55fc44d16cbc1 — MNJ-2 FAIL — 20260729T112444Z — 03c933eaa2aa8f0de4a6860cb6a55fc44d16cbc1 — MNJ-2
push Authenticated owner and tenant mobile-frontend/hooks/notifications/usePushNotificationsBootstrap.native.test.ts cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm exec jest --runInBand hooks/notifications/usePushNotificationsBootstrap.native.test.ts Route: /account/preferences then /notifications
Role: disposable owner and tenant on newly registered devices
Action: enable push, trigger a lease notification, receive it in background, and tap it
Expected: each token belongs to the fresh MamNajem project, only intended recipient receives it, and tap opens the authorized route
$mamnajem_evidence_root/external/push.json PENDING PENDING
analytics Product analyst and owner mobile-frontend/utils/telemetry/activationTelemetry.test.ts cd /home/szymek/pro/mamnajem/mobile-frontend && pnpm exec jest --runInBand utils/telemetry/activationTelemetry.test.ts Route: /onboarding then /property/create-property
Role: disposable owner observed by product analyst
Action: complete qualified sign-up and first-property milestones and query the fresh Firebase stream by candidate SHA
Expected: one sanitized event per milestone reaches the MamNajem stream with no raw address or user data
$mamnajem_evidence_root/external/analytics.json PENDING PENDING
alerts Release operator architecture/test/newrelic-observability.test.ts
architecture/test/newrelic-discord.test.ts
cd /home/szymek/pro/mamnajem/architecture && npm test -- --runInBand test/newrelic-observability.test.ts test/newrelic-discord.test.ts Route: /actuator/health and MamNajem New Relic entities for the candidate SHA
Role: release operator
Action: verify the health baseline, emit one controlled handled failure and one threshold metric, then inspect New Relic ingestion, alert incidents, and Discord delivery
Expected: scrubbed events use the intended environment and candidate, the alert notifies once, and the recovery state is recorded
$mamnajem_evidence_root/external/alerts.json PENDING PENDING

Findings

MNJ-1 — the OpenAPI half of the health check cannot pass as written

GET /v3/api-docs returns 404 on both https://api.mamnajem.pl and https://integration.mamnajem.pl. That is deliberate: application.yml sets springdoc.api-docs.enabled to ${SPRINGDOC_API_DOCS_ENABLED:false} and neither deployment overrides it, so the document is not served anywhere. Health itself passes — both origins return {"status":"UP"}.

The row asks a hardened deployment to expose something it is hardened against. Resolving it is a decision, not a fix. Product and Infra must choose one of two acceptance contracts before this row can be replaced with a passing verdict: serve OpenAPI through a deliberate authenticated operator path, or move title, server and namespace assertions to the generated build artifact and reduce the deployed check to health alone. Do not enable public /v3/api-docs as a side effect of this matrix row.

MNJ-2 — email verdict is stale and must be rerun or superseded

sesv2 get-account for the AWS account behind both environments returns EnforcementStatus: SHUTDOWN, with ReviewDetails.Status: DENIED on case 178502209100274. Every send is rejected with AccountSuspendedException, and SentLast24Hours is 0.0.

SendingEnabled reads true and ProductionAccessEnabled reads true; neither is the operative field. This affects confirmation mail, password reset, tenant invitations, payment notifications and data-export completion — every transactional message the platform sends.

It is not fixable from the API. Reinstatement is an AWS support case and one has already been refused. See architecture/docs/runbooks/remaining-production-steps.md.

This dated verdict now conflicts with the pre-release gate record. The pre-release email docs record SES as healthy on 2026-06-25 and record a successful integration invitation smoke with a CloudWatch provider message id on 2026-06-26; the charter marks Email delivery working as Pass for launch-scope integration evidence. The matrix row still requires a fresh acceptance rerun, or a Product/Infra decision to replace this row with scoped email evidence and a production check. Do not claim production email from this document without live verification.

Checks that cannot run yet, and why

workflow what is missing
public marketing The packaged spec drives a local preview server on 127.0.0.1:4173. Checking the deployed origin needs a run pointed at https://mamnajem.pl, which does not exist yet.
legal The public documents are reachable and carry current copy; the authenticated half of the check needs a signed-in owner.
support The check is an Android flow, and there is no device or emulator attached.
public intake Submitting the forms writes a founding-pilot and an agency-waitlist record into production.
sign-up Android flow; also creates a real Cognito user.
sign-in Android flow with two disposable accounts.
password reset Android flow, and the reset code arrives by mail; the email acceptance row still needs a fresh rerun or superseding verdict.
owner onboarding Android flow; writes a property.
tenant invitation Android flow, two roles, and invitation delivery is mail; the email acceptance row still needs a fresh rerun or superseding verdict.
property Android flow; writes and archives a property.
lease Android flow; writes a lease.
document upload/download Android flow; uploads to the production private bucket.
messaging Android flow with two linked sessions.
notification Android flow; needs a delivered notification.
calendar Android flow; writes a shared event.
rent schedule Android flow; generates a tenant-visible rent request.
payment proof Android flow; writes a receipt and an attachment.
hosted rent payment Android flow plus a Stripe test payment against the live catalog.
subscription purchase/restore Needs a Play store test account and a published track.
Stripe Connect Needs a Stripe test connected account completed interactively.
handover Android flow with two roles and immutable state transitions.
deposit/final settlement Android flow; writes to the deposit ledger.
data export Produces an archive of a real account's data.
problem report Android flow plus an authenticated admin session.
admin authentication Needs a fresh allowlisted admin and a TOTP enrolment in production.
admin accounts Needs an authenticated admin, and suspends a real account.
admin activation funnel Product Outcomes replaces the old funnel. Requires deployed integration comparison, dedicated query-identity/billing prerequisites, and separately authorized manual production verification.
webhook recovery Needs a dead Stripe event to reveal and replay.
push Needs a device with a registered FCM token. The delivery path itself is provisioned.
analytics Needs a device emitting activation telemetry.
alerts New Relic account 8573192 (EU) has 30 integration and 39 production conditions, environment-specific Discord workflows, live backend/host/cloud telemetry and verified delivery records. CloudWatch logs remain for corroboration; legacy metric alarms were retired. See the current observability runbook.