Surfaces and environments for managing research processes, operating knowledge systems, and organising workflows.

  • Control interfaces are the tools and environments users need to run knowledge systems and technologies. They are organised around how work actually moves: setting up a task, gathering and triaging sources, designing and testing prototypes, assessing them, authenticating them, and certifying them.

  • Governance is usually designed for the people who audit work rather than the people who do it. The result is controls that exist in the documentation and not in practice, because practitioners find them slower than the alternative and route around them. Work moves through recognisable stages: setting up a task, gathering and triaging sources, designing and testing, assessing, authenticating, certifying. Most tooling supports some of these while leaving the transitions between them unrecorded.

  • 1. Where in a workflow does an operator actually retain the ability to intervene, and does the interface place the control at that point?

  • 2. What does a recorded decision cost in time, and at what threshold does that cost change behaviour?

  • 3. Can one record structure serve a sole practitioner and a large team without being rebuilt for each?

  • 4. What makes a practitioner willing to rely on work certified by someone else?

Previous

Epistemic Assurance