aitp-derivation-discipline

Use when AITP needs to write or review a derivation so the result reads like a serious theoretical-physics argument rather than polished prose or a loose sketch.

AITP Derivation Discipline

Environment gate (mandatory first step)

  • Confirm the topic is already inside AITP.
  • Read the current L3 derivation records and any comparison receipts before writing a new derivation spine.

When to use

  • A derivation needs to be written, repaired, or audited.
  • The current notebook sounds too literary and not stepwise enough.
  • A result risks hiding assumptions, factors, or caveats.

Workflow

Write derivations in this order:

  1. Goal
  2. Starting point
  3. Key steps
  4. Consistency checks
  5. Where the caveat enters
  6. What is and is not established

Hard rules

  • A derivation record is AI-authored provisional reasoning, not truth by itself.
  • Do not skip factor, sign, convention, or regime checks.
  • If a cited step is missing, say so and queue return to L0 rather than smoothing it away.