Craft

Instruction audit

Note

Written for AI agents. Orbit and coding agents follow this page when they work on your world. You don't need it to use Craft, but it shows how an agent will approach the job.

This audit reads every instruction the GM is given and checks each against writing good instructions. It follows how an audit works: start from the world check, read, report, change nothing.

One reader reads all of it

A world's always-on rules, situational rules, procedures, trackers and scripts are one design in pieces. A rest rule hands off to a script, a tracker's rules repeat a procedure's step, two rules fire on the same moment and disagree. None of that shows to a reader who holds only one piece. So this audit has no readers: you read every part yourself, in full, and judge them together.

What to use from the world check

  • Findings about instructions, procedures, trackers and scripts.
  • Numbers: the always-on size, how many rules of each kind, script candidates, how many scripts.
  • Parts: all of them, every numbered part included.

Lines in the parts headed "In the GM's prompt:" and "Checked after each reply:" are written by Craft from a tracker's settings. The creator can't edit them: a fix changes the tracker's "changes when" or its rules instead.

What to read, in order

  1. Writing good instructions, triggers, procedures and scripts, in one step.
  2. Every part the check lists, whole, in as few steps as they fit. Read them all before judging any.
  3. Only then, what a question below sends you to: a script's code when a rule, option or tracker depends on what it writes, the character type for a field a rule names, a folder a rule sends the GM to.

Across the parts

Ask these first. They are what reading everything together is for.

  • What fires together? Take the moments the world plays most (a fight, a rest, a spell cast, a sale, a level gained) and list every rule, procedure, tracker rule and script that speaks to each. Where they repeat each other, say which one should hold it. Where they disagree, quote both.
  • Who writes each piece of state? Hit points, a pool, an effect, a tracker's row. If a script keeps it, no rule, procedure or tracker should tell the GM to write it by hand, and the other way round.
  • Does every name point at something? A script a rule says to run, a tracker a procedure names, a field, a pool, a class, an item, and the files a rule tells the GM to read: a kind of file with no files is a missing name. Look each up among the scripts and trackers you read, and search for the rest. A deleted script is one the world doesn't have. Naming a tool the GM has is fine.
  • How many trackers can be in the state at once? The current state holds at most 10. Count the ones that start with the game and the most that one moment (a fight) starts.
  • Is each rule the right kind? Exact steps with no judgment are a script. Several turns with judgment are a procedure. One moment is a situational rule. A count that lasts is a tracker.

Always on

  • Would each of the world's own always-on rules apply on most turns? The premise and the narration style do. Rules for one kind of moment don't: unless the game is nearly all combat, combat rules here are a finding. Say what each such rule should become.
  • Does any rule make the GM read, check or audit on every turn? A file to open before each reply, a list to check each reply against, fields to look up for everyone in the scene. Quote it.
  • Is any always-on rule doing bookkeeping? Counting, subtracting, updating a sheet. That is a tracker's or a script's job.
  • Player options: does one of the world's own rules override a choice, or repeat one? An option's default choice shows in the always-on text because it is picked. That is the option working.
  • Craft's defaults are in every world and are not the world's copies. Leave them out unless the world wrote a second rule that says the same thing.

Situational

  • Is each one "when X, do Y"? A trigger a story moment can show, never a number on a sheet, with the ruling first.
  • Which are exact steps or bookkeeping? Anything that changes the game's state in one turn, a table to roll on, a sum to work out. These are script candidates: list them.
  • Which are several moments in one rule?

Procedures, trackers, scripts

  • Is each procedure the rough shape of something that takes several turns, with room for the GM's judgment? One with no judgment in it is a script. One short enough for a single moment is a situational rule.
  • Does each procedure's title name its moment? The GM picks by title.
  • Does each tracker say when it changes and what its ends mean, and nothing more (trackers)?
  • Scripts: does each name and description say what it does and when to use it? Open a script's code when a rule, option or tracker depends on what it writes, or the check flagged it for reading too much. A script's size is not an issue.

What the report covers

Only the GM's instructions: rules, procedures, trackers and scripts. Leave the check's findings about maps, file types and game starts to their own audits.