Appendix B. AES-ID v1.0 — Identifier Scheme, Permanence Rules and Register Fields

Master Register §1–§2, extracted verbatim from the register of November 14, 2026 (SHA-256 91f17bbd…4011).

1. The identifier scheme (AES-ID v1.0)

Public Entry ID grammar:

AIK-YYYY-T-O-KEY[-NN]

Element Meaning Rule
AIK Aikipedia Constant
YYYY Collection year — always Never the original publication year; that date is recorded separately (§2)
T Record type: F full-length entry · E expanded entry · S short entry · L lexicon installment / collection container Fixed at assignment
O Editorial origin: P originally published in the collection year · N newly commissioned for the collection Fixed at assignment
KEY Editor-assigned identifying letters (uppercase ASCII letters and digits) Assigned in this register, never derived mechanically; established acronyms take priority; otherwise a distinctive stem, generally 3–12 characters; two-letter keys only when the acronym is canonical
NN Optional collision suffix (-02, -03, …) Used only when the full ID (year + type + origin + key) would otherwise collide

Permanence rules

  1. Two levels of identity. The Internal Concept ID (AIKC-######, sequential, never reused) identifies a concept across all its texts, years, and editions. The Public Entry ID identifies one specific entry record within a collection. This register is where the two are linked.
  2. Assignment. IDs are assigned when a record is accepted into this register. Until then, an entry's metadata reads "To be assigned."
  3. Never reuse. Once assigned, an ID is never reused, even if the record is withdrawn; withdrawn records are marked Retired.
  4. Type and origin are assignment-time facts. Later changes in length, classification, title, or publication status are recorded in the register's fields, never by altering the ID.
  5. Corrections vs. expansions. A correction to an existing entry retains its Public Entry ID and receives a new version number. A separately published expansion receives a new Public Entry ID, linked to the same Internal Concept ID.
  6. Containers and contained entries. An installment (L) and each entry within it receive separate IDs; contained entries carry the parent installment's ID in the Parent Record field, together with their original sequence within the installment. A concept occurring in several installments receives a separate entry record per occurrence, all linked to one Internal Concept ID; the -NN suffix is used only on a full-ID collision, not merely for repetition.
  7. Versions are not identifiers. Version numbers (draft v0.x; collection versions from 1.0 at publication) live in the Version field and in each entry's editorial record.
  8. IDs identify records, not correctness. A record's review and publication state is carried by its Status field, never by its identifier.
  9. Collection scope. A Public Entry ID identifies a record within one annual collection. If the same concept appears in a later collection (for example, a revised RLVR treatment in Aikipedia 2026), that collection assigns its own Public Entry ID, linked to the same Internal Concept ID; earlier collections' records are not altered.
  10. Provisional concept IDs. A provisional concept identity (assigned where a variant's distinctness is unverified — e.g. the "2.0" variants CAI2 and INSTRTUNE2, and concepts whose attestation is unverified) carries a normal Internal Concept ID; provisionality is a classification state recorded in the record details, not a separate ID series. If the concept is later merged into another concept, its Internal Concept ID is marked Retired — merged into AIKC-######, is never reused, and its entry records are re-pointed to the surviving concept ID, with the re-pointing verified, and the merger recorded in the assignment log (§4). A merger changes no Public Entry ID: the affected occurrence records keep their Public Entry IDs, and only their Internal Concept ID link is re-pointed; the retired ID is retained in this register with its merger history. If it is withdrawn without merger, its ID is Retired under rule 3. If its distinctness or attestation is confirmed, the provisional marking is removed and the ID continues unchanged. (Rule entered November 11, 2026; merger confirmation entered at the AES-ID v1.0 freeze, November 14, 2026.)

2. Register fields

Field Content
Internal Concept ID AIKC-######; immutable; one per concept
Public Entry ID As §1; one per entry record
Title Entry title as published or drafted
Type / Origin The T and O codes, spelled out in the record details
Parent Record Public ID of the containing installment (L records: —), with the entry's original sequence
Date of Appearance The earliest verified public appearance documented by the available evidence (never inferred from publicity), distinguishing that milestone from any claim of absolute historical priority. Where no sufficiently supported date is established, the field states 'Not established.'
Date of Original Publication First publication of this text (— for new additions not yet published)
Date of Collection Publication Publication in the annual collection (pending until published)
Version Current text version
Status One of: Draft · In review · Accepted · Published · Corrected · Superseded · Retired. For records at Accepted or beyond, the record details additionally itemize peer-review status, editorial approval, and publication status as three separate facts; a reviewer's acceptance is a recommendation and is never recorded as editorial approval
Contributor / Reviewers Model name and release number, per the standing identification rule
Source File, URL, or print location of the record's text
Base version The published text state the canonical text is corrected from, with the basis for the choice — the post's own declaration, the editor's choice, or sole published version (corrected originals only; AES §3). For an installment, stated per occurrence where occurrences differ

Correction IDs are recorded in the Master Register under the record's details (the register carries no separate correction-ID field).