Shokunindō in the Software Era

Craft Ethic → Digital Practice

This document maps how the craft ethic of Shokunindō is expressed in modern software systems. These are not innovations; they are translations under digital constraints.

Shokunindō provides the ethic. Systems enforce it where discipline alone is insufficient.

Lineage Overview

• Ethic: Shokunindō (craft, responsibility, care)
• System: TPS (visibility, flow, stop-and-fix)
• Software Era:
  • Agile Manifesto
    Values direct engagement, working systems, feedback from reality, and adaptation over adherence to plans.
  • The Twelve-Factor App
    Encodes deployability, operability, and inspectability as design constraints to ensure reliability under change.
  • Site Reliability Engineering (SRE)
    Treats reliability as a first-class feature, formalizing sustainable pace, failure handling, and continuous learning at scale.
  • Extreme Programming (XP)
    Preserves hands-on craft through technical discipline: testing, refactoring, pairing, and small, finished increments of work.

Agile Manifesto → Craft Under Uncertainty

Agile removes false certainty rather than adding speed.

• Individuals & interactions → Respect the craftsman
• Working software → Finish what you start
• Customer collaboration → Genchi Genbutsu
• Responding to change → Perfection as direction, not claim

Agile succeeds only when treated as a craft discipline, not a productivity hack.

Twelve-Factor App → Reliability by Design

Twelve-Factor encodes operability and inspectability.

• Single codebase → Genba
• Explicit dependencies → Design for repair
• Config in environment → Separate form from instance
• Stateless processes → Make problems visible
• Fast startup / shutdown → Stop and fix
• Logs as streams → Andon

This is TPS translated into runtime behavior.

Site Reliability Engineering (SRE) → Craft at Scale

SRE is the clearest modern expression of Shokunindō in software operations.

• Reliability over features → Reliability above all
• Error budgets → Sustainable pace (Heijunka)
• Blameless postmortems → Hansei without excuse
• Automation of toil → Respect for people
• Capacity planning → Eliminate overburden (Muri)

SRE enforces what individual discipline cannot sustain under load.

Extreme Programming (XP) → Hands-on Craft Discipline

XP preserves craft at the code level.

• Test-first development → Design for repair
• Continuous refactoring → Iteration with care
• Pair programming → Teach by example
• Small releases → Finish cleanly
• Collective ownership → Respect the work

XP fails when treated as ideology. It succeeds when treated as shop practice.

Summary

Agile removes false certainty. Twelve-Factor removes hidden fragility. SRE enforces reliability. XP protects craft at the bench.

Shokunindō supplies the ethic that makes all of them coherent.