Governance
Authority is determined by completed controls, not version numbers.
Rihuum publishes the present document status so directors, teams, partners and customers can distinguish operative authority from approval intent, rectification work and future architecture.
Master Blueprint v3.6 and Digital Ecosystem Master Architecture v2.7 remain the operative top-level editions. Records dated 2 August 2026 show unanimous Board approval intent for a v5.1/v4.1 bundle, but all seven Schedule 1 hashes mismatch the available files. A Board-approved RIL-BR-ADOPT-051-R1 execution package was prepared on 3 August 2026, but formal execution and independent C03 verification remain pending and Controlled Commencement has not been issued. The current v5.1/v4.1 files are therefore rectification candidates—not operative authority or proof of implementation.
Authority register
The operative and pending records.
No download on this page is presented as a current controlled master. Authorised controlled copies must be obtained through the Company Secretary's document-control process.
| Record | Current status | Effect |
|---|---|---|
| Master Blueprint v3.6 | Operative | Remains the top-level corporate blueprint until a properly executed and verified superseding instrument takes effect. |
| Digital Ecosystem Master Architecture v2.7 | Operative | Remains the top-level digital ecosystem architecture under the same authority boundary. |
| Master Blueprint v5.1 and Architecture v4.1 bundle | Rectification candidates | Board approval intent is recorded, but the available seven files do not match the Schedule 1 hashes and cannot establish the approved exact-artifact baseline. |
| RIL-BR-ADOPT-051-R1 execution package | Prepared; unsigned | Prepared on 3 August 2026. It does not operate as an executed Board instrument until genuine execution is complete. |
| Independent C03 verification | Pending | No completed independent verification record currently establishes that all seven files match approved SHA-256 values. |
| Controlled Commencement | Not issued | The v5.1/v4.1 candidates have not commenced and do not supersede v3.6/v2.7. |
Completion controls
What must happen before authority changes.
These steps protect the company from treating an unsigned or mismatched bundle as an operative Board record.
- 01Independent evidence required
Execute the R1 package
Obtain genuine signatures or traceable electronic consents from the authorised directors and Company Secretary, with true signing dates.
- 02Independent evidence required
Reconcile the seven-file baseline
Generate approved SHA-256 values from the controlled source and correct the Schedule 1 record.
- 03Independent evidence required
Complete independent C03 verification
Record the verifier, tool and version, date, time zone, controlled source, custody reference and Company Secretary acknowledgement.
- 04Independent evidence required
Issue Controlled Commencement
Only after execution and verification may the authority record identify any new operative editions and their precise supersession effect.
Interpretation standard
Architecture is not implementation evidence.
A blueprint may define a target state, but it does not prove that software, integrations, security controls, payment providers, AI agents or client environments are operational.
Each product and service must retain its own release record, acceptance evidence, credentials, operating owner and support boundary. Public product status is recorded separately on the work and technology sites.
Request an authoritative controlled copy.
For governance, audit or transaction use, state the document, purpose and required date. The public website should not be treated as the controlled repository.