Choose your path
Four kinds of people use the suite, and they arrive with different questions. Each path below says what you will do with the apps, which pages to read, and in what order. Most people fit one; a fractional GC who also installs the apps for clients reads two.
Practitioner
You run engagements for clients and the apps are your method, record and output in one place. An engagement is a set of sessions with the client's people in named roles; the app says at each step who proposes, who records and who reviews, refuses anything outside a role, and generates the outputs (statement, policy outline, board minute, action list, register, findings) as Word documents marked draft until the right person signs them off.
Board member or executive
You take part in an engagement someone else facilitates the record shows who proposed, who decided and who reviewed, and nobody can be said to have done another's part.
Operator
You install and run the apps: on your own Cloudflare account, for your own organisation or as a practitioner's firm, or on the Triodian account as a Triodian administrator. Each app is one Cloudflare Worker with its own D1 database, behind Cloudflare Access for sign-in; the apps of one deployment share an identity database and call each other over service bindings, so there is no public API between them and no secret to create or rotate for the links.
Contributor
Every repository is public under github.com/Triodian, Apache 2.0, and takes issues and pull requests. The apps share one shape, so what you learn in one carries to the others, and most changes people want to make are to wording or rules, which live in content files rather than code.