MANSOQ Knowledge
← Knowledge library

Security & governance

Evaluate enterprise go-live readiness

Use the evidence-backed setup worklist before treating a configuration package as production-ready.

Current source · source reviewed · 7 min read

Before you begin

1. Run the non-mutating readiness check

Use enterprise-go-live-readiness for the latest or selected immutable package. Read the returned blockers and setup_checklist before any certification action.

2. Complete setup evidence

Verify organizations, roles, delegation, contracts, products, issued policies, classes, benefits, tariffs, assignments, member coverage and the applicable source/approval chain.

3. Complete external and financial proof

Review production NPHIES routes and certification, certificate state, taxpayer/unit ZATCA qualification, accounting posting evidence and settlement controls.

4. Complete deployment and operational proof

Attach actual deployment, UAT and monitoring evidence required by the readiness service. Software route existence and successful model tests do not provide those deployment facts.

5. Certify only after all blockers are resolved

Use certify-enterprise-go-live only after readiness is green. It creates an immutable enterprise certificate and refuses unresolved blockers.

Source audit versus deployment certification

This knowledge base describes inspected source. It does not certify the live installation. Some older operator/checklist prose reflects an earlier integration state; current code and the actual readiness response must be checked together.

Operational acceptance

Exercise a witnessed encounter-to-cash workflow, including failure and recovery, in the appropriate environment. A table populated with draft rows cannot substitute for this evidence.

Troubleshooting

Readiness remains red after completing forms

Follow the checklist’s named owner, required evidence and corrective action. Check expiry, approval, package pinning and external proof rather than entering placeholder values.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.