#fc — Focus Series Specification

Contents

Canon — meta. This document defines terminology, numbering, authority, title, and file conventions for the fc series. For higher authority-system rules, follow co-99-01-authority.md.

There is no unified banner title for the series. Each volume has its own title(Imunrok, Chondamjip, Yahwa, Byeolchaek, and so on). Only the folder code fcNN is the systematic identifier.

Related Items: co-99-01-authority.md · co-99-02-core-principles.md · ../co-00-04-index.md

---

#Purpose

The core book(co) and major expansions(ex1·ex2) alone make it hard to steadily publish small supplements focused on a single topic. ex projects are too large to release quickly, while co is the authoritative rule core and cannot carry experimental or local material. fc is a small, single-topic, high-frequency series that fills the gap between them.

---

#Identity

Small enough to write quickly and revise quickly.

• Small — A volume is basically ≤ 20 .md files(including index, meta, and appendix files). However, if splitting detailed operations documents inside one topic is clearer, volume-level approval may expand the cap to ≤ 25 .md files.
• Single-topic — One volume handles only one topic(single NPC, incident, school, one-shot scenario, and so on).
• High-frequency — If ex is a year-scale project, fc is sized for weekly/monthly release.
• Self-contained — It must depend only on co and be playable on its own.

---

#Numbering System

#Folder Name — fcNN (two-digit zero padding)

• Format: fc01, fc02, ..., fc99.
• No one-digit form (fc1 ✗), no three-digit form (fc100 ✗).
• fc reserves two digits because it assumes more releases than ex(1 digit). Maximum 99 volumes.
• Numbers follow release order. There are no reserved slots by topic — do not skip empty numbers.

#Internal File Name — fcNN-SS-DD-descriptive-name.md

This inherits the 2-2-name pattern from the core book and expansions.

• SS — section number (00–99, two-digit zero padding)
• DD — document number inside the section (00–99, two-digit zero padding)
• Examples: fc07-01-02-kidnapping-plot.md, fc23-00-00-index.md

#Section Slots

#Required Root Files

---

#Scope Hard Cap — Basic ≤ 20 Documents, Approved ≤ 25 Documents

• The number of .md files inside fcNN/ should basically stay at 20 or fewer. VERSION, cover images, and maintenance records outside the public root do not count. Meta, index, main text, and appendix files all count.
• If the volume's topic would be excessively compressed inside 20 documents, it may expand to 25 or fewer with explicit approval and a maintenance record.
• If the volume exceeds 20 documents without approval or exceeds 25 documents at all, one of the following two paths is mandatory:

1. Reduce — merge, delete, or move documents outside the volume to return within the basic or approved cap.
2. Promote — migrate it to exN(see the Promotion Clause below).

• Do not publish while ignoring the cap. The identity of fc is "small."

---

#Dependencies and Self-Containment

All direct dependencies are listed in the frontmatter depends field.

---

#Authority

Authority level definitions follow co-99-01-authority.md. The default rank of an fc document depends on content type:

#Absolute Rules

• New data in an fc is authoritative only inside that fc. When another fc or ex references it, treat it as optional material.
• An fc cannot overwrite co Canon. On conflict, the core book takes priority.
• An fc also cannot overwrite an ex Canon domain. However, an fc that does not depend on that ex may include an fc-internal alternative (explicit statement required).

---

#Frontmatter Standard

Every fc .md has the following frontmatter:

---
version: 1.3.3
depends:
 - ../co/co-00-04-index.md
 # Add ex/fc if needed
authority: Scene Tool   # Canon / Summary / Campaign Module / Scene Tool / Data Catalog / RP Guide / Reference Only / Fiction-Only / Archive
focus: [one-sentence topic]   # Example: "Matsunaga Hisahide and the curse of Tsukumo Nasu"
reading_time: 45m     # expected time for this document alone
---

The index(fcNN-00-00-index.md) represents the whole volume, so its focus uses the topic of the whole book, and its reading_time uses the time for the whole volume.

---

#Title Convention — Free Naming By Volume

Each fcNN has a unique title. This follows the same pattern as the core Konsei Reiyotan and the expansions Drift of the Spirit Realm and Hyakka Yoran, which each have different names. There is no single banner title that groups the whole series.

The title format is Korean + Hanja in the form [topic, region, or person] [style suffix]. Choose the style suffix from the open list below — traditional styles outside the list are also allowed.

#Style Suffix Candidates (Open List)

#Naming Examples

• fc01 — Yogoe Imunrok (妖怪異聞錄) — yoma bestiary supplement
• fc02 — Sakai Yahwa (堺 夜話) — 5 ghost stories from Sakai harbor
• fc03 — Oda-ga Byeolchaek (織田家 別冊) — details for Oda Nobunaga and his retainers
• fc04 — Tsushima Chondamjip (対馬 寸譚集) — 3 one-shot scenarios in the Tsushima Strait
• fc05 — Tennen Rishin-ryu Gimunjip (天然理心流 奇聞集) — deeper treatment of a specific school
• fc06 — GM Sucheop (GM 手帖) — collection of play-reference tables

#Constraints

• The title must use Korean + Hanja notation. Do not omit the Hanja notation (inherited from the core/expansion convention).
• Do not use the same or a similar title as the core, an expansion, or an existing fc. Examples: do not reuse Drift of the Spirit Realm or Hyakka Yoran.
• In the index(fcNN-00-00-index.md), put the Korean title in the frontmatter name field and write Korean (Hanja) in the body H1.

---

#Inherited Conventions (Same As Core And Expansions)

• Dice: only 2d10, d100, and d10. No other polyhedral dice.
• Time unit: round(間合). Do not introduce a separate turn term or alternate round vocabulary.
• Section symbols: when needed, use the § Scent(香) → § Law(法) structure (same as the ex line).

---

#Suitable / Unsuitable

#Suitable (write as fc)

• Single NPC deep dive — examples: one volume for Oda Nobunaga, one volume for Matsunaga Hisahide.
• One-shot scenario (1–3 sessions) — examples: "Ghost Story on the Ise Pilgrimage Road", "Black-Market Incident at the Sakai Trading House".
• Single school, sorcery, or rite spotlight — examples: one volume for Tennen Rishin-ryu, one volume for a specific barrier rite.
• Narrow region or custom feature — example: naval-battle supplement limited to the Tsushima Strait.
• Prerelease experimental rule (GM test kit) — candidate for later promotion to co or ex.

#Unsuitable (write elsewhere)

---

#co / ex / fc Comparison Table

---

#Promotion Clause

fc has the following clause to enforce the identity that it "must be small."

1. If an unapproved fc exceeds 20 documents, or if any fc exceeds 25 documents regardless of approval, resolve it within the next minor version.
2. Resolution methods:
3. Reduce — merge, delete, or move appendix material outside the volume to return within the basic or approved cap.
4. Promote — migrate it to exN. Leave only a "→ promoted to exN" notice at the top of the original fcNN-00-00-index.md, and demote it to Archive.
5. An fc left at 26 or more documents is demoted so that its entire authority becomes Archive (automatic clause).

---

#Deprecation

• A deprecated fc adds a > **Archive.** callout at the top of fcNN-00-00-index.md and changes frontmatter authority to Archive.
• Do not delete the directory (history preservation).
• If another document references a deprecated fc, break the link or add "(Archive)" notation.
• Record the reason for deprecation at the bottom of the volume-specific maintenance change record.

---

#Publication Number Registry (Optional)

• When publishing sequentially from fc01, maintaining a registry is recommended so the topic assigned to each number is visible at a glance.
• Registry location: co-99-meta/co-99-fc-registry.md (if created).
• This specification document does not force a registry management method (operational discretion).

---

#Checklist — When Publishing A New fc

• [ ] Is the folder name two-digit fcNN?
• [ ] Are fcNN-00-00-index.md and fcNN-VERSION present, and is the volume-specific maintenance change record preserved outside the public root?
• [ ] Do internal file names follow the fcNN-SS-DD-name.md pattern?
• [ ] Does every frontmatter block have depends, authority, and focus?
• [ ] Is the total document count 20 or fewer by default? If it exceeds that, is there volume-level approval and a maintenance record, and is it 25 or fewer?
• [ ] Do references remain intact without co? (If depending on ex, is the alternative stated?)
• [ ] Are there no rules attempting to overwrite co or ex Canon?
• [ ] Does the title use Korean + Hanja notation? (free style such as Imunrok, Chondamjip, Yahwa, or Byeolchaek)
• [ ] Does the title avoid duplication with the core, expansions, and existing fc volumes?
• [ ] Are the dice limited to 2d10, d100, and d10?