Case Governance and Inclusion Criteria

2 min read

Purpose

This document defines what constitutes a case study within the Institutional Experiments program.

It exists to:

  • maintain methodological consistency,
  • prevent ad hoc case proliferation,
  • and clarify publication boundaries.

Not all explored scenarios are published as cases.


What Qualifies as a Case

A scenario may be included as a case study only if it satisfies all of the following conditions.

1. Situated Context

The case must be grounded in a concrete, describable context involving real participants, systems, or interactions.

Abstract designs, hypothetical systems, or purely speculative futures do not qualify.


2. Institutional Friction

The case must surface tension, ambiguity, or breakdown in one or more institutional dimensions, such as:

  • identity,
  • authorization,
  • accountability,
  • delegation,
  • or trust formation.

The friction must arise from ordinary operation rather than exceptional failure.


3. Conceptual Pressure

The case must meaningfully challenge or stress-test at least one core Institute concept (e.g. AI Workforce Identity, Language Governance).

Cases that merely illustrate concepts without exposing limits are excluded.


4. Observability Without Intervention

The case must allow observation without requiring system redesign, policy change, or behavioral instruction.

If the scenario only becomes interesting after intervention, it is not a case.


What Is Explicitly Not a Case

The following are intentionally excluded:

  • product feature specifications,
  • implementation playbooks,
  • policy proposals,
  • advocacy narratives,
  • success stories or promotional examples.

Cases are diagnostic instruments, not solution showcases.


Publication Levels

Cases are managed under three publication states.

Published Case Studies

Fully written cases that:

  • are conservative in scope,
  • omit operational detail,
  • and are suitable for public reference.

Active Case Series

Cases under active investigation that:

  • have defined scope and title,
  • may be partially written,
  • and may be published incrementally.

Planned Case Studies

Cases acknowledged as relevant but:

  • intentionally unpublished,
  • sensitive in nature,
  • or dependent on further evidence.

Listing a planned case signals research intent, not commitment.


Case Lifecycle

Cases may evolve through the following stages:

  1. Identified
  2. Framed
  3. Observed
  4. Written
  5. Published
  6. Re-evaluated

Cases may be revised, merged, or retired as research progresses.


Revision and Governance

This document may be updated to reflect methodological refinement. Revisions are documented to preserve interpretability across time.

The goal of case governance is clarity, not exhaustiveness.