Learn GovernanceOS

Choose your role

• Institution administrator
• CRO
• Model owner
• Validator
• Compliance lead
• Practitioner
• Examiner

Each step opens the screen in the demo, on fictional institutions, so you practice without touching real records.

Finishing a path writes a completion record to your account. It is not a certification and makes no claim about your institution.

1. Claim the tenant
2. Set the regime profile
3. Invite members and set roles
4. Choose which assistants may read
5. Rehearse the exit: export both forms and verify

1. Sign a gate with a reason
2. See what an examiner sees

1. Register a system and its owner
2. Attach evidence that existed at the decision
3. Answer a condition on an approval

1. Record the G2 report and what was not examined
2. Record dissent as a record of its own
3. Check that your report reached the approver unchanged

1. Build an evidence pack, adverse records included
2. Issue a time-boxed examiner key
3. Follow regulation rows and their checked dates

1. Sign up and request your access code
2. Import a client's register
3. Bring files: upload or GitHub
4. Draft findings for the client
5. Hand the workspace over

1. Open your key and read its scope
2. Ask a question and check how it was read
3. Verify a pack offline, and see a failure
4. Know what verification does not prove

Further reading

Every record field cites the published specification it comes from. The specifications are listed on About, under Intellectual property. For help at any step, see Help and support.