For your role

Research

Ground investigations in the glossary anchors the standards use, so findings can be cited back into them.

Where to start

Three moves, in order

Each ends somewhere you can act rather than somewhere you can read.

  1. Anchor the question in the doctrine

    State the claim as one of the twelve laws, so findings cite something a standard binds rather than a mood.

    Read the laws

  2. Read why the laws hold

    The theory essays carry the argument: dependence, standing, capture, absorption, and the refusals between capability and authority.

    Open theory

  3. Bring a case or a dataset

    Field studies, incident analyses, and protocols can enter the agenda through the participation intake.

    Open Participate

What to attend to

The parts of the method that bear on your work

Not everything here is yours. These are the parts that are.

  • Align research questions with glossary and standard definitions.
  • Publish protocols and artifacts that feed validators and mechanisms.
  • Coordinate with the Institute to share datasets and findings.
  • Research agenda — Current agendas, focus areas, and publications.
  • Glossary — Canonical definitions for research protocols.
  • Participate — Submit findings and coordinate peer review.
  • Field notes — Published case notes tied to standards.

First moves

  1. Select glossary anchors for your research framing and cite them consistently.
  2. Share protocol drafts through the participation intake.
  3. Publish bridge artifacts that translate findings into mechanisms.

Other roles

If that was not you

Seven audiences, one page each. Picking the wrong one costs a click, not a detour.

  • Engineering — You build or operate the system that makes the decision.
  • Policy and compliance — You write the rules the system has to satisfy, or prove to a regulator that it does.
  • Audit and assurance — You verify someone else's claims from the evidence their system emits.
  • Operations — You run the appeals, the incident response, or the queues where the system's errors land.
  • Design — You shape the interface where a person meets the decision.
  • Executive — You decide whether to deploy, and you carry the liability when it goes wrong.

Or go back to Start, which asks the same question with all seven answers on one screen.