BEPCO Studio Richmond, Virginia Est. 2026 BEPCO-R-RF-SCHEMA
Institutional Record · Studio Document BEPCO-R-RF-SCHEMA

The Archival Coding Standard

Filing & reference schema · Records Office
ReferenceBEPCO-R-RF-SCHEMA
LayerR · Studio document
Serial tierCanonical · SCHEMA
CustodyRecords Office
Date filedJuly 21, 2026
StatusActive · Standing

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.

BEPCOInstitution · descriptor LLayer · R or F · descriptor TTRecord type · addresses SSSSSerial · addresses ·xEndcap · kits only · optional
SegmentRoleRule
BEPCODescriptorThe institution prefix. On everything. Never varies.
LDescriptorLayer bit. R = real, F = fictional. On everything; describes, does not identify. See §02.
TTAddressRecord type. Two characters from the register in §03. Describes and addresses.
SSSSAddressSerial. Behaves in one of three tiers — counter, canonical word, or faceted. See §04.
·xModifierEndcap. 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.

BitLayerRepresentsVoice
RRealBEPCO Studio — the actual 2026 entityPlain, factual, first-person maker
FFictionalBrickworks Electric & Power Co. — the in-world utilityInstitutional, 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.

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.

CodeRecord TypeTypical layerWhat it covers
KTKitF RA physical LEGO kit. The one faceted record type — see §05.
CMCommissionRBespoke builds and museum pieces. Increments on its own.
FNField NotesF RBlog/journal surface. Build logs, process notes, event write-ups, in-world dispatches. Increments on its own.
ARArchive RecordFStandalone in-world documentation not tied to a kit.
RIReal InformationRGenuine transmission-tech and energy-sector content. The credibility layer.
PRPress / CorrespondenceRContact, press, inquiry, channel-catalog records.
ABAbout / InstitutionR FWho BEPCO is — real studio bio and in-world company history.
SHShop / CatalogRRequisition-style catalog and availability records.
RFReference / SchemaRSystem 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.

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.

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.

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.

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
EndcapFaceLayerNotes
·SShop / requisitionRThe face where money moves.
·IInstructions / bookletFIn-world artifact.
·AArchive recordR FEither 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.
·BPhysical boxFKeeps 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.

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.
BEPCO-F-AR-0007
Fictional · Archive. A standalone in-world document, not tied to a kit. Its own counter.

Standing Rules

RuleStatement
CasingAll alphabetic segments uppercase.
Descriptors firstBEPCO then the layer bit always lead. They frame; they never address.
AddressingIdentity is carried by record type + serial only.
Serial tiersCounter (four digits), canonical (one word), or faceted (shared kit serial + endcap). Never mixed.
No shared countersEach type counts in its own space. One type incrementing never advances another.
Endcap scopeThe dotted endcap is kit-only and never stacks.
Era handlingEra is not encoded in the code. It lives in colorway, the diamond marker, and — for kits — separate serials per variant.
Cross-referenceNon-kit records relate to a kit by pointing at its serial in metadata, not by borrowing it.
ImmutabilityOnce assigned, a code is never reissued or reused.