The Archival Coding Standard
How every BEPCO record is addressed: the layer bit, the record-type register, three serial tiers, and the kit endcap. The system document for the archive itself.
Code Anatomy
Two descriptors set the frame; two components do the addressing; one optional endcap disambiguates a kit's faces. BEPCO and the layer bit describe every record and narrow nothing. Record type and serial carry the identity. The dotted endcap appears on kits alone.
| Segment | Role | Rule |
|---|---|---|
| BEPCO | Descriptor | The institution prefix. On everything. Never varies. |
| L | Descriptor | Layer bit. R = real, F = fictional. On everything; describes, does not identify. See §02. |
| TT | Address | Record type. Two characters from the register in §03. Describes and addresses. |
| SSSS | Address | Serial. Behaves in one of three tiers — counter, canonical word, or faceted. See §04. |
| ·x | Modifier | Endcap. Disambiguates the faces of a single kit. Kits only; absent everywhere else. See §05. |
Layer · Real vs. Fictional
A descriptor, not an identifier. It rides on every record and settles the one question a visitor might ask — "is this the real studio, or the story?" — before they read a word.
| Bit | Layer | Represents | Voice |
|---|---|---|---|
| R | Real | BEPCO Studio — the actual 2026 entity | Plain, factual, first-person maker |
| F | Fictional | Brickworks Electric & Power Co. — the in-world utility | Institutional, in-character, archival |
Record Type Register
A non-exhaustive 80/20 set — the record kinds actually expected on the site and in the archive. Most are layer-agnostic. New types are added only when a real body of records needs one.
| Code | Record Type | Typical layer | What it covers |
|---|---|---|---|
| KT | Kit | F R | A physical LEGO kit. The one faceted record type — see §05. |
| CM | Commission | R | Bespoke builds and museum pieces. Increments on its own. |
| FN | Field Notes | F R | Blog/journal surface. Build logs, process notes, event write-ups, in-world dispatches. Increments on its own. |
| AR | Archive Record | F | Standalone in-world documentation not tied to a kit. |
| RI | Real Information | R | Genuine transmission-tech and energy-sector content. The credibility layer. |
| PR | Press / Correspondence | R | Contact, press, inquiry, channel-catalog records. |
| AB | About / Institution | R F | Who BEPCO is — real studio bio and in-world company history. |
| SH | Shop / Catalog | R | Requisition-style catalog and availability records. |
| RF | Reference / Schema | R | System docs like this one. |
Serial Address Space · Three Tiers
The serial behaves in one of three ways, each matched to how a kind of record actually exists. A type never shares its counter with another type — a field note incrementing never touches the kit count.
The Kit Endcap · Faces of One Object
A kit is the one record that manifests across many surfaces as a single identity — a real product carrying a fictional artifact. Its faces share one serial and fan out by a dotted endcap. The layer bit still varies per face: the shop face is real, the instructions and box are fictional, and the archive face takes either layer — the studio's real catalog entry or the utility's in-world one.
| Endcap | Face | Layer | Notes |
|---|---|---|---|
| ·S | Shop / requisition | R | The face where money moves. |
| ·I | Instructions / booklet | F | In-world artifact. |
| ·A | Archive record | R F | Either layer — the studio's real record (R) or the utility's in-world catalog (F). The endcap letter is A (Archive), not R — R is the layer bit. |
| ·B | Physical box | F | Keeps the fiction intact in-hand. Optional — a box may instead carry ·A to point at the record. |
Era variants are separate kits, not stacked endcaps. A 1958 reissue of the H-Frame is a different product and gets its own serial (e.g.
KT-0014), never KT-0001·I·O. The endcap stays single-purpose and never stacks.
Worked Examples
Standing Rules
| Rule | Statement |
|---|---|
| Casing | All alphabetic segments uppercase. |
| Descriptors first | BEPCO then the layer bit always lead. They frame; they never address. |
| Addressing | Identity is carried by record type + serial only. |
| Serial tiers | Counter (four digits), canonical (one word), or faceted (shared kit serial + endcap). Never mixed. |
| No shared counters | Each type counts in its own space. One type incrementing never advances another. |
| Endcap scope | The dotted endcap is kit-only and never stacks. |
| Era handling | Era is not encoded in the code. It lives in colorway, the diamond marker, and — for kits — separate serials per variant. |
| Cross-reference | Non-kit records relate to a kit by pointing at its serial in metadata, not by borrowing it. |
| Immutability | Once assigned, a code is never reissued or reused. |