#Edo Adversary Data Design Principles

Contents

Canon. Design principles and hub for the Edo-specific adversary data added in ex3.

---

#Scent — Edo's Adversaries Stand Among the People

Edo's enemies are not only monsters that descend from the mountains. Dojo disciples, a possessed daimyo, a merchant with a black ledger, a yoma sitting like the master of someone else's house — all become adversaries. Numbers are the weight of a blade's edge; a character's role in an incident is the reason that blade was drawn.

#Law — Choosing Adversaries by Role

• Do not create new data when existing co adversaries are sufficient.
• First decide whether the incident needs an enemy to defeat, negotiate with, keep alive, or outlast after their organization remains.
• Choose a rank and data type for that role, then note one problem that remains after the adversary is incapacitated.
• Create new data only for a recurring Edo role that existing data cannot fill. Candidates are famous Edo yoma absent from the core, Edo Kaidan variants with distinct tactical functions, repeatedly needed human adversaries, and faction leaders or campaign antagonists. Give them an incident use and post-resolution criteria as well as rank, stats, and techniques.
• Final question: does removing this adversary end the incident, or does it reveal the incident's true architect?

---

#Documents

• ex3-06-01-edo-yoma.md
• ex3-06-02-human-adversaries.md
• ex3-06-03-faction-bosses.md

---

#Rank Guidelines

---

#Reusing Core Data

Yoma already in the existing co are used as-is. Onryo, yoko, rokurokubi, bakeneko, tsukumogami, nurikabe, kappa, and umibozu default to their core data. ex3 creates variants or named adversaries only when a distinct Edo Kaidan function is required.

---

"Edo's adversaries are dangerous not because they are strong, but because they stand at the center of the incident."