Operations¶
Last audited: 2026-05-30.
Current operator-facing documentation for MamNajem application ownership, deployments, observability, incident response, and payment webhook handling.
- MamNajem readiness status: current split between completed migration evidence and remaining launch-readiness gates.
- MamNajem repository copy evidence: checksummed history-copy, recovery-archive, governance, and donor-archive proof.
- MamNajem source commit ledger: frozen donor commits, trees, refs, and object inventories used for the migration.
- MamNajem naming contract: canonical machine-readable brand, repository, domain, provider, and protocol names.
- Application map: repository boundaries, runtime responsibilities, external services, and important operational ownership.
- Deployments: branch policy, CI/CD flows, mobile release paths, environment URLs, and release verification.
- Incident triage: first-response checklist for backend, mobile, billing, notifications, and production support issues.
- Observability and alerts: request tracing IDs, New Relic, CloudWatch, alert routing, important alarm names, and investigation flow.
- New Relic product dashboard review brief: application context, selected shared product/retention definitions, implemented reporting sources, publication blockers, and independent review boundaries.
- Product Outcomes reporting: configuration, private account/identity prerequisites, immutable results, publication verification, warnings, and failure handling.
- Payment webhooks: Stripe webhook behavior, supported events, state changes, and replay considerations.
- Not the right fit referral script: support script for >25-unit, agency, team, accountant, and other out-of-scope inbound leads.