CIB Is a Claim, Not a Condition
“Complete in box” is often treated as though it were a visible condition, like clean plastic or bright artwork. It is more useful as an evidentiary status. A box can look full while containing the wrong controller, a later power supply, replacement paperwork, or software from another bundle. A worn package can still support a complete claim if its identity and documented contents are established. CIB does not mean that every useful object associated with a platform is present. It means that a specific original retail package, sold in a defined region and period, can be identified and its documented contents accounted for.
That definition places the burden on the package rather than on the console family. “Saturn,” “PlayStation,” or “Genesis” identifies a platform context, but it does not define a retail object. The relevant object may be a core system, a game bundle, a later hardware revision, a regional electrical package, or a promotional configuration. Each can have different packaging, product numbers, controllers, power equipment, printed matter, and interior supports.
Three kinds of evidence should remain separate throughout a CIB record. A source claim is what a manufacturer manual, catalog, support document, court order, museum record, or other named source says. A measured fact is an observation from the physical example: a serial transcription, component count, box dimension, paper size, model marking, or label placement. A collector inference is a conclusion drawn from those claims and observations. The distinction matters because a source may establish that an item existed, while an inspection establishes only that the item is present in one example. Neither automatically proves that every related package contained it.
The U.S. Sega Saturn instruction manual provides a useful period example. Its package-content list identifies the Saturn console, control pad, A/V cable, power cord, battery, sticker, warranty card, instruction manual, and safeguards material. That list is valuable because it names small paper and consumable items alongside the obvious hardware. It is not a universal Saturn checklist. It describes the documented U.S. package represented by that manual, not every Japanese, European, later, or promotional Saturn package.
The Saturn list also demonstrates why “functional completeness” and “retail completeness” are different claims. A console, controller, video lead, and power cord may be enough to operate the system. They are not necessarily enough to recreate the documented package. A battery, warranty card, sticker, or safeguards sheet may have little practical value once the system is in a collection, but each can carry identification value. Their presence may support the package claim; their absence may require a qualification.
Several everyday terms should therefore be separated:
| Term | What it establishes | What it does not establish |
|---|---|---|
| Boxed | A box is present with the system or collection. | That the box is original, correctly matched, or complete. |
| Complete | The documented contents for an identified package are present. | That the contents are genuine, factory-paired, or cosmetically excellent. |
| Original | An item belongs to the original package claim being made. | That it is the oldest, cleanest, or only component ever associated with the system. |
| Matching | Identifiers or physical features correspond in some recorded way. | That the console and box were paired at the factory. |
| Authentic | The object is supported as manufacturer-produced rather than reproduced or counterfeit. | That it belongs to the particular box or was never replaced. |
These are independent tests. Identity asks which package is being examined. Completeness asks whether the source-supported contents are present. Originality asks whether those contents belong to that package rather than merely being compatible with it. Integrity asks whether the box, labels, manuals, and hardware are genuine and whether alterations or substitutions affect the claim.
A genuine console in a genuine box can still contain the wrong regional power equipment. A package with all the major hardware can include reproduction paperwork. A console and box can carry corresponding model information without any evidence that they were factory-paired. Conversely, a worn box may be entirely suitable for a documented CIB claim if its package identity and contents are clear. Cosmetic condition should not be allowed to substitute for evidence, in either direction.
Accessories sold separately should not become CIB contents merely because they are useful, contemporary, or commonly seen with the platform. Extra controllers, memory devices, cables, games, carrying cases, and adapters count only when the original SKU documentation identifies them as included. An item can be period-correct and still be a replacement. It can be authentic and still be an extra. The record should say which.
A practical vocabulary can make those distinctions visible. Documented CIB means that the original retail package has been identified, every source-supported content item is present, and no known substitution changes the claim. This is not a condition grade. A battered but genuine box may qualify under the same completeness definition as a clean one.
CIB with qualification required describes a package that appears coherent but contains an unresolved point. The issue might be a warranty card, inner tray, regional adapter, serial relationship, revision-specific manual, or structural insert. The qualification should identify the exact uncertainty. “CIB, warranty card not verified for this product number” is more useful than an unqualified label that conceals the gap.
Complete-looking/incomplete applies when the major hardware is present but documented items are missing, substitutions are known, or the package cannot be tied confidently to a particular SKU. This label is not an accusation of fraud. A missing item may reflect ordinary ownership, repacking, or incomplete research. It simply prevents visual plausibility from being treated as proof.
Consider a hypothetical inspection of a U.S. Saturn package. The box has appropriate artwork, the console and controller appear consistent with the model, and the A/V cable and power cord are present. The battery is installed, but no warranty card or safeguards sheet can be found. The package may be highly coherent, but the correct description depends on the evidence. If the Saturn manual’s list is being used for the target package, the record should state that the documented paper items were not located. It should not declare the system counterfeit, and it should not quietly call it complete because the hardware works.
The reverse problem is equally important. Suppose every listed item is present, but the box itself is a reproduction. The contents may be complete as a functional setup, yet the original retail-package claim fails. A complete collection of components is not automatically a complete original package. The box’s identity and integrity are part of the claim.
Manufacturer package-content evidence normally outranks collector convention because it addresses the historical question directly. A period manual, catalog, package insert, or contemporaneous product document may identify an item as supplied. Collector convention can help locate recurring components, but it can also merge regions, revisions, bundles, and later replacements. Repeated belief is not the same as period documentation. When convention and source material conflict, the conflict belongs in the record.
The best CIB description is therefore specific: identify the manufacturer, territory, product or model number, approximate period, documented contents, observed contents, substitutions, and unresolved questions. It should state whether each conclusion is a source claim, measured fact, or collector inference. CIB is not a synonym for “looks untouched,” “contains everything useful,” or “works correctly.” It is a reproducible claim about a particular retail object.
The Original SKU Is the Object Being Collected
A hardware family is too broad to serve as the basic collecting unit. The same platform name can identify a core system, a bundle with software, a later revision, a regional electrical package, or a promotional configuration. Each may have a different box, product number, controller, power component, printed set, and structural interior. “I have a Genesis” supplies platform context. A defensible CIB claim must identify which original retail package is represented.
An SKU, product number, and model number may describe different layers of that object. A model number can identify the hardware revision inside the box, while a product or item number can identify the retail package. The console, box, power equipment, controller, and bundled software may each carry separate identifiers. They should be transcribed independently rather than collapsed into one assumed identity. The relationship between them can then be recorded as documented, corresponding, inferred, or unresolved.
Sega’s 1993 product catalog gives a controlled example. It distinguishes the Genesis Core System, item 1630, from the Sonic the Hedgehog 2 System, item 1614. The catalog’s distinction includes software: the Sonic 2 package contains the cartridge, while the Core System is described without a software cartridge. The consoles may be closely related, but the retail objects are not the same.
The consequence is straightforward. A collector who places a correct Genesis console, controller, adapter, and RF equipment into the Core System box has not recreated the Sonic 2 package. If item 1614 is the target, the cartridge is not an optional extra. Conversely, placing the Sonic 2 cartridge into an item 1630 package does not silently convert the package into item 1614. It creates a Core System package with an additional item unless other evidence establishes that the target package has changed.
Collector inference: Sega’s catalog demonstrates why bundled software is an identity question before it is a completeness question. The physical console may be nearly identical between two packages, but the object being collected changes when the product identifier and included software change.
The same logic applies to later packages that retain a familiar platform name. A revised system may use a different console, controller, tray, manual, or power supply. A color variant may have a distinct product number even when the internal hardware is related to the standard release. A promotional package may contain ordinary hardware but a different box, bundled title, insert, or registration material. The prominence of the console should not obscure the package surrounding it.
Regional electrical packages make SKU-level identification equally important. Voltage marking, plug style, power cord, RF equipment, and language can change without changing the platform name. A box intended for one territory should not be called complete merely because it contains a functional component from another territory. Function establishes compatibility or usability; it does not establish original package membership.
The package identity belongs in the SKU analysis, not in a generic record template. A retail object should be distinguished by its manufacturer, territory, product or item number, language, electrical standard, approximate release window, and known revision when those facts are documented. The box front, back, ends, and bottom may carry different parts of that identity: product numbers, regulatory marks, barcode placement, language panels, and claims about included software. Those identifiers explain why a familiar platform name is not enough to define the object being collected.
The Genesis examples show the practical consequence. The console, box, controller, power component, and bundled software may each carry separate identifiers, and those identifiers should not be collapsed into one assumed identity. A package can therefore be identified as a product target before its contents are judged complete. The full field structure for recording those identifiers belongs in the Collector’s Evidence Ledger.
Platform context should remain separate from package-content proof. A corporate sales table may establish that a platform was sold in a territory or that a product family existed during a period. It does not necessarily prove the contents of a particular box. Sales records answer questions about distribution and market activity; manuals, catalogs, and contemporaneous product documents answer questions about retail contents.
This distinction prevents a common research error. A collector finds evidence that a console was sold in Europe and then assumes that a photographed European-looking box contains the standard European accessories. Or a catalog confirms that a bundle existed, and every box with similar artwork is treated as that bundle. Context can suggest a candidate identity, but it cannot replace package-specific evidence.
Contemporaneous manufacturer material generally deserves priority over later cataloging, but its scope still matters. A period catalog may list a product while omitting small inserts. A manual may describe contents for one revision. An official document preserved later may confirm that a manual existed without proving how every historical box was packed. The record should state what the document establishes and what it leaves unresolved.
Box architecture is part of SKU identity. Front artwork may be reused between territories or after a revision. The back panel may reveal the bundled game, included accessories, languages, and legal text. End panels and bottom labels may carry the product number that the front does not show. Identifying a package from its front image alone is therefore weaker than documenting all available panels.
Promotional and retailer bundles need separate treatment. A retailer may have combined a standard system with a game or accessory without creating a manufacturer-defined SKU. A mail-order offer may have used an ordinary system box and shipped an additional item separately. Such a package can be historically interesting, but it should not automatically be described as the same object as a documented manufacturer bundle. The record should identify the offer’s source and whether the package identity is supported.
Color variants deserve the same discipline. Color can be a useful clue, but it is not a complete identity test. A special color may indicate a region, later revision, limited package, or shell variation. It should be checked against model number, box language, regulatory marks, serial information, electrical specification, and included accessories. A color-only conclusion is a collector inference, not an established SKU identity.
A SKU matrix makes the distinctions visible. Each row should represent one package target, with columns for package title, product or item number, territory, model or revision, included software, controller count, power equipment, printed matter, box identifiers, and evidence status. If two rows differ only by software or regional power equipment, that difference still belongs in the record.
| Package field | Genesis Core System example | Sonic the Hedgehog 2 System example |
|---|---|---|
| Catalog item | 1630 | 1614 |
| Software status | No software cartridge listed | Sonic the Hedgehog 2 cartridge listed |
| Hardware evidence | Catalog-listed system hardware | Catalog-listed system hardware plus documented bundle distinction |
| Collector question | Are all contents appropriate to item 1630? | Is the documented cartridge and package identity present? |
The table does not establish every insert, tray, tie, warranty item, or regional counterpart associated with either package. It illustrates the necessary boundary: a catalog distinction can identify the target without answering every interior-packing question.
The proper collecting statement is therefore specific: “North American Genesis Core System, item 1630, with the catalog-listed hardware present.” If the box contains an additional cartridge, that should be recorded as an extra unless package evidence supports another target. If the manual, tray, or regional adapter remains uncertain, that uncertainty should remain visible.
The original SKU is the object because only the SKU gives completeness a defined boundary. Without it, the collector is comparing a physical assembly with a platform memory. With it, the box, hardware, software, accessories, and paperwork can be tested against a particular historical claim.
Region Changes the Checklist
A shared platform name does not establish identical contents across territories. Packages may differ in electrical equipment, language, regulatory information, video or RF equipment, controller presentation, warranty paperwork, and sometimes the console or controller’s color and form. Two systems can belong to the same hardware family while representing different retail objects. Regional identification is therefore required before a CIB checklist can be applied.
Sony’s service-manual scan for the SCPH-5500, SCPH-5501, SCPH-5502, SCPH-5503, and related configurations provides a useful comparison of model-specific electrical specifications and supplied accessories. Its evidentiary role must be described accurately. It is a Sony service manual, not a consumer retail package checklist. It can help identify model relationships, electrical differences, and accessory configurations, but it does not alone establish the complete contents of every regional box.
This limitation matters. A service manual may document that two model numbers differ in voltage requirements or supplied equipment. It does not necessarily prove the precise contents of a particular consumer package, including its inserts, inner tray, warranty paperwork, or regional promotional material. Retail completeness still requires package-specific evidence such as a consumer manual, catalog, package illustration, or documented physical comparison.
Sega’s Saturn technical bulletin provides a different kind of evidence. Dated November 8, 1995, it records regional differences in Saturn and controller color and form factor. That supports a narrow conclusion: regional variation may involve the appearance and shape of the hardware itself, not merely the language of the manual or the power cord. The bulletin does not establish retail contents, voltage rules for every package, serial-prefix rules, or a universal authenticity standard.
Collector inference: A platform name should be treated as a starting point rather than a checklist. Model number, box identity, electrical marking, and documented accessories must be evaluated together before a regional package is assigned.
Regional differences can appear in the power cord, external adapter, voltage marking, plug shape, RF equipment, and A/V arrangement. They can also appear in controller model, color, quantity, manual language, warranty layout, safety notices, and regulatory text. A component that physically fits another system is not thereby proven to belong to its original box.
Region should be assigned from converging clues rather than from one visual detail. In a mixed example, the box language and product number might support one market while the console model and power equipment point to another. That conflict is more informative than any isolated clue: it may indicate a swapped box, a replacement component, a regional revision, or an unresolved package relationship. The complete regional field list and status vocabulary belong in the evidence ledger.
No single clue is conclusive. Boxes can be swapped, labels can be altered, and accessories can move between packages. A console may have a regional shell but a replacement power unit from elsewhere. A box may carry the correct language while containing hardware from another market. The appropriate description may be “region supported by box language and model number; console-box relationship unresolved,” rather than a categorical regional claim.
PAL, NTSC-U, and NTSC-J should not be treated as interchangeable package categories. These labels describe broad video or market contexts, not universal contents lists. A PAL package may use different power equipment or documentation from an NTSC-U package. An NTSC-J package may use different box language, controller presentation, or warranty paperwork from both. Shared platform branding does not remove those distinctions.
Power equipment should be recorded as a regional and originality identifier. The specification on the console, adapter, or cord should be transcribed exactly as observed. A replacement that functions with the system may preserve usability, but it does not prove original package membership. An apparently correct adapter should not be accepted solely because its plug fits. Its markings, model relationship, region, and package evidence all matter.
Video and RF equipment can produce similar confusion. One package may document an RF switch or lead, while another uses a different connection arrangement. A later A/V cable may be compatible without being the documented original. The contents list and regional package evidence should control the classification, not an assumption that every console in the family used the same connection set.
Printed matter is often a strong regional indicator. Manuals can be translated, reformatted, or replaced by separate safety sheets. Warranty cards may contain territory-specific service language or registration instructions. Box panels may include local legal notices, distributor information, or language combinations. These items should be inventoried individually rather than summarized as “manuals included.” The correct hardware with the wrong regional paperwork may still fail the original SKU test.
The controller can also carry regional evidence. Its model marking, label, connector, color, and quantity should be compared with the package documentation. A second controller may belong to a later bundle or promotional package but be absent from the core system. Adding it does not make the package more complete. It should be marked documented, extra, period-correct, replacement, or unknown.
Regional identification becomes especially important when box and console have been separated for years. A box may belong to one market while the console belongs to another. A shared logo proves very little. Compare product number, model identifier, language, power marking, regulatory text, controller, cables, serial information, and paperwork as a group. If the clues conflict, describe the package as mixed or unresolved rather than forcing a regional label.
Manufacturer documents must also be read within their purpose. A service manual covering several model numbers may list variations rather than one universal package. A technical bulletin may document hardware differences without listing retail inserts. A later support page may identify a component without proving its historical inclusion. The document’s subject, date, market, and intended use should be recorded before its information is applied to a CIB claim.
A hypothetical inspection makes the problem concrete. Imagine a PlayStation package whose box language and model number point toward one market, while the power equipment bears another regional specification. The console label is consistent with the box, but the controller and manual are from a different language edition. The correct conclusion is not automatically “counterfeit” and not automatically “complete.” The package is mixed or unresolved until evidence explains the differences. The components may all be genuine; the original retail-package claim is still unproven.
A practical regional checklist has two stages. First identify the package: territory, model or product number, language, electrical standard, box identifiers, and approximate period. Then test contents: console revision, controller, power equipment, A/V or RF equipment, manuals, warranty matter, inserts, and structural packaging. Each item should be marked documented, observed, substituted, extra, or unresolved.
When several independent clues agree, they can support package coherence. They still do not establish factory pairing or prove that every regional component is original without package-specific documentation. Regional analysis is not intended to make collecting arbitrary. It prevents a shared platform label from doing work that only package evidence can do.
Japanese, North American, and European systems can each be authentic and complete in their own contexts. They are not interchangeable examples of one checklist. When the region changes, the retail object and its completeness standard can change with it.
What Counts as an Insert
Inserts are easy to overlook because many are thin, inexpensive, and visually secondary to the console. They are nevertheless part of a package’s historical and evidentiary structure. A CIB record should classify printed and structural contents rather than reducing them to “manual included.” The relevant question is whether a particular item was documented as part of the exact SKU and period under examination.
Printed contents may include an instruction manual, setup guide, safety sheet, safeguards notice, warranty card, registration card, catalog, promotional leaflet, game advertisement, battery notice, or sticker. These may appear as separate sheets or as sections of one booklet. A warranty card can be blank and still be original package matter. A registration card can be unused and still belong in the inventory. Condition and package membership are separate observations.
The U.S. Sega Saturn package documentation specifically identifies a sticker, warranty card, battery, instruction manual, and safeguards sheet alongside the console, control pad, A/V cable, and power cord. This establishes those items for the examined U.S. package. It does not establish that every Saturn region or revision used the same printed set, or that every box had identical placement and packing.
The example shows why low-value matter should not be dismissed automatically. A collector who checks only the console, controller, video lead, and power cord has established a plausible functional setup, but not necessarily the documented package. At the same time, the example should not be broadened into a universal Saturn taxonomy. It supports a method: document each item for the exact package.
Manuals require careful identification. A manual for the same platform may belong to another territory, model, revision, or language edition. A later manufacturer reprint may be genuine but not the booklet supplied with the original package. The record should capture title, language, model references, revision information where available, and evidence connecting the document to the target SKU. “Original manual” is too broad when the package relationship is unknown.
Safety sheets and safeguards notices are sometimes treated as duplicates because they contain little platform-specific information. That can erase regional and period evidence. Their language, regulatory wording, paper format, and package references may distinguish one market from another. If a source identifies a separate safety sheet, it should be listed separately even when its information overlaps with the manual.
Warranty and registration cards occupy an uncertain middle ground. Some collectors exclude them because they were intended to be mailed or discarded. That describes their use, not whether they were included. If exact-SKU documentation names the card, its presence supports completeness. If no package-specific evidence has been located, the card should be marked unresolved rather than automatically required or automatically dismissed.
Promotional leaflets and catalogs deserve the same discipline. A manufacturer may have inserted a product catalog, game advertisement, or registration promotion in one package period and changed it later. A period leaflet from the same company is not necessarily the leaflet supplied with the box being examined. It may be an extra, a replacement, or material from another SKU. Record its identity and evidence status instead of allowing age alone to establish package membership.
Stickers and labels can be especially difficult because they may have been applied to the console, placed loose in the box, or attached to a paper card. The Saturn documentation identifies a sticker as package content, but it does not establish its placement for every package or region. Describe what is observed—loose, applied, missing, or replaced—and separately state what the source documents.
Battery notices deserve their own entry when they accompany a battery or explain installation and disposal. A notice can disappear during ordinary ownership while remaining relevant to a strict package record. The same applies to protective films, temporary notices, and peel-off labels. Whether an item was intended to be discarded does not determine whether it was originally supplied. Inclusion must still be supported by exact-SKU evidence.
Structural pieces belong in the inventory even though they are not printed matter. Molded trays, cardboard spacers, dividers, sleeves, bags, cable ties, and restraints may organize the package or protect its contents. They can be evidence-bearing, but they must not be treated as presumptively required. Count them only when period documentation or a documented physical comparison supports their inclusion.
Modern online manuals are useful but limited evidence. An official manual index can help locate manufacturer documentation and confirm that a manual existed. It cannot by itself reconstruct the contents of a historical retail package. Current online availability may reflect later support priorities, regional uploads, or preservation choices rather than the original packing list. A downloadable manual should not silently become proof that a printed booklet, safety sheet, or related insert was included in every earlier box.
The exact SKU and period remain controlling. If an insert is documented for a later revision, it should not automatically be transferred to an earlier package. If a manual covers several models, the collector should determine whether the relevant package falls within its scope. If the only evidence is a photograph of another example, that image can be a comparison point or research lead, but it should not become a universal checklist without corroboration.
Disputed inserts should be recorded in the final evidence ledger, where each item receives its own source note and status. This chapter’s narrower point is that package membership must be established for the exact SKU, region, and period; age, visual appeal, or repeated collector convention cannot substitute for that evidence.
Period-correct accessories should remain separate from originally included items. A contemporary catalog may show a memory device, carrying case, extra controller, or cable associated with the platform. Unless the exact retail SKU identifies it as included, it should not count toward CIB completeness. Appropriate labels include “period-correct accessory,” “compatible replacement,” “later-region component,” and “package status unknown.”
A hypothetical inspection illustrates the distinction. Suppose a box contains a genuine manual, a genuine warranty card from the same manufacturer, and a contemporary promotional leaflet. The leaflet’s paper and artwork appear consistent with the period, but no source connects it to the target SKU. It should be recorded as an observed period item with package status unresolved, not counted automatically as a required insert. If the warranty card is explicitly listed for the package, it can support completeness even if it was never filled out.
Another hypothetical package contains a molded tray and cable ties that appear to fit perfectly. Unless the target package is documented through a manufacturer source or a reliable comparative record, the correct status is not “missing tray” when the pieces are absent. It is “structural packaging not documented for this SKU.” This wording avoids converting familiar packing arrangements into unsupported requirements.
Each item can be classified as documented original, observed but not documented, period-correct replacement, reproduction supported by evidence, extra, or unknown. That vocabulary preserves distinctions that an unqualified “complete” label would conceal. It also allows a package to be described honestly when the major hardware is present but a low-value paper item remains unverified.
The smallest pieces can carry significant evidentiary weight. A warranty card, battery notice, sticker, or cardboard spacer may distinguish an original package from a later assembly. The goal is not to elevate every scrap into a universal requirement. It is to identify what the evidence supports for one SKU, one region, and one period—and to keep everything else visibly unresolved.
Box Architecture and the Missing-Cardboard Problem
A retail console box is not merely an illustrated container around the hardware. Its interior may reveal how a particular package was assembled, which components it was designed to hold, and whether the contents now presented belong to one original SKU. Trays, dividers, endcaps, foam, sleeves, bags, cable restraints, and inner cartons can therefore carry evidentiary value. They do not become original simply because they look old or fit neatly. Each structural piece requires support from documentation for the exact package or from a carefully recorded comparison with identified examples.
The first useful distinction is between structural completeness and paper completeness. Structural completeness concerns the physical organization of the package: molded or folded trays, cardboard partitions, foam supports, endcaps, sleeves, inner cartons, bags, and restraints. Paper completeness concerns manuals, safeguards sheets, warranty cards, registration forms, catalogues, stickers, and promotional leaflets. A box may contain every documented paper item while lacking its original tray. Another may retain the tray but be missing a warranty card. Those are separate findings and should not be compressed into one yes-or-no judgment.
Source claim: The examined U.S. Sega Saturn manual lists a console, control pad, A/V cable, power cord, battery, sticker, warranty card, instruction manual, and safeguards material. That is useful evidence for the U.S. package covered by the manual. It does not establish the interior arrangement of every Saturn box, nor does it prove that Japanese, European, or later Saturn packages used the same tray, bag, divider, or restraint.
Interior construction can distinguish packages that share an exterior platform identity. A core system may use one cavity for a console, another for a controller, and a third for power equipment. A bundle containing software or an additional accessory may require a different insert while retaining broadly similar exterior artwork. A divider may separate a console from a power unit; a sleeve may protect a manual; an inner carton may carry a product label more specific than the outer box. These possibilities make the interior worth recording, but they do not make every familiar packing piece mandatory.
The relevant question is not, “Have collectors seen this tray before?” It is, “What evidence connects this tray to the identified original retail SKU, region, and period?” A manufacturer document that names the product number is stronger than an unidentified online photograph. Several physical examples with recorded identities are stronger than one attractive interior whose history is unknown. A package illustration may show an arrangement without proving that the pictured material was supplied in every production run. Evidence must remain within its documented scope.
Collector inference: If an inner carton, tray, and divider recur in independently recorded examples of the same product number and regional package, and their dimensions correspond to the claimed contents, they support package coherence. That inference remains weaker than a manufacturer packaging diagram or an explicit contents list. It should be written as support for a conclusion, not as proof that every surviving example originally contained the same structure.
Silence in a manual is especially easy to misuse. A contents list may identify the console and major accessories while omitting disposable bags, folded cardboard, or the exact arrangement of the interior. That omission does not prove that no structural material existed. Conversely, a photograph showing a tray does not prove that it was factory-standard. The record should distinguish documented present, observed but not documented, not observed, missing from a documented package, and not documented. The last status is often the most accurate where the documentation does not establish whether a piece belonged.
Institutional records show why packaging deserves independent cataloging. The Smithsonian National Museum of American History’s Magnavox Odyssey record documents box dimensions and accession information. Its NES record identifies a console, instruction booklet, associated game, accession data, and physical measurements. These are valuable examples of cataloging practice: the box, documentation, dimensions, and relationships among objects are treated as historical information. They do not establish a universal factory checklist for every Odyssey or NES package, nor do they prove that every object in an accession was factory-paired.
An accession describes a particular preserved object or group of objects. A museum may receive a surviving package with a box, console, booklet, and associated game, but that record does not automatically establish that every retail example shipped with that combination. The institution may also describe items collected together after their original sale. Accession-level completeness and original retail CIB are related but different questions. Museum documentation can be stronger than a seller’s description for identifying what the institution possesses while remaining insufficient to reconstruct the manufacturer’s standard package.
Physical comparison is most useful when it is tied to an identified package. A tray, divider, or inner carton that recurs in independently documented examples of the same product number may support package coherence, especially when its dimensions correspond to the claimed contents. That comparison remains an inference unless a manufacturer document or equally specific evidence establishes the relationship. The complete measurement and image-capture protocol belongs in the Collector’s Evidence Ledger.
A vacant cavity should be described carefully. It may indicate that a component is missing, but its shape alone does not identify exactly what occupied it. A cavity can also result from a replacement tray, a modified interior, or a different package configuration. “Open cavity consistent with a controller compartment” is an observation and qualified inference. “Missing original controller tray” requires stronger evidence connecting that cavity to the exact package.
Structural wear is contextual, not conclusive. Compressed foam, softened folds, rubbed tray edges, creased sleeves, and adhesive residue may be consistent with age and use. They may also result from storage, repacking, or later handling. A clean tray is not automatically a reproduction, and a damaged tray is not automatically original. Describe condition separately from origin: “tray present, worn, origin not independently documented” is more precise than “original worn tray.”
The same rule applies to bags, ties, and protective films. Some were intended to be discarded during setup; others may have been retained. A generic plastic bag that fits a controller is not documented package content merely because it appears old. A cable tie may be period-correct without being the tie supplied with that SKU. A protective film may have been applied at manufacture, added during later storage, or replaced during preservation. Unless exact package evidence supports inclusion, classify such material as period-correct, observed but undocumented, replacement, or unknown.
| Observed element | What it may show | What it does not prove by itself |
|---|---|---|
| Molded tray or folded insert | That the box was designed to organize particular contents | That the tray was supplied with every revision or region |
| Inner carton or sleeve | A possible package layer or product-specific construction | Factory pairing with the console now inside |
| Bag, tie, or protective film | Possible period packing practice | Original inclusion with the identified SKU |
| Empty cavity | That material may have been removed or the interior altered | The identity of the missing component |
Structural pieces should also be separated from presentation additions. A collector may add acid-free sleeves, replacement foam, tissue, or a custom divider to protect an original box. Those additions may be sensible preservation measures, but they are not original retail architecture. Record them as later protective material. Do not let a well-organized interior imply factory completeness, and do not penalize the box for a documented preservation sleeve that is clearly disclosed and kept separate from the original package assessment.
Structural completeness is therefore a bounded claim. Exact-SKU documentation or documented physical comparisons can establish that a particular interior belongs with a particular package. They cannot create a universal rule for every box carrying the same platform logo. Record the architecture, preserve measurements and photographs, identify the evidence level, and use “not documented” when the documentation does not settle the question. The missing-cardboard problem is real, but disciplined comparison is more reliable than confident assumption.
A Console’s Serial Number Is Evidence—not a Time Machine
Serial numbers are useful because they place physical objects within manufacturer identification systems. They are also easy to overinterpret. A console serial, box serial, warranty-card number, barcode, product number, or regional prefix may support package identity, but each is a separate observation. None should be allowed to tell a larger story than the evidence supports. Record the identifiers independently before deciding whether they correspond.
Begin with exact transcription. Photograph every serial or product label and copy the characters, punctuation, spacing, prefix, and suffix as displayed. Record the label’s position, surface, orientation, and condition. Note whether a number is printed directly on the shell, applied as a sticker, printed on the box, placed on a warranty card, or associated with a barcode. If a character is unclear, preserve the uncertainty. Do not silently replace an ambiguous “0” with “O” or a damaged digit with the most convenient reading.
A package may contain several different identification systems. The console model number may identify a hardware revision. The box product number may identify a retail package or bundle. A barcode may identify a sales unit without encoding the console’s individual serial. A warranty card may provide a space for a retailer or owner rather than a factory-linked number. These identifiers can be related without being interchangeable. The ledger should retain each one and describe its documented function where known.
Three terms keep the conclusions precise. Matching serials means that two displayed strings agree, or appear to agree, character by character. Corresponding serials means that numbers, prefixes, model references, or regional markings are consistent with the claimed product family or market, even when they are not identical. Factory-paired serials means that manufacturer or distribution records establish that the particular console and box were packaged together. The first may be a measured fact. The second is usually a source-supported inference. The third requires evidence beyond the objects themselves.
Nintendo support documentation states that a system serial number may appear on the box or receipt. That makes a box or receipt number worth recording. It does not state that a box number necessarily proves an individual factory pairing with the console currently inside. A box may remain after its original console is replaced, and a console may later be placed into a matching empty box.
This distinction matters even when the strings are identical. Matching numbers can support package coherence, particularly when the box product number, console model, language, regulatory markings, and accessories all agree. They cannot independently prove that the package was never opened, that every component was present at first sale, or that no part was swapped during ownership. A matching label is evidence of correspondence, not a record of an invisible factory event.
Regional prefixes provide another layer, but only within their documented scope. Nintendo’s support guidance for the NES Classic Edition gives “CU” as an Americas prefix example and “CEE” as a European example. This supports regional classification for that NES Classic Edition example when the prefix agrees with other evidence. It does not establish a universal prefix system for older Nintendo hardware, other manufacturers, or every console marketed in those territories.
The NES Classic Edition example also illustrates why power equipment should be recorded alongside serial evidence. Nintendo’s guidance discusses the original adapter associated with that product and distinguishes regional equipment. A CU or CEE prefix can support a regional inference, but it does not prove that the adapter, HDMI cable, controller, and box all originated in the same package. Record the power unit’s model, rating, plug, label, and condition separately from the console’s serial.
Barcodes require similar restraint. A barcode may identify a product family, sales unit, regional distribution channel, or package revision. It may correspond to a box product number without encoding the individual console’s serial. Agreement between barcode and product number supports package identity; disagreement deserves investigation. Neither result alone proves that the particular console was originally packed in that box.
Warranty cards can be especially ambiguous. A card may be printed for a particular region and package while leaving the serial field blank. It may contain a handwritten number, retailer stamp, or registration information added after purchase. Its presence can support the region and documentation set. It does not necessarily prove factory pairing, and its absence does not prove that a box was opened. Record what the card actually shows before drawing any conclusion.
Physical condition may reveal conflicts but cannot settle origin alone. Note torn label edges, residue, overprinting, mismatched fonts, different aging between a label and its surface, or a number that appears under a later sticker. These are measured facts that may support further inquiry. They are not automatic proof of alteration. A clean label may be original; a damaged label may reflect ordinary use. The correct conclusion depends on converging evidence.
Serial evidence is most useful as part of package coherence. Compare the console identifier with model or revision, box product number, region, language, regulatory marks, power specification, controller markings, cable type, manuals, tray arrangement, and provenance. If those elements converge, state that they support coherence. If one number agrees while the power equipment and printed matter point to another region, record the conflict rather than allowing the number to override the rest.
Collector inference: Console and box identifiers correspond to the same regional product family, and the observed accessories are consistent with that package. Unresolved: no manufacturer record located here proves factory pairing or uninterrupted ownership history. This is a stronger statement than “matching serials, guaranteed original” because it identifies both the support and the limit.
Serial labels can be transferred, replaced, obscured, or damaged. A label that appears consistent may have originated on another unit. A box may have been retained with a console for decades without being its first companion. These possibilities should not be asserted without evidence, but a sound method must leave room for them. Serial correspondence raises or lowers confidence; it does not reconstruct custody by itself.
Do not use serials as a shortcut around SKU identification. A console number may identify a revision while the box belongs to a bundled package. A matching console and box number can still leave the included game, controller count, power unit, or regional paperwork unresolved. Completeness is not established until the package target is known and its documented contents are compared with the observed contents.
The same caution applies to receipts. A receipt may support a purchase date, retailer, territory, or product description. It may carry a system serial, as the manufacturer guidance allows. It does not necessarily describe every component inside the box or prove that the current contents have remained unchanged. Treat it as provenance evidence with a defined scope, not as a complete packing record.
Serial evidence is neither trivial nor decisive. It can identify a model family, expose regional contradictions, and strengthen a carefully documented package claim. It cannot prove untouched history, complete contents, or factory pairing without records that establish those facts. Record every identifier independently, distinguish matching from corresponding and factory-paired, and let the conclusion stop where the evidence stops.

Authenticating the Box Before Authenticating the Console
Authentication should begin with the package as a group, not with a favorite logo or the apparent age of the console. A CIB claim includes the outer box, labels, manuals, structural packaging, hardware, accessories, and the relationship among them. A genuine console can be placed in reproduction packaging. A genuine box can contain substituted or mixed hardware. The authenticity of one component does not automatically transfer to the others.
The first layer is documentary comparison. Period manufacturer manuals, catalogues, package illustrations, and model-specific material can establish how a product was identified, which language it used, and which accessories were associated with it. Compare the box’s product number, model references, regional language, regulatory marks, and included-software claims with documentation for the same approximate period. A platform logo can be genuine while the surrounding product information belongs to another package or market.
The Sega 1993 catalog provides a useful controlled comparison. It distinguishes the Genesis Core System, item 1630, from the Sonic the Hedgehog 2 System, item 1614. The catalog supports the existence of separate package targets and identifies a software difference. It does not, by itself, establish every insert, tray, fold, or paper item in either package. That limitation should remain visible when the catalog is used for authentication.
Typography and logos are useful comparison points, but they are not solitary tests. Examine letterforms, spacing, weight, alignment, trademark placement, color relationships, and the way text sits beside photographs or illustrations. A deviation can matter when it appears alongside conflicting identifiers, paper, or construction. It can also reflect a revised print run, regional artwork, scanning distortion, or a change in package design. Use qualified language such as “appears consistent with” or “appears inconsistent with documented material,” not absolute authentication based on one visual detail.
Model identifiers and barcodes deserve particular attention. Check whether the model or product number appears in the expected position, uses the expected format, and describes the package rather than only the console. Compare barcode placement, surrounding text, regulatory marks, and language with identified period examples. A correct-looking barcode can be copied. A missing barcode may reflect a different regional or promotional package. Confidence increases when identifiers, language, marks, contents, and physical construction point to one SKU.
Print registration and paper characteristics may reveal differences between an original box and a later-made imitation, but visual inspection remains conditional. Compare board thickness, surface finish, color alignment, halftone structure, edge sharpness, fold geometry, die-cut edges, glue lines, and staple points. Examine how artwork wraps around corners and whether printed areas align across folds. These observations can support an inference. They do not establish manufacturing origin, date, or legal status without comparative evidence or provenance.
Original boxes may also look unusual because of storage, moisture, sunlight, compression, repairs, or handling. A faded panel is not automatically false. A clean replacement is not automatically original. If the paper and construction appear inconsistent with the documented period, record the inconsistency and identify what was compared. Avoid converting a visual impression into the stronger term “reproduction” unless comparative evidence or provenance supports that classification.
Interior construction provides an independent comparison. Check tray shape, divider placement, endcaps, foam, inner cartons, and the relationship between cavities and the claimed hardware. An interior that cannot accommodate the stated contents deserves explanation. However, a missing or altered tray does not by itself prove that the outer box is counterfeit. It may indicate loss, repacking, regional variation, a different package revision, or an unresolved configuration. Structural observations should be recorded separately from the final authenticity assessment.
Labels and stickers should be examined for placement, substrate, printing, edges, adhesive residue, and their relationship to the surface beneath them. A box label may identify a product number or distributor. A console label may identify a model or serial. Compare them without assuming that they were applied at the same stage. A genuine label may have been transferred. A missing label may reduce confidence without proving that the underlying box or console is false.
The console requires an independent comparison. Record shell form, seams, visible fasteners where relevant, label layout, model marking, connector arrangement, regional regulatory information, and serial label. The controller should be recorded by model, color or form, markings, connector, and quantity. Cables and power equipment should be recorded by model information, visible electrical markings, plug, and regional designation. These observations can expose a mixed package, but no single shell detail or connector should carry the entire authentication conclusion.
Sony’s service manual for the SCPH-5500, SCPH-5501, SCPH-5502, and related models documents model-specific specifications and supplied accessories. It is useful for comparing model and accessory differences. It is not, by itself, a complete retail-package contents manual. It does not establish every insert, tray, or factory configuration of every regional box. A box authentication assessment must therefore use package-specific evidence in addition to that service document.
Provenance can strengthen converging physical evidence. A contemporaneous receipt, retailer record, institutional accession, original ownership account, or documented chain of custody may explain why a box and console belong together. Provenance remains a source claim whose reliability should be considered, not a substitute for inspecting the objects. A confident seller description without independent records is still an assertion requiring verification.
A March 3, 2025 federal default-judgment order involving Nintendo-branded products illustrates the legal relevance of packaging deviations in a specific case. The court record included evidence concerning differences in products, packaging, and materials. That example shows that packaging can matter to a counterfeit claim. It does not create a universal collector standard, and it does not authorize a conclusion that every unusual box is counterfeit.
The legal record and collector taxonomy answer different questions. A court order establishes findings within its own parties, claims, evidence, and procedural posture. A collector may not possess equivalent manufacturing records or expert comparisons. The bounded lesson is that deviations can be probative in a particular case, not that one logo, fold, barcode, or paper feature settles every later authentication dispute.
Photographs are essential to an authentication review but remain limited evidence. They can preserve visible typography, labels, folds, materials, serials, and contradictions for comparison. They cannot by themselves establish provenance, manufacturing date, factory pairing, hidden alterations, or legal status. Authentication should therefore describe what the images support and identify the conclusions that require physical inspection, documentary comparison, or provenance.
Blurry images create a special risk because uncertainty is easily mistaken for agreement. An unreadable serial should remain unreadable. A logo that resembles a known design should be described as visually similar, not authenticated. If the back panel, inner structure, or power marking was not inspected, say so. The conclusion should not be stronger than the least-observed layer on which it depends.
A useful assessment may be graded rather than binary: box artwork and product identifiers appear consistent with the regional SKU; paper and folds require comparison; console model agrees with the box; power equipment is a later-region component; factory origin remains unverified. This format separates observations from interpretation and allows new evidence to change the assessment without rewriting the physical record.
Authentication is strongest when independent observations converge. Documentation supports the SKU; typography and identifiers fit the region; paper and board are consistent with the period; interior construction accommodates the listed contents; hardware and accessories match the model; and provenance explains the relationship. When those layers conflict, record a qualification or unresolved status rather than forcing certainty. A box can be plausible without being proven original.
Hardware, Accessories, and Substitution
A functioning accessory is not automatically an original package component. CIB collecting asks a historical question—what belonged to this retail SKU—not only a functional question—what allows the console to operate. A replacement controller, cable, adapter, RF unit, battery, game, or manual may preserve use while changing the package’s originality. The distinction should be explicit so that a working system is not represented as an original complete system without qualification.
Begin with the documented contents for the exact package. Sony’s service documentation identifies supplied accessories by model family and region, illustrating why a controller or cable should be compared with the relevant model rather than accepted by appearance. Sega’s 1993 catalog identifies the Genesis Core System’s control pad, AC adapter, and Auto RF Switchbox, while the Sonic the Hedgehog 2 package adds the cartridge. Accessory membership can therefore change with both region and bundle.
The controller should be recorded by model marking, color or form, connector, label, and quantity. A controller from the same platform may be genuine and period-correct while belonging to another package or later revision. An extra controller can be historically interesting without being required. If the documentation identifies one control pad, the presence of two does not improve the CIB claim; list the second as an extra unless package-specific evidence identifies a two-controller configuration.
Do not use color alone as an origin test. A matching color can support visual coherence, while a clearly different form or regional marking can expose a substitution. Neither observation is decisive by itself. Record the model and markings where available, then compare them with the identified SKU and region. If the accessory’s exact package membership cannot be established, use “period-correct replacement” or “origin unknown” rather than silently counting it as original.
Cables require the same treatment. Record whether the package documentation identifies an A/V cable, RF equipment, adapter lead, or another connection type. Note visible model information, connector arrangement, label, and regional characteristics. A cable that fits the console establishes compatibility, not original package membership. It may be a later replacement, a component from another market, or a third-party product. If its origin cannot be established, classify it as an unknown or compatible replacement.
Power equipment is both a functional component and a regional identifier. Record input and output markings, model number, rating, plug style, label, and market designation exactly as observed. A replacement with suitable specifications may allow use, but it should not be called original without evidence. A later-region component may also fit while contradicting the claimed retail package. The collecting conclusion should identify the component’s status without drifting into operational or repair guidance.
The RF switchbox provides a useful package distinction. If the period catalog identifies an Auto RF Switchbox as part of the Genesis Core System, that item belongs in the contents record for that SKU. A later cable that performs a similar connection function does not erase the original package requirement. Conversely, an RF switchbox associated with another regional package should not be imported into the Core System checklist without documentation connecting it to that package.
Bundled software is also part of the substitution problem. The Sonic the Hedgehog 2 system is not merely a Genesis with an optional cartridge nearby. The catalog identifies the game as part of that package. A genuine, period-correct cartridge placed inside a Core System box may be authentic software but not evidence that the box is the Sonic 2 retail bundle. The box product number, package title, artwork, and documented contents must agree.
Software can create the opposite error as well. A collector may possess the correct Sonic 2 cartridge and console but a box for the Core System. The hardware and game are individually genuine, yet the assembled package is mixed. Record the cartridge as present and its authenticity as documented or unresolved, while separately marking the box-package relationship as inconsistent or unresolved. Item authenticity and package completeness are independent fields.
Batteries and other consumables should be handled according to the source evidence. The U.S. Saturn package documentation identifies a battery among its contents. That establishes the battery category for the examined package, not the originality of every battery of the correct size. A replacement battery may be functionally equivalent while lacking package provenance. Record whether the documented item is present, replaced, installed, loose, or unresolved.
Printed matter can be substituted without changing basic operation. A modern manual, photocopy, reproduction warranty card, or manual from another region may explain how to use the console, but it does not necessarily belong to the original package. Classify the item by SKU relationship, not usefulness. A genuine manufacturer manual can still be the wrong manual for the identified model or market.
| Status | Meaning in a CIB record | Counted as original content? |
|---|---|---|
| Original | Evidence supports inclusion with the identified package | Yes |
| Period-correct replacement | Appropriate to the period, but not established as the supplied component | No |
| Compatible replacement | Fits or functions but lacks evidence of original package membership | No |
| Later-region component | Associated with another market, revision, or package | No |
| Reproduction | Later manufacture supported by comparative evidence or provenance | No |
| Unknown | Evidence cannot distinguish among possible origins | Not determined |
Optional accessories create another source of false completeness. A memory device, extra controller, carrying case, or peripheral may be shown in platform literature or sold during the same period. Unless the original SKU documentation identifies it as included, it remains outside the CIB contents list. Association with the platform is not inclusion in the box. An extra item should be recorded as an extra rather than allowed to obscure a missing documented component.
Physical condition can support a substitution inference but cannot prove package history. Matching wear, dust, or color may make a group appear coherent. A different regional label may expose a conflict. Age and appearance are not ownership records: a replacement can acquire similar wear, and an original component can remain unusually clean. State the observation first, then the limited conclusion it supports.
Manufacturer documentation should control where it exists. A manual that distinguishes supplied accessories from optional parts is stronger evidence than a marketplace photograph showing a crowded package. A catalog listing one controller and one adapter should not be overridden by a collector convention that treats an extra controller as mandatory. If documentation is silent, mark the item unresolved rather than promoting it to original status.
Measured fact: The observed power unit carries a model and regional marking that differ from the claimed package’s documented equipment. Source claim: The package documentation identifies a different supplied power component. Collector inference: The observed unit is a later-region or compatible replacement, not documented original content. This conclusion concerns package classification; it does not make a broader claim about the item’s legal status or practical use.
Functional substitution and historical substitution should remain separate throughout the ledger. A compatible replacement may preserve the system’s operation without preserving CIB originality. The record can state that the package contains a working replacement while also stating that the replacement is not counted as original. This is a classification distinction, not a judgment about ownership, repair, or preservation decisions.
The final contents assessment should identify every substitution that affects the claim. List the documented item, compare it with the observed component, assign a status, and note unresolved relationships. A package with the correct box, console, controller, power equipment, bundled software, printed matter, and documented structural pieces may support documented CIB. A package with a later-region adapter or reproduction manual may be visually complete but qualified. The useful conclusion is not simply what works; it is what is present, what belongs, and what the evidence can actually establish.
The Bundle Trap: Core, Pack-In, and Promotional Packages
A console bundle is not simply a system with an extra object placed beside it. It is a retail configuration with its own identity when the manufacturer assigned it a distinct title, item number, product number, box design, or documented contents. That distinction matters because two packages may contain nearly identical hardware while requiring different standards of completeness. A collector can possess an authentic console, controller, cable, power equipment, and box, then add a period game and describe the result as complete. Whether that description is accurate depends on the original SKU, not on the game’s age, compatibility, or visual relationship to the box.
The Sega 1993 product catalog supplies a useful controlled example. It distinguishes the Genesis Core System, item 1630, from the Sonic the Hedgehog 2 System, item 1614. The catalog describes the Sonic 2 package as including the cartridge, while the Core System is presented without a software cartridge. That is a documented difference between two retail products. It does not, by itself, establish every insert, tray, tie, bag, or regional variation associated with either box.
Source claim: Sega’s catalog identifies separate products and a different software allocation. Measured fact: a particular box, console, and cartridge carry the identifiers recorded from the objects. Collector inference: the objects may form a coherent bundle, provided that the regional, model, and package evidence does not contradict the conclusion. Keeping those three levels separate prevents one catalog entry from becoming a universal checklist.
In a hypothetical inspection, a collector finds a Genesis Core System box containing the correct console and controller, then places an authentic Sonic the Hedgehog 2 cartridge beside them. The cartridge may be historically appropriate, genuine, and desirable. It still does not transform the Core System box into the Sonic 2 System package. The reverse is equally important: a Sonic 2 System box without the documented cartridge is not complete merely because all of the hardware is present. The software’s authenticity and its membership in the original package are separate questions.
The collecting unit should therefore be recorded as a package identity: manufacturer, platform family, territory, product or item number, model or revision, language, electrical standard, and approximate period. “Genesis,” “Saturn,” or “PlayStation” identifies a family rather than one retail configuration. Within that family may be a core system, a software bundle, a revised hardware package, a regional electrical version, a color edition, or a promotional release. These products may share a console shell while requiring different content lists.
| Bundle field | What to record |
|---|---|
| Package identity | Printed title, item or product number, territory, language, model, revision, and approximate release window |
| Software status | Title, format, region, quantity, label or product reference, and whether inclusion is documented |
| Hardware and accessories | Console, controller quantity, cables, power equipment, adapters, RF equipment, and batteries |
| Printed and structural matter | Manuals, warranty cards, leaflets, stickers, trays, dividers, sleeves, and other documented pieces |
| Evidence status | Documented, measured, inferred, substituted, absent, contradictory, or unresolved |
A core system establishes the baseline package through its own evidence. It may include a console, one or more controllers, power equipment, video or RF equipment, manuals, safety material, and other documented contents. It does not automatically include software because the manufacturer advertised games alongside the system or because a setup manual discusses a game format. Software sold separately remains separate unless the package documentation identifies it as included.
A pack-in package changes the target. The cartridge, disc, or other software becomes part of the documented contents rather than an optional addition. Record the media by title, format, region, label, product reference, and any package-specific sleeve or manual. A loose copy of the same game may be genuine and period-correct while still failing to prove that it is the original pack-in. Several releases can share a title, artwork, or language while differing in region, printing, or package relationship.
Do not allow a product title to carry more information than the source supports. A catalog may distinguish two products and identify their principal hardware or software difference without listing every paper item inside the box. The correct conclusion is limited: the catalog proves that the products were treated as separate offerings and that the named game belonged to one of them. It does not become a universal completeness standard for every component inside those packages.
Box artwork must be read with product identifiers. A large platform logo may dominate the front while a smaller side-panel statement, barcode, or product sticker identifies the actual configuration. A game pictured on the box may indicate a promotional association rather than included software. Conversely, wording such as “includes” or a product title naming a game may provide stronger evidence of pack-in status. Photograph and transcribe every panel rather than selecting the interpretation that produces the fullest-looking package.
Later hardware revisions create another bundle error. A package may retain a familiar title while changing the console model, controller, power equipment, printed matter, or inner packaging. A newer console can be compatible with an older box and may even appear nearly identical. Compatibility does not establish package membership. Record the hardware revision independently, then ask whether that revision is documented for the product number, territory, and period being claimed.
Promotional packages require the same discipline. A manufacturer may have issued a special box, added software, changed artwork, or supplied a campaign-specific item. A genuine promotional SKU can require a different checklist from the ordinary core system. Establish that status with contemporaneous manufacturer or retailer documentation. A later sticker, seller description, or repeated collector attribution may be a useful lead, but it does not alone prove that a stable retail package existed.
Retailer and mail-order offers should remain a separate category. A retailer could ship a standard console box with a separately sold game or accessory as part of a temporary promotion. That transaction may have been historically real without creating a manufacturer-defined package. Unless contemporaneous documentation identifies the combination as a stable retail SKU, record it as a retailer bundle or sales arrangement. Do not merge the added item into the standard box’s original CIB checklist.
Physical arrangement can help distinguish these possibilities, but it cannot decide them by itself. In a hypothetical inspection, a standard console box has no documented cartridge cavity, while a specially printed bundle box contains a fitted compartment and package-specific artwork. Those observations may support different inferences about intended contents. They remain measured facts until a catalog, manual, package photograph, or comparable source establishes what the manufacturer supplied.
Sales tables provide context rather than package evidence. A company’s regional sales data can show that a platform or product family was sold in a territory and period. It cannot establish whether a particular box contained a cartridge, second controller, adapter, or promotional insert. A product family appearing in a market does not prove that every bundle variant appeared there. Keep sales context separate from the contents checklist.
Software substitutions deserve component-level descriptions. Identify whether the media is original to the claimed package, a separate retail copy, a later-region release, a compatible replacement, a reproduction, or of unknown origin. If the evidence proves only that a genuine game of the correct title is present, write exactly that. Do not upgrade “same title” to “original pack-in.” A precise entry such as “Core System box with separate Sonic 2 cartridge” is more useful than the attractive but unsupported phrase “complete Genesis.”
The final bundle assessment should state what is established and what remains unresolved. “Sonic the Hedgehog 2 System, cartridge present; package-specific insert status unresolved” is precise. “Genesis Core System with additional period Sonic 2 cartridge” is also precise. Both descriptions preserve the difference between an original bundle and a later assembly of related objects. The collector’s task is not to make every grouping fit a familiar label, but to preserve the identity of the package that was actually documented.
Institutional Catalogs and Retail Completeness
Museum and archival records are valuable to system collectors because they preserve object identity, provenance, dimensions, relationships, and historical context. They are not automatically factory packing lists. An institutional accession can document exactly what an organization received and chose to catalog while leaving unanswered whether those objects represent a complete original retail package. That limitation reflects a difference in purpose, not a defect in the record.
Retail CIB research asks what a manufacturer supplied in a particular SKU, territory, and period. Institutional cataloging asks what an accession contains, how its objects relate, where they came from, and why they merit preservation. The questions may overlap. A museum record can identify a box, console, booklet, or associated game. It can provide dimensions for comparison and provenance that a seller’s description lacks. It does not automatically convert the accession into a universal checklist for every example of that system.
Source claim: the Smithsonian National Museum of American History record for a Magnavox Odyssey documents a box, maker, date, accession information, and measurement. That establishes that the box is a catalogable historical object and that its physical dimensions were recorded. It does not establish every item originally supplied inside the box, the exact retail SKU represented, or whether all factory packaging materials survived with the accession.
Measured fact: a collector may measure an Odyssey box and compare the result with the institutional record. Collector inference: close agreement in dimensions and visible construction may support package identification. It remains an inference unless product identifiers, period documentation, or additional evidence establish the relationship more securely.
The Smithsonian’s NES record offers a related example. It identifies a console, instruction booklet, associated game, accession information, and physical measurements. That relationship is useful evidence about the particular object held by the institution. It may support the conclusion that those items were preserved or cataloged together. It does not prove that every NES package contained that game, that every regional box used the same materials, or that the accession arrived directly from a complete retail package.
The word associated should not silently become included. Objects can be associated because they were acquired together, donated by the same person, displayed together, or considered historically relevant to one accession. The institutional record may accurately describe the relationship while leaving factory packing unresolved. A collector should preserve the institution’s wording and identify any stronger conclusion as an inference.
Accession numbers can be stronger than seller descriptions for identifying a preserved object. They connect the record to an institution’s custody and cataloging process and may provide stable references, measurements, object relationships, and acquisition information. Their evidentiary strength has a boundary: an accession number identifies an institutional record, not a manufacturing or distribution event. It proves what the institution cataloged, not necessarily what a factory placed in a box.
A donated example can be both informative and easy to overgeneralize. A donor may have retained manuals, advertising matter, a console, and packaging that other owners discarded. The institution may catalog those objects as a coherent group. That demonstrates historical association and preservation value. It does not establish that the same combination was standard in all retail packages. The accession describes what survived in that particular case.
Institutional records may also preserve a broader historical field than the console itself. A library or archive can list platform titles, advertising materials, strategy guides, and other ephemera. Such a record demonstrates that software and printed material have historical significance. It does not mean that every listed advertisement, guide, or promotional sheet belonged inside the original console box. Preservation scope is wider than package scope.
Assign institutional sources a precise role in the evidence ledger. They may support object identity, maker, approximate date, dimensions, provenance, associated objects, and preservation status. They may provide a source claim about what an accession contains or a measured fact about a box. They should not automatically populate “documented original retail contents” unless the record itself, or a separate period source, establishes that relationship.
Dimensions are useful when handled cautiously. A recorded box measurement can expose a substantial mismatch or support identification of an approximate package family. It cannot authenticate the box alone. Different printings, regional packages, or packing configurations may share similar outer dimensions. Combine measurements with product numbers, artwork, language, labels, model information, and interior structure. If the dimensions correspond but the identifiers conflict, record the conflict rather than allowing size to decide the result.
Institutional photographs have a similarly limited scope. An image may reveal a tray, booklet, divider, or associated game from one accession. It shows what was documented in that example. It does not prove that the arrangement was factory-standard, untouched, or complete. Record the image as evidence of an observed institutional example, then label any broader conclusion as a collector inference.
Provenance has the same dual character. A documented donation can explain how an institution acquired a system and which objects arrived together. A receipt, family history, or contemporaneous account may strengthen the relationship among them. Yet provenance does not automatically eliminate later additions unless the chain of custody supports that conclusion. “Received together” is not necessarily equivalent to “packed together at manufacture.”
Institutional records may also preserve absence, but silence must be handled carefully. If an accession description identifies a console and booklet but does not mention a box, that may mean the box was absent or simply outside the cataloging scope. The appropriate entry is “not documented in the accession record,” followed by what the record does identify. Do not turn an omission into proof that an item was never present.
One accession cannot serve as a universal checklist because packages vary by region, revision, and period. A particular NES example with an associated game does not settle every NES package. A measured Odyssey box does not establish the interior architecture of all Odyssey boxes. An archive preserving advertising materials does not prove that those materials shipped with the console. Institutional examples are controlled observations, not manufacturer-wide standards.
The strongest research combines institutional and manufacturer evidence without asking either source to answer the other’s question. Manufacturer manuals and catalogs are generally stronger for SKU-specific contents when they actually identify the package. Institutional records are stronger for provenance, dimensions, object relationships, and preservation context. Physical inspection supplies measured facts from the collector’s example. Together, these sources can support a cautious package inference.
Consider a hypothetical inspection in which a collector’s console, booklet, and box resemble objects in a museum record, but the collector’s box has a different product label and the associated game is from another region. The institutional record may still be useful for comparative dimensions and construction. It cannot resolve the conflicting SKU evidence. The correct result is not a rejection of the museum record, but a narrower use of it.
A ledger entry might therefore read: “Institutional record documents a box of this maker and period with recorded dimensions. A separate accession identifies a console, booklet, and associated game. These records support the historical relevance of packaging and related objects but do not establish a universal retail checklist or factory pairing.” That wording preserves the value of the sources while preventing an accession-level observation from becoming a global rule.
Institutional catalogs are neither irrelevant nor decisive. They can be more reliable than seller descriptions for identifying and contextualizing a surviving object. They can reveal which packaging and ephemera deserve preservation. They can provide dimensions and relationships that make comparison possible. Retail CIB, however, remains a SKU-specific question. Use accession records to document the object that exists, then seek package evidence before claiming what the original retail package contained.
Legal Boundaries: Counterfeit, Reproduction, Restored, or Merely Incomplete
Collector terminology and legal terminology overlap without being interchangeable. “Counterfeit,” “reproduction,” “restored,” “incomplete,” and “substituted” answer different questions. A collector may use “reproduction” to identify a later-made insert, while a court may decide whether particular conduct created liability under trademark, copyright, false-designation, or related law. The presence of a reproduction does not automatically resolve the legal question, and a legal finding does not create a universal CIB grading standard.
Incomplete is the least legally loaded category. A package is incomplete when documented contents are missing or unresolved. A missing warranty card, tray, game, cable, or safety sheet may reduce completeness. It does not, by itself, indicate that any remaining item is counterfeit. A genuine original box with missing inserts is incomplete. A genuine console with a compatible replacement cable is substituted or qualified. Neither conclusion requires a legal finding.
Reproduction describes an item made later to imitate or replace an earlier item. A reproduction box, manual, label, warranty card, or tray may exist in a collection, but it must be disclosed and must not be counted as original. Whether a particular reproduction creates legal liability depends on facts outside ordinary visual classification, including branding, representations, commercial circumstances, and applicable law. Do not declare every reproduction unlawful or treat every later-made replacement as counterfeit.
Restored describes an object that has undergone intervention intended to preserve, repair, stabilize, or improve its condition. Restoration may affect a box, label, shell, tray, or printed matter. It does not automatically make the result counterfeit or non-original. A restored original and a reproduction are different categories, although restoration may include replacement material. Record what was changed, what remains original, and whether the account comes from documentation, observation, or inference.
Substitution means that one component has been replaced by another. The replacement may be original to the same SKU, period-correct but from another package, compatible, later-region, reproduction, or unknown. This is a collector classification. A later power unit or replacement manual should not be called counterfeit merely because it is not the component originally supplied. The package may instead be recorded as qualified, substituted, or incomplete.
Counterfeit should be used when converging physical and documentary evidence supports the collector’s authentication conclusion that an item was made or presented as an imitation rather than an authentic manufacturer product. That is a collector classification, not automatically a judicial finding. Reserve claims of legal liability, infringement, or statutory counterfeiting for the findings of a court or other competent legal authority. When the evidence is suggestive but incomplete, use narrower language such as “appears inconsistent with authentic material,” “probable reproduction,” or “origin unresolved.”
Procedural posture matters. An allegation is a party’s claim, not a judicial finding. A default judgment is a judgment entered after a party fails to defend, but its scope remains the scope of that case. Summary judgment resolves issues under the applicable legal standard and record; it does not necessarily answer every collector question. An injunction governs conduct within the case and parties covered by it. An appellate decision may affirm, reverse, vacate, or modify a lower-court result.
A March 3, 2025 order in Amazon.com, Inc. et al. v. Jing et al., Case C23-1641, in the United States District Court for the Western District of Washington, provides a recent, bounded example. The default judgment concerned counterfeit Nintendo-branded amiibo cards sold through Amazon, and the court’s discussion included deviations in authentic products’ packaging and materials. Its evidentiary lesson is analogical: packaging and material differences can matter in a case-specific authentication record. The order is not direct authority for deciding whether a retro-console box, manual, tray, or insert is authentic, complete, or legally counterfeit.
Historical Nintendo litigation supplies another bounded example. Nintendo v. Brown, decided by the Ninth Circuit in 1996, addressed false designation and trademark-counterfeiting issues involving Nintendo cartridges. Nintendo v. NTDEC, decided in the District of Arizona in 1993, involved counterfeit Nintendo cartridges, trademarks, and copyright-related relief. Nintendo v. Aeropower, decided by the Fourth Circuit in 1994, concerned counterfeit cartridges and related trademark relief, including issues surrounding damages and injunctive scope. These decisions should be summarized according to their holdings and procedural outcomes, not converted into a collector rulebook.
The distinction between a counterfeit good and an incomplete genuine good is fundamental. A genuine retail box missing its registration card remains a genuine but incomplete box unless other evidence indicates alteration or fabrication. A reproduction warranty card inside an otherwise genuine package may make the package non-original or qualified. Neither fact alone proves that the package as a whole is a legally counterfeit product. The collector’s classification should identify the component and the evidence.
Packaging deviations also require restraint. A wrong font, altered barcode, unusual fold, inconsistent product number, or unfamiliar paper may support an authenticity concern. It may also reflect a regional revision, later printing, repair, retailer handling, or incomplete comparison material. Measured fact: the observed item differs from the documented comparison in a specified way. Collector inference: the item appears inconsistent or its origin remains unknown. Do not leap from visual difference to legal status.
Do not treat a court order as a grading manual. Courts decide defined disputes using pleadings, evidence, procedure, and applicable law. They do not ordinarily determine whether a collector should call a package “qualified CIB,” whether a missing tray is material to completeness, or whether a period-correct replacement preserves originality. Those are collector-taxonomy questions. A court’s findings may inform them, but they do not replace SKU research and physical documentation.
Legal language should not inflate a marketplace description. A seller may call an item “original,” “factory,” or “authentic,” but those are source claims requiring verification. If a package includes undisclosed reproduction material, revise the CIB classification and document the discrepancy. Do not turn a seller’s overstatement into proof of intent or liability. The accurate statement may be no more than: “The seller described the insert as original; independent evidence does not establish that claim.”
Evidence should be kept in three layers. First, record the physical observation: a manual differs in paper, typography, language, product number, or fold. Second, state the supported collector inference: the manual appears to be a later replacement, another regional edition, or of unknown origin. Third, identify whether a legal authority is relevant: a cited decision found liability in a specific dispute, or no legal finding has been located for this object. This structure prevents legal vocabulary from replacing examination.
When a package is mixed, describe it component by component. The box may be genuine, the console may be appropriate to the region, the controller may be a later replacement, and the warranty card may be reproduced. Calling the whole assembly simply “counterfeit” obscures those distinctions. Calling it “complete” is equally misleading. Record the package as incomplete, substituted, restoration-affected, or authenticity-unresolved, depending on the evidence.
A responsible conclusion may be deliberately limited: “The insert is not supported as original and may be a reproduction; the package is therefore not documented CIB. No legal conclusion is drawn.” That sentence answers the collecting question without pretending to resolve trademark liability. If a court has entered a judgment concerning the goods, state the procedural result and case-specific scope rather than extending it to every similar-looking object.
The same discipline applies to restored packaging. A collector may disclose that a torn corner was repaired, a label was reattached, or an interior tray was reconstructed. Those interventions affect integrity and should be part of the record. They do not automatically transform an original box into a counterfeit. Conversely, a later-made box may be visually excellent and structurally accurate while still being a reproduction. Condition, restoration, and manufacturing origin must remain separate fields.
Legal boundaries protect accuracy in both directions. They prevent collectors from calling genuine but incomplete systems counterfeit, and they prevent reproduction packaging from being passed off as original merely because it fits. They also keep court decisions in their proper place: evidence about particular disputes, not universal definitions of CIB. The collector’s task is to classify the object precisely, preserve the evidence, and stop the claim where the record stops.
The Collector’s Evidence Ledger
A defensible CIB record should be reproducible by another collector who has the same documentation, photographs, and physical observations. The goal is not to describe an attractive box or produce a confident-sounding label. It is to document an identifiable package, distinguish evidence from interpretation, and preserve uncertainty where the record cannot resolve it. The ledger is a research tool, not a buying guide, price record, or declaration of certainty.
Begin the ledger with the complete identity header: manufacturer, platform family, territory, original SKU or product number, package title, console model, hardware revision, language, electrical standard, and approximate release window. Keep the retail product identifier separate from the console model. Record the basis for the regional assignment—such as box language, regulatory marks, model information, serial prefix, power specification, and documented accessories—without allowing color alone to determine the result.
Use the evidence labels locally and only where they clarify a new assertion: source claim for a named document or institutional record, measured fact for an observation from the inspected example, and collector inference for a conclusion drawn from those materials. The labels are ledger metadata, not a second general essay on method. Every important conclusion should show which underlying observations and sources support it.
| Ledger area | Minimum record |
|---|---|
| Identity | Manufacturer, platform, package title, SKU or product number, territory, language, electrical standard, model, revision, and date range |
| Package | Box panels, artwork, barcode, labels, product claims, dimensions, condition, restoration, and structural observations |
| Contents | Console, controllers, cables, power equipment, software, printed matter, inserts, and structural packaging |
| Identifiers | Console, box, receipt, warranty-card, barcode, model, product-number, and regional-prefix transcriptions, with legibility and location |
| Relationships | Matching, corresponding, conflicting, factory-paired, substituted, extra, or unresolved |
| Integrity | Provenance, repairs, restoration, reproduction concerns, contradictions, exclusions, and unresolved questions |
The box section should identify the front, back, sides, top, bottom, barcode, product labels, stickers, and visible package claims. Record whether the box appears to represent a core system, software bundle, revised package, promotional SKU, or retailer offer. If that classification is inferred rather than documented, say so. Note tears, repairs, fading, compression, replaced labels, and restoration separately from authenticity. Condition is not identity, and attractive presentation is not proof of originality.
The contents section should use a source checklist rather than memory. List the console, controller quantity, video or RF equipment, power equipment, batteries, bundled software, manuals, safety sheets, warranty and registration cards, catalogs, promotional leaflets, stickers, bags, ties, trays, dividers, foam, sleeves, endcaps, and inner cartons where relevant. For each item, use a status such as documented present, observed but undocumented, missing, replacement, extra, reproduction, later-region component, or unresolved.
Do not treat the category list itself as proof that every category belonged in the package. The U.S. Sega Saturn manual, for example, documents a console, controller, A/V cable, power cord, battery, sticker, warranty card, manual, and safeguards material for that examined U.S. package. It does not establish a universal requirement for every Saturn region or revision. For other packages, a tray, bag, tie, film, or spacer should be marked “not documented” until exact-SKU evidence or a documented physical comparison supports inclusion.
The box-identification record should preserve conflicts rather than resolve them by preference. If the front artwork suggests one bundle but the side label identifies another product number, photograph both and record the contradiction. If the barcode is consistent with the region but the console model is not, keep both facts visible. A collector inference may eventually favor one explanation, but the ledger should show the observations that led there and the evidence that remains inconsistent.
Serial fields should remain independent. Transcribe the console serial, box serial, warranty-card number, barcode, product number, model, and regional prefix exactly as displayed, preserving uncertain characters and recording each identifier’s location, label type, legibility, and condition. Use matching serials only when displayed strings agree; use corresponding serials when model, prefix, product, or regional information is consistent without identical numbers; and reserve factory-paired serials for manufacturer or distribution evidence that establishes the original pairing.
Nintendo’s support documentation states that a system serial number may appear on the box or receipt. That establishes a possible serial record, not proof that the box and console were factory paired. The NES Classic Edition example identifying “CU” for the Americas and “CEE” for Europe is limited to that product. It should not become a universal rule for older Nintendo systems, other manufacturers, or all regional prefixes.
Power specifications should be copied exactly as observed, including input and output markings, model information, plug type, and regional designation. Record whether the equipment is documented original, a period-correct replacement, compatible, later-region, reproduction, or unknown. A functioning replacement may preserve usability but not package originality. The same principle applies to controllers, A/V cables, RF equipment, batteries, bundled software, and printed matter.
| Status | Meaning for the ledger | Counted as original CIB content? |
|---|---|---|
| Original | Documented or strongly supported as supplied with the identified SKU | Yes, subject to the remaining package evidence |
| Period-correct replacement | Appropriate to the period but not established as the supplied component | No |
| Compatible replacement | Fits or functions but lacks evidence of original package membership | No |
| Later-region component | Associated with another market, revision, or package | No |
| Reproduction | Later manufacture supported by comparative evidence or provenance | No |
| Unknown | Evidence cannot distinguish among possible origins | Not determined |
Insert inventory should be granular. List the manual, safeguards sheet, warranty card, registration card, catalog, sticker, battery notice, promotional leaflet, and other documented items separately. Record title, language, model or product references, revision information, fold pattern, condition, and package status. Classify each item as documented original, observed but undocumented, replacement, extra, reproduction, later-region, missing, or unresolved. A disputed item receives a source note here rather than a repeated procedural explanation in every earlier chapter.
Structural packaging receives the same treatment. Record outer-box and accessible interior dimensions, tray or divider dimensions, foam shape, endcaps, inner cartons, sleeves, bags, restraints, protective films, and visible markings. Photograph each layer before rearranging the contents, and identify any surfaces that could not be inspected safely. A cavity is a measured fact; the proposed identity of the absent object is an inference unless package documentation confirms it.
Institutional examples belong in the ledger with a restricted role. A museum record may identify a box, console, booklet, associated game, accession, or measurement. The collector’s example may correspond or differ in dimension and construction. The institutional object may support historical context or package comparison. It does not automatically prove factory pairing, universal contents, or completeness of the collector’s example.
Provenance should identify where the object came from, who supplied the account, what documents accompany it, and whether the account describes receipt together or factory purchase. A receipt or institutional accession can strengthen identity and history. It does not automatically prove that every current component was packed together at manufacture. Use cautious language such as “received together,” “documented in one accession,” or “reported by a prior owner.”
Restoration and substitution notes should be explicit. Record repaired corners, reinforced folds, replaced labels, cleaned surfaces, reconstructed trays, copied inserts, swapped shells, later-region adapters, and unknown components. If an intervention is reported but not independently observed, label it as a provenance claim. If a component appears changed but the cause is unknown, record the observation without assigning intent. Restoration may preserve an original object while affecting integrity; it should not be collapsed into counterfeit status.
Use one consolidated capture set for the ledger: every box panel, barcode, product label, serial, product number, insert front and back, tray underside, connector, controller marking, cable end, power label, and representative overview of the arrangement. Preserve close views for text and construction, and note inaccessible or unexamined surfaces. Images document what was visible at a stated time; they do not establish hidden history, factory pairing, or legal status.
Assign a confidence level to each major conclusion, not only to the package as a whole. Identity confidence may be high while factory-pairing confidence is low. Hardware completeness may be well documented while insert completeness remains uncertain. Regional confidence may be strong while box authenticity remains unresolved. Explain the reason for each level. “Medium confidence” is not useful unless the record states which evidence supports it and which unanswered question prevents a stronger conclusion.
The unresolved-questions field is essential. List missing documentation, unreadable serial characters, uncertain bundle status, disputed tray structure, unknown power-equipment origin, possible reproduction inserts, conflicting regional clues, and unverified provenance. Do not erase uncertainty when a package looks convincing. A future catalog, manual, institutional record, or comparative example may resolve the question. The ledger should make that future work easier rather than hiding the gap.
Include a dedicated do-not-overclaim field. It might state: “Serials correspond but do not prove factory pairing”; “the box is consistent with the identified region but authenticity is not established from photographs alone”; “the game is genuine but pack-in status remains unresolved”; or “institutional records document an accession, not a universal retail checklist.” This field prevents later descriptions or database exports from shortening a careful conclusion into an unsupported absolute.
Optional accessories should be recorded as extras, not allowed to obscure missing documented components. A second controller, memory device, carrying case, or platform peripheral may be genuine, period-correct, and useful. Unless the original SKU documentation identifies it as included, it remains outside the CIB contents list. Association with the platform is not inclusion in the box.
The final assessment is a compact decision field rather than a repeated definition. Select Documented CIB, CIB with qualification required, or Complete-looking/incomplete, then state the limiting evidence in one sentence. The field should identify the package SKU, the missing or unresolved item, any substitution affecting the claim, and whether factory pairing or authenticity remains unverified. These grades describe evidence status, not value, desirability, or cosmetic condition.
The ledger should also record deliberate exclusions: separately sold accessories, compatible replacement cables, additional period games, later-region adapters, modern downloadable manuals, seller checklists, collector databases, and single unverified photographs do not populate the original contents list without package-specific support. Exclusion is a positive research decision and should be visible alongside the included items.
The ledger’s purpose is not to eliminate every uncertainty. Historical packages can survive incompletely, regional records can be uneven, and ownership histories can be undocumented. Its purpose is to show exactly where certainty ends. When another collector can reproduce the identity check, inspect the same photographs, compare the same source claims, and reach the same bounded conclusion, the record has done its job. A CIB system is strongest not when every question is forced into a yes-or-no answer, but when every unresolved question is preserved honestly.





