Documentation

Jidoka builds quality into the instructions humans and agents share. You put every file on one layer, then let a check stop the line when a layer drifts. Each job below covers one part of that work. Start with the adoption job. Then pick the job you have in front of you now.

Adopt the Standard (Teams Using Agents)

Adopt Jidoka in Your Repository

Install the Jidoka skill pack, lay out the root instruction layers, wire the checks into your check command and CI, then watch the line stop on a deliberate breach.

Give Every Instruction One Owning Layer (Teams Using Agents)

Put Your Instructions on One Layered Architecture

Give every instruction file one owning question, one load moment, and one budget, so a bad agent run points at exactly one file instead of at a pile of prose.

Author or Repair One Instruction Layer

Write or fix one layer at a time. Name the layer that owns a piece of text, move misplaced text, and bring an over-budget layer back under its cap without a loss of meaning.

Write a Checklist That Verifies Instead of Teaches

Place a READ-DO entry gate and a DO-CONFIRM exit gate at real pause points. Keep every item to one binary check. Tag both gates so one search finds every gate in your repository.

Write Jobs To Be Done Entries

Write a job entry that traces an instruction layer to the progress a persona seeks in a real moment. The page covers the entry structure, the Big Hire and Little Hire split, and the four forces. It also covers the Fired When clause and the tag that makes every job searchable.

Catch Drift Before It Ships (Teams Using Agents)

Stop the Line on Instruction Drift

Wire the jidoka checks into your check script and your CI workflow. Read a finding. Route each finding to the fix that owns it. The line stops where the defect appears.

Enforce Your Repository's Own Invariants

Write a declarative rule module so the check fails on a forbidden import, a value that disagrees across two files, or a broken directory shape. The engine ships with the CLI. The policy stays in your repository.

Jidoka says nothing about your directory shape. For the repository structure these layers sit in, see the Monorepo Structure Standard. For an agent team that runs on these layers every day, see the Kata Agent Team.