MamNajem readiness status¶
Last reconciled: 2026-08-03.
This page separates completed greenfield migration evidence from remaining launch and acceptance work. It is a repository documentation reconciliation, not live AWS, GitLab, Stripe, Google Play, New Relic, or production verification.
Summary¶
The hard migration from the donor platform to MamNajem is documented as complete. The remaining work is launch readiness: acceptance reruns, app-link association publication, legal review, pilot validation, and production release signoff.
Do not use this page as proof that a live external system is healthy today. Before any completion or release claim, refresh the relevant live evidence and record the command, timestamp, environment, and candidate SHA.
Completed Migration Evidence¶
- Repository history copy, recovery staging, governance verification, donor archival, and final fresh-clone gates are recorded in MamNajem repository copy evidence.
- Migration design, execution-prompt, bootstrap evidence, source ledgers, and provider-access records were sealed outside all six repositories and source copies were removed, as recorded in MamNajem migration preservation.
- Current docs should treat donor identifiers as allowed only in Git history, sealed archives, and explicit sanitized evidence records.
Remaining Non-Migration Gates¶
| Gate | Current status | Next action |
|---|---|---|
| Acceptance matrix reruns | Open | Re-run or supersede the dated verdicts in MamNajem feature-parity matrix for the candidate being accepted. |
| OpenAPI deployed check | Decision required | Choose either authenticated operator exposure for OpenAPI or build-artifact verification plus deployed health-only smoke. Do not enable public /v3/api-docs accidentally. |
| Email acceptance row | Reconciliation required | The July 29 matrix verdict records a failed candidate check, while pre-release gate docs mark launch-scope integration email as passed from June evidence. Re-run live email acceptance or replace the row with explicit scoped evidence. |
| App-link associations | Pending external mobile signing contract | Remove MAMNAJEM_ASSOCIATIONS_PENDING only after MAMNAJEM_STAGING_CLIENT_CONTRACT_FILE and MAMNAJEM_STAGING_CLIENT_CONTRACT_SHA256 exist, then redeploy web frontend association files. |
| Legal review | Open | Complete Polish counsel review, record answers in Legal review response log, merge required changes, and update the charter gate only from evidence. |
| Pilot completion | Open | Run the first pilot onboarding batch, pricing test, support review, scorecard, and go/narrow/stop memo from real landlord workflows. |
| Production release signoff | Not satisfied by migration | Promote production only after the normal release signoff checks pass for the exact integration SHA. |
| Live-state refresh | Required before claims | Re-query current deployed heads, CI, health, email, app links, store state, New Relic, and alarms before declaring any release or external dependency complete. |
Local Workspace Caveat¶
The local polyrepo can contain unrelated in-progress work. A pre-cleanup check on
2026-08-03 showed mobile-frontend on android-espresso-e2e with many local
changes, and the canonical docs checkout had an untracked audits/ directory.
Those files are not migration evidence and were not modified by this cleanup.
Re-run git status --short --branch in each repository before staging,
releasing, or reporting a clean workspace.
Next Verification Pass¶
Use this order for the next evidence-producing pass:
- Confirm each repository branch and remote head.
- Re-run the docs validators and build.
- Resolve the OpenAPI acceptance contract.
- Re-run email acceptance with current SES and workflow evidence.
- Verify app-link association prerequisites after the first Play upload.
- Complete legal review and pilot evidence gates before public launch.