24C/ Machine Readable Governance: Theory, Code, and the Future

From IIW

Machine Readable Governance: Theory, Code, and the Future

Thursday 24C

Convener: Mike Ebert, Simon Nazarenko

Notes-taker(s):  Mike Ebert

Tags for the session - technology discussed/ideas considered:

Machine readable governance, trust registries, roots of trust, workflows

Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps

Presentation slide deck:


Machine Readable Governance Definitions

Goals of Machine Readable Governance

  • Provide information about roots of trust

  • Organize the ecosystem by codifying rules, conventions, and standards

  • Decouple (some) business logic from code

  • Provide flexibility to accommodate change and avoid having to frequently re-release or update agents

Start with defining the ecosystem’s assets, actions, and authorizations.

Components of Machine Readable Governance

  • Governance files

  • Schemas

  • Presentation definitions

  • Interaction documents

Governance Files

  • Allow a jurisdiction to act with sovereignty

  • Can be cached to improve offline operations

  • Can be hand edited or generated

  • We have written code that responds to governance when present but functions with it

  • Agents can utilize governance but aren’t bound to it (but caveat emptor!)

Meta Data







Presentation Definitions

Used for verification (cryptographic) and validation (business logic)


Future: Workflows

Future: Composability

Future: Discoverability

Future: Trust Registries and Machine Readable Governance