L-07 · Method

Designing a control question set

Primary intent
Create a control set that detects change without drifting with every observation window.
Evidence state
Source-grounded reference
Review owner
Matthias Ramahi · independent review not claimed
Last reviewed
2026-08-22
Direct answer

Control question set

A control question set is a versioned group of stable questions repeated under comparable conditions across observation windows. It should cover the declared question classes, avoid unstable wording, record expected answer constraints, and change only through an explicit version and comparability decision.

Use this method when a study needs a fixed reference series rather than a rotating collection of topical prompts.

Controls need a job

A control set is not a list of popular queries. Its job is to provide repeated observation units that make change interpretable. Each question should connect to a declared class or stress condition in the protocol.

Include enough variety to expose the behavior under study, but keep the set small enough to repeat reliably within the cost ceiling. Unmaintainable controls are not controls.

Select for stability and diagnostic value

Prefer wording that has one clear task and does not depend on a private personal context. Flag time-sensitive questions, location-sensitive questions and questions whose correct answer changes. These can be useful, but they need their own interpretation.

Record why each question exists, which class it represents and what would make it invalid. This protects the set from becoming an unexplained prompt collection.

  • Stable question ID and exact submitted text.
  • Question class and inclusion rationale.
  • Locale and route requirements.
  • Volatility or safety flag.
  • Retirement condition.

Freeze text and conditions together

The text alone is not the full control. Surface, route, locale, session rule, timing and available configuration belong to the protocol version. A stable prompt sent through a different route may be a different observation unit.

Hash or otherwise identify the frozen control file. Publish the version and effective date. Where the raw question cannot be shared, publish enough metadata to explain the limitation without inventing reproducibility.

Change through retirement and replacement

Do not edit a question in place. Retire the old ID with a reason and add a new ID. Decide whether the new question begins a new series or can be analyzed only as an adjacent exploratory track.

Periodic review is still necessary. A formerly stable question may become ambiguous, unsafe, obsolete or impossible to run under changed provider terms. Version control preserves the history without forcing a broken control to continue forever.

S

Source notes

These sources support the definitions, standards or project boundaries named in this reference. They do not prove that a public observation dataset exists.

  1. portfolio-dossier
    Canonical ai-fanout.com domain dossier

    Confirmed ownership, accepted public Evidence Lab purpose, named Research Owner, indexable website launch and separately gated provider research.

    Owner record
  2. w3c-prov-o
    PROV-O: The PROV Ontology

    Provides provenance concepts for entities, activities, agents, derivations, sources and versions.

    Open
  3. rfc-3339
    RFC 3339: Date and Time on the Internet

    Supports an interoperable timestamp representation tied to UTC.

    Open
  4. fair-principles
    The FAIR Data Principles

    Supports reusable research data with metadata, provenance and clear usage licenses.

    Open