Skip to content

Welcome — you've just been handed a ticket

You're new to Axonis, or new to how we build here, and someone has just handed you a ticket — "add X to the Lens", "fix the gap in trained-model lifecycle", "ship this by Friday". Your instinct is to open the code and start editing. On this platform, that instinct is the one thing this tutorial asks you to unlearn.

The spec-first model

Axonis development runs on a simple inversion: the specs describe the golden state — what the system should be — and the code catches up. A spec here is not documentation written after the fact; it is the authoritative, reviewable statement of intended behavior, and "implementing" means closing the measured gap between what a spec mandates and what the code does.

That inversion has practical consequences you'll feel on day one:

  • Every piece of work starts by finding (or writing) the spec section that governs it.
  • "What's missing?" is a tool-assisted question (/sdd-spec-gap), not an opinion.
  • Code review asks "does this match the mandate?" before "is this good code?"
  • When code and spec disagree, the spec wins — or the spec gets formally amended. Never a silent drift.

The whole process — the skills, the gates, the critics, the staging model — exists to make that loop cheap and honest. The reference description lives in the SDD decision log; this tutorial is the narrative version, and it ends with a real feature followed end-to-end.

The map

  1. The spec corpus — what specs exist, how they're addressed, how to find yours.
  2. The three entry shapes — classifying the ticket in your hand.
  3. Staging and slugs — where in-flight work lives and why canonical specs never change mid-flight.
  4. The pipeline — plan to ship, and the adversarial critics in between.
  5. A worked example — one real feature, end-to-end, mess included.

What you can do now

  • Say the model in one sentence: specs are the golden state; code catches up; gaps are measured, not guessed.
  • Resist the open-the-code instinct on your ticket until you've read the spec corpus page.