Institutional Record · Studio Document BEPCO-R-RF-SCHEMA

The Archival Coding Standard

Filing & reference schema · Records Office

Every record in the BEPCO archive carries a reference code. This standard defines that code (the layer bit, the record-type register, three serial tiers, and the kit endcap) and governs how it is assigned.

Section 01

Code Anatomy

Each code is built from two descriptors, two addressing components, and one optional endcap. BEPCO and the layer bit are descriptors — present on every record, narrowing nothing. Record type and serial are the address, and carry the record's identity. The dotted endcap appears on kits alone.

BEPCOInstitution · descriptor – LLayer · R or F · descriptor – TTRecord type · addresses – SSSSSerial · addresses ·xEndcap · kits only · optional

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.

Section 02

Layer · Real vs. Fictional

The layer bit is a descriptor, not an identifier. It appears on every record and marks a single distinction: whether the record belongs to the real studio or the fictional utility.

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

Layer follows the face, not the object The same record type can sit in either layer depending on which face is being referenced. A process log about how a render was actually shot is R; a lineman's log written in-character is F. This is what lets a kit page speak in two voices — real where money moves, fictional where the world lives.

Section 03

Record Type Register

The record types currently in use across the BEPCO archive. A new type is added only when a genuine body of records requires 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.
RF	Reference / Schema	R	System docs like this one.

Deliberately deferred Left out until they earn a place: episodic records, insignia/logo asset records, and per-era variants — the last handled as separate kits (§05), not as a new type.

Section 04

Serial Address Space · Three Tiers

The serial takes one of three forms, each suited to how its record type is organized. No type shares a counter with another — a field note's count never advances the kit count.

Tier 1

Counter

FN-0004 · CM-0002

Most types. An independent four-digit count, zero-padded from 0001, unique within its own layer+type space. Things that come in sequences.

Tier 2

Canonical

RF-ABOUT · RF-SCHEMA

Singular records. The four digits are replaced by one uppercase word-token. The word signals "the one, not the 47th" — no siblings, no counter.

Tier 3

Faceted

KT-0001·S · KT-0001·I

Kits only. One shared serial across all the kit's faces, disambiguated by the dotted endcap. The serial threads identity within the kit family.

The rule in one line Serials are four digits (counter) or a single uppercase word (canonical) or a shared kit serial with an endcap (faceted). Never mixed within a record.

Section 05

The Kit Endcap · Faces of One Object

A kit is the one record type that exists across several surfaces under a single identity — a real product carrying a fictional artifact. Its faces share one serial and are distinguished by the dotted endcap. The layer bit varies by face: the shop face is real, the instructions and box are fictional, and the archive face may take either — the studio's real catalog entry or the utility's in-world one.

H-Frame Transmission Tower · Kit 0001

BEPCO-R-KT-0001·SShop — the saleable product · real layer, money moves

BEPCO-F-KT-0001·IInstructions — the booklet · fictional, institutional voice

BEPCO-R/F-KT-0001·AArchive — the catalog entry · R the studio's record, or F the utility's own

BEPCO-F-KT-0001·BBox — the physical package · fictional, part of the artifact

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.

Two rules that keep the endcap disciplined Kits only. A field note or commission has no faces — it never takes an endcap. The dot exists solely because the kit is the one multi-surface identity.

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.

Section 06

Worked Examples

BEPCO-F-KT-0001·I

Fictional · Kit · Instructions. The H-Frame booklet, institutional voice, faceted endcap.

BEPCO-R-KT-0001·S

Real · Kit · Shop. The same H-Frame as a saleable product. Same serial, different face, real layer.

BEPCO-R-CM-0002

Real · Commission. The 2nd bespoke build. Tier-1 counter, no endcap.

BEPCO-R-FN-0004

Real · Field Notes. The 4th field note. Its own counter, untouched by any other type.

BEPCO-R-RF-ABOUT

Real · Reference. The singular About record. Tier-2 canonical word-token, no counter.

Section 07

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.