MYNT REGISTER · MYNTGROUP · PROJECT DOCUMENTATION

Production readiness checklist

15 October 2026 · Product documentation · Version 2

This checklist summarises the controls and evidence required to evaluate production readiness. Test data, operating scope, evidence and acceptance authority must be defined before live operation. No item is marked accepted by this presentation.

Gate 1 · Responsibilities and service perimeter

• Identify the issuer, registrar, technology provider and any market, payment or custody operator.
• Record who owns the register, authorises changes, handles exceptions and responds to incidents.
• Complete the applicable legal, FCA / MLR and jurisdiction assessment; record required permissions before real services begin.
• Document data protection, operational scope, acceptance and continuity requirements.

Gate 2 · Verified source and lossless migration

• Select one company and retain its verified source register and authority to migrate.
• Agree share classes, rights, quantities, nominal values and relevant paid / unpaid amounts.
• Preserve member identities, addresses, membership dates, joint holdings and relevant historical entries.
• Preview and approve the import, reconcile issued capital and prove rollback or recovery without data loss.

Gate 3 · Access and separation

• Test admin, registrar, company and shareholder permissions against agreed roles.
• Prove that a user cannot view or change another company’s records without authorisation.
• Test revocation, session controls, reviewer separation and privileged actions.
• Record the result and evidence of both allowed and denied operations.

Gate 4 · Register operations and accounting

• New issues increase capital only after the required authority, supporting documents and approval.
• Transfers update the entitled holders without changing issued capital; check signatures, consideration and other agreed requirements.
• Repeated or simultaneous requests do not issue or transfer twice, lose a change or create an inconsistent register.
• Record before / after state, user, time, source authority and approved exception handling.

Gate 5 · Evidence, lifecycle and audit

• Store and link supporting evidence rather than relying on free-text references alone.
• Test joint ownership, changes of name or address, cessation of membership and certificate workflows within the agreed scope.
• Protect audit records; represent corrections as traceable changes.
• Agree identity-review requirements, retention and inspection procedures appropriate to the real service.

Gate 6 · Outputs, recovery and sign-off

• Reconcile printed records and complete exports against the stored register, preserving required fields and numeric precision.
• Test filing and inspection workflows where included, with submission and receipt records.
• Restore backups in a test environment and document incident response, handover and exit.
• Obtain named acceptance of the agreed electronic register before assessing an optional tokenisation phase.

Optional tokenisation / trading phase

Agree instrument rights, issuer authority, the service perimeter and the chosen network first. Then test custody, key management, contract validation, allowlists, transfer restrictions, payment settlement, reconciliation and recovery appropriate to that scope. A browser simulation does not satisfy these acceptance tests.

Acceptance record

Read the original Neville / FCA requirements review for its dated sources and distinction between legal requirements, service benchmarks and proposed technical controls.