Craft

File type 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 checks a world's file types, the character type first, against improving file types. It follows how an audit works: start from the world check, read, report, change nothing.

What to use from the world check

  • Findings about the character type and other types.
  • Numbers: fields on the character type, computed fields, a typical and the largest character.
  • Samples: the characters.

What to read, in order

  1. Improving file types and key fields.
  2. The character type and the three sampled characters, whole.
  3. One more type, when the check flags it heavily.
  4. The rules and scripts that read the sheet: the parts of the GM instructions that name its fields, pools or stats, and the code of the scripts that change them. A field nothing reads, a rule that names a field the sheet lacks and a script that writes the wrong field all show only here.

With no characters to sample, work a new character through from the creation flow, and check that its picks lead to files that exist.

The character type

  • Is the type more complicated than the game needs? Count the fields a turn would actually read against the ones it wouldn't.
  • Are the key fields the few the story leans on: who someone is, how they look and sound, the handful of numbers a turn reads and changes?
  • What in a sheet says the same thing twice, sits empty, or is bookkeeping the GM shouldn't read?
  • Do the computed fields work out right? Read each expression against its field's description and work one sampled character through by hand. A sheet that computes a wrong number is wrong on every turn that reads it. Give the character, the field, what it shows and what it should show.
  • Numbered fields and typed-in totals: which should be one list, or worked out.
  • Before calling a field dead, find what reads it. A world's characters are mostly NPCs, so the ring slots, spell lists and second-class fields a player's character fills in play sit empty in nearly every file. A field is dead only when nothing fills it and nothing reads it: no computed field of this type or another, no script, no rule, no layout, no creation flow. The check's dead fields already leave out what code or a rule reads by name.
  • Does the sheet point at things that exist? Every kind of file a reference field or an expression names should exist and have files, and a character's stored links should lead to a file. A sheet that links to nothing loses what that file would have given it.
  • Before calling a stored value broken, read the computed field that uses it: some match a plain name against the inventory on purpose.

Another type

The same questions, for a type other than the character's that the check flags for dead fields, numbered fields or very large files. Skip it when nothing is flagged.

What the report covers

Wrong computed numbers with a worked example, values over their maximum, links to files that don't exist, rules and scripts that name fields the sheet doesn't have, the key fields, numbered fields and fields nobody fills or reads. A sheet's size is Medium at most.