Documentation

Jidoka builds quality into the instructions that humans and agents share. You put every file on one layer, and a check then stops the line when a layer drifts. Each section below covers one part of that work. Start with the adoption guide, then choose the guide for the task you have now.

Adopt the Standard (Teams Using Agents)

Adopt Jidoka in Your Repository

Install the Jidoka skill pack, create the root instruction layers, add the checks to your check command and CI, then watch the line stop on a planted defect.

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. A bad agent run then points at exactly one file.

Author or Repair One Instruction Layer

Write or fix one layer at a time. Find 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 yes-or-no check. Tag both gates so that one search finds every gate in your repository.

Write Jobs To Be Done Entries

Write a job entry that links 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, the four forces, 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

Add the jidoka checks to your check script and your CI workflow. Read a finding, and 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 that 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, and the policy stays in your repository.

Jidoka does not define your directory shape. For the repository structure that holds these layers, see the Monorepo Structure Standard. For an agent team that runs on these layers every day, see the Kata Agent Team.