【Notice】FireMatch Empire Development Progress Archive Numbering System 2.0

Document ID & Publication Time

Document ID: FM-DEV-0000
Published: 2026-01-10 18:10 【PST】

Official Notice

This document is an official 【Notice】 of FireMatch,
concerning the FireMatch Empire Development Progress Archive Numbering System 2.0.

This notice belongs to the category of Meta Notices within the development progress system,
and is used to establish and freeze the organizational structure, numbering rules,
and semantic boundaries of FireMatch’s public-facing development progress information.

I. Purpose and Scope of the System

1.1 System Objectives

This system is designed to address the following questions:

How to communicate the current real development status externally
How to record progress that has already occurred
How to maintain historical traceability without creating any form of commitment
How to clearly distinguish between status / facts / wording / direction / stance / the system itself

Supplementary Note:
Among the distinctions above,
explanatory documents and design-origin materials are not part of progress, status, or commitments.
Their sole purpose is to assist understanding of FireMatch’s design background and reasoning.

This system is explicitly not used for:

Feature commitments
Timeline commitments
Roadmap guarantees
Commercial outcomes or release judgments

1.2 Scope of Application

This system applies to all FireMatch official public-facing development progress content,
and is binding on all future FM-DEV–numbered documents.

Clarification:
Explanatory documents using FM-DEV numbering
are still bound by numbering rules,
but do not thereby acquire progress or commitment semantics.

II. Positioning of the Numbering Systems

Within FireMatch’s official document ecosystem,
there exist two numbering systems with completely independent semantics and legal standing:

2.1 FM-ARCHIVE (Civilization Public Archives)

Civilization-level / canonical records
Irreversible and non-overwritable
Used for narrative, definitions, and irreversible rulings

2.2 FM-DEV (Development Progress Archives)

Used to describe real development status and official wording
Does not constitute any form of commitment
Updates allowed (for specific types only)
Overwrites allowed (for specific columns only)

Supplementary Note:
The FM-DEV system may also carry
explanatory, traceability, and design-argument documents,
which are not semantically equivalent to “development progress.”

FM-DEV and FM-ARCHIVE must not be converted, mixed, or cited as legal basis for one another.

III. Development Progress Archive Number Format

3.1 Number Format

All development progress archives use the unified format:

FM-DEV-XXXX

Where:

FM: FireMatch
DEV: Development (progress state)
XXXX: Four-digit sequential number, starting from 0001

3.2 Number Properties

Each FM-DEV number has the following properties:

Uniqueness
Permanence
Historical sequence significance

The number indicates only the order of first publication,
and does not represent completion level, priority, or version stage.

IV. Overview of the Type System (Core of 2.0)

FireMatch’s development progress system adopts a three-layer semantic structure:

Meta-level institutional types
Progress / event types (bound to FM-DEV numbers)
Column semantic types (long-term pages, unnumbered)

Supplementary Note:
Some columns are used to carry
explanatory and design-origin content,
which does not participate in progress or commitment semantics.

V. Meta-Level Institutional Type

5.1 【Notice】 — Institutional Notice (Meta Notice)

Definition
Used to publish announcements that exert binding force on the development progress system itself.

【Notice】 does not describe development status or progress facts.
It exists solely to define rules, structures, and institutions.

Permitted Content Includes:

Establishment, upgrades, or freezing of numbering systems
Addition, explanation, or retirement of tag systems
Rulings on column responsibilities and semantic boundaries
Formal explanations of existing FM-DEV rules

Rules:

Must use an FM-DEV-XXXX number
Must not be overwritten
Carries institutional binding force
Has interpretive priority over all subsequent FM-DEV documents

Typical Example:

FM-DEV-0000 【Notice】Development Progress Archive Numbering System 2.0

VI. Progress & Event Types (FM-DEV Only)

The following types may appear only on pages using FM-DEV numbering.

6.1 【State】 — Current State

Describes FireMatch’s real development status judgment at the time of publication.

A. Living State Record

Location:
01 · Current Status

Rules:

Must use FM-DEV-XXXX 【State】
Content may be updated multiple times under the same number
Not treated as a historical event record

Number Upgrade Conditions:

Substantial development phase change
Clear shift in project focus
Overall judgment of “current state” changes

B. State Change Notice

Location:
02 · Progress Announcements

Rules:

Uses FM-DEV-XXXX 【State】
Must not be overwritten
Records a single, explicit state transition event

6.2 【Progress】 — Phase Progress Summary

Definition
A summary record of a phase that has already been completed or concluded.

Rules:

Uses FM-DEV-XXXX 【Progress】
May describe only facts that have already occurred
Must not be overwritten
Must not be used to predict the future

6.3 【Change】 — Wording / Structural Adjustments

Definition
Used to record changes in expression, column structure, or institutional wording.

Rules:

Uses FM-DEV-XXXX 【Change】
Does not describe feature implementation
Does not serve as a status or progress statement
Has no institutional legislative force

VII. Column Semantic Types (Long-Term Pages)

The following types use optional FM-DEV numbering
and are intended for long-term pages.

7.1 【Direction】 — Development Direction

Location: 03 · Direction Planning

7.2 【Confirmed】 — Positions Confirmed Not to Change

Location: 04 · Confirmed

7.3 【Unconfirmed】 — Areas Not Yet Decided

Location: 05 · Unconfirmed

These pages may be fully rewritten,
do not preserve event history,
and explicitly do not constitute commitments.

7.4 【Essay】 — Explanatory & Design-Origin Documents

Location: 06 · Essays & Design Origins

Used to publish explanatory, traceability, and design-argument content, including but not limited to:

Origins of worldbuilding and civilization settings
Design philosophy, structural reasoning, and derivations
Historical, real-world, or engineering background analysis

Content in the 【Essay】 column:

May optionally use FM-DEV numbering
May be modified, supplemented, or fully rewritten
Does not describe current development status
Does not record phase completion
Does not constitute any feature, timeline, or version commitment

VIII. Column × Type × Numbering Matrix (Frozen)

Column	Allowed Types	FM-DEV Required
00 · Institutional Notices	【Notice】	Required
01 · Current Status	【State】	Required
02 · Progress Announcements	【State】 / 【Progress】 / 【Change】	Required
03 · Direction Planning	【Direction】	Optional
04 · Confirmed	【Confirmed】	Optional
05 · Unconfirmed	【Unconfirmed】	Optional
06 · Essays & Design Origins	【Essay】	Optional

IX. Numbering Rules (Immutable Clauses)

Numbers are assigned in order of first publication
Numbers are never reset
Numbers are never reused
Content assigned an FM-DEV number must not be overwritten
Numbers do not represent commitments, completion, or version stages

X. Effective Time

This system takes effect as of
2026-01-10 18:10 【PST】.

From this point onward,
all FireMatch official development progress–related content
must unconditionally comply with this system.

— FireMatch Studio