Milestone 2: Your rules and your question

WarningUnder development

This milestone chapter is part of a book in active development and has not yet been through the author’s review. Content may change as the review advances.

Open In Colab

This chapter closes Studio 2: Set your rules, shape your question. Its lessons each ended at It is your turn; what you wrote there arrives here as working material, and this is where the pieces become one artifact you can defend.

What this milestone produces. Your working agreement (an ownership statement, your working rules, your opened AI Research Ledger, your delegation map, and the red-flag screen of your chosen problem) and your question, formally declared: objective, units, outcomes and conditions, kind and reach, and a provisional claim boundary.

What you bring

You also carry forward the last milestone’s artifact: Milestone 1: Your curiosity, committed. This one builds on it, and the chain assumes it is versioned and filed.

Check you are carrying each of these before you start. If one is missing, go back and work that lesson’s It is your turn first; the practice below assumes it.

The practice

  1. Write your ownership statement: the decisions that stay yours no matter how good the tool gets — the choice of question first among them.
  2. Write your working rules: what you will delegate, what you will always verify, and how you will record both. Mark the declaration work on the map: candidate wordings are delegable; kind, reach, and the boundary never are.
  3. Open your AI Research Ledger and give its first rows to the exchanges you have already run, the Studio 1 brainstorm included.
  4. Build and run the red-flag screen on your chosen problem: is it answerable, is it yours to ask, and could you defend attempting it.
  5. Assemble your declaration from the last two lessons: the lead question classified by kind and reach, the field card (objective, unit, outcome, conditions), and the chosen wording with every change accounted for.
  6. Write your provisional claim boundary beside it: the sentence you hope to defend, the stronger sentence you will not be able to, and the uncertainty-and-limitations line any answer will have to carry.
  7. Read the two artifacts against each other: every never-delegate line in the agreement must cover a decision the declaration actually made. Where one names a rule the other ignored, fix the weaker document.

A version, not a pass

Your milestone artifact is a dated, numbered version with the reason for the version attached. When later evidence changes it, you write the next version rather than editing the last one, because the sequence of changes is itself part of your research record.

The four rails, here

Four concerns cross every studio in this book. At this milestone they take these specific forms.

  • Ethics, permissions, and data exposure. The red-flag screen runs here, and a problem that studies people leaves this studio with that fact attached.
  • Evidence, provenance, and reproducibility. Nothing here is settled until Studio 3 checks it against what is already known.
  • AI activity, verification, and human decisions. The ledger opens here and every earlier exchange gets its row; from now on, no delegation goes unrecorded.
  • Uncertainty, claim boundary, and revision history. A question with no recognizable answer cannot carry uncertainty; fix the question before you leave.

Where this milestone sits

You arrived carrying Milestone 1: Your curiosity, committed. Milestone 3 holds the declared question up against what is already known, and it will usually send back a sharper version. The chain ends at Milestone 12: Your release and next cycle, where you decide whether your finished research artifact leaves your hands.

What sends you back

Studio 3 almost always sends the question back here for a sharper version, and any change in your tools, your data source, or your collaborators reopens the agreement.

How this milestone is assessed

Each row scores 0, 1, or 2. 12 points total.

# Criterion 0 1 2
1 The milestone artifact exists in full, specific to your own project absent, or generic text that would fit any project present but incomplete, or specific in some parts and generic in others complete and unmistakably about your project
2 The milestone is written as a dated, numbered version with its reason no version, or a version with no reason given versioned, but the reason is decorative rather than an account of what changed versioned with a reason a reader could use to reconstruct your thinking
3 Every judgment in the artifact is defended by you, not asserted by a tool conclusions appear with no reasoning, or reproduce a tool’s wording reasoning present but thin where the decision was hardest each judgment carries a reason you could defend under questioning
4 The four rails are carried in the form this studio requires one or more rails absent where this studio required them all rails present but one is nominal every rail addressed in the form this studio requires
5 The milestone’s own product is present and defensible: Your working agreement (responsibility statement, working rules, opened AI Research Ledger, delegation map, and the red-flag screen of your chosen problem) and your question, formally declared: objective, units, outcomes and conditions, kind and reach, and a provisional claim boundary the milestone’s own product is missing present but would not survive a careful question present and defensible as stated
6 The declared question is fixed by its own words: kind and reach match the sentence, double-barrels are split, and the claim boundary states the defensible sentence, the forbidden sentence, and the uncertainty-and-limitations line the answer must carry no declaration, or a kind or reach the question’s words do not fix declared, but one term is loose enough that a stranger could not say what gets recorded or who the answer is about declared so a stranger could restate unit, record, and audience, with both boundary sentences present

Your workbook

Open the workbook with the badge above. It walks these steps with a cell for each one, ends by writing your milestone version with its reason, and adds the rows this studio contributes to your AI Research Ledger and your Research Dossier.

opens in a new tab