PC Builder and Compatibility Rules
Understand how part selection, product facts, compatibility checks and policy administration fit together across a PC build.
The PC Builder helps shoppers assemble a system from current products. It combines catalog eligibility, product facts, compatibility rules, and current commerce checks. Administrators use policy tools to manage rule sets, while product information managers maintain the specifications and evidence those rules rely on.
Seeing a product in a slot means it passed the current catalog screening for that request; it does not, by itself, confirm that the product fits every other selected part. An unresolved category may remain available while compatibility is pending, while a known wrong-family item is excluded. The system keeps these questions separate so it can give shoppers useful choices without overstating what the available evidence proves.
How the platform fits together
| Area | Responsibility | Example |
|---|---|---|
| Product catalog | Current product identity, category, price, availability and stock | Identifies a memory module and its current sellable state. |
| Product information management (PIM) | Structured specifications and their provenance | Stores DDR generation, socket, module format, capacity, dimensions and connectors with source and applicability context. |
| Compatibility rules | Typed conditions evaluated against selected products and facts | Checks whether a module's generation matches the motherboard's supported memory generation. |
| PC Builder | Part selection, quantities, saved configuration, comparison and recommendations | Adds a selected item to a slot and evaluates it in the context of the other choices. |
| Commerce | Current quote, cart and checkout eligibility | Rechecks price, stock, identity and applicable policy before purchase steps. |
| Admin policy tools | Drafting, validating, simulating, approving, publishing and rolling back rule policies | Changes a policy through an auditable workflow without changing the underlying PIM facts. |
These areas share data but retain separate authority: policy changes do not rewrite PIM facts, and saved builds must be rechecked because products, stock, prices or policies may change.
A shopper builds a system
A shopper can start from a preset or choose parts manually. The builder offers twelve selection slots: processor, motherboard, memory, graphics card, storage, power supply, case, cooling, operating system, display, keyboard and mouse, and audio. Some are optional. The shopper can compare products, adjust quantities, retain owned parts as fit context, freeze choices, undo or redo changes, reset, save or share a build, export it, request a quote and add purchase lines to the cart.
A picker request asks for products in one slot. The server derives tenant context and resolves current catalog data; client-submitted references do not supply trusted specifications. Filters can include publication, enabled state, positive price, valid stock and the requested category. The known-wrong-family category check runs before sorting and the final result limit, so a confirmed wrong-class item cannot occupy a displayed position. An unresolved category is not treated as a known negative and may remain visible while compatibility is pending. Price proximity or configured brand priority may affect ordering, but ranking is not compatibility proof.
When the shopper has already selected other parts, the builder can resolve those references and evaluate a candidate in context. A result can be eligible, pending or ineligible. A pending result asks for more trustworthy facts or review; it should not make the shopper guess a specification. A known negative check remains negative even when a different fact is unknown.
Slot eligibility and compatibility are different checks
Slot eligibility asks whether an item belongs in a requested component family. Compatibility asks whether the selected products satisfy the rules that apply to their combination. A memory card can be valid in a camera accessory flow while remaining outside the PC RAM category. Its brand or title is not needed to make that distinction; assigned category lineage is the authority. SSDs, HDDs and NVMe drives are common PC-storage examples, with interface and connector checks still applying.
The engine's source catalogue has ten class-eligibility families: CPU, motherboard, RAM, GPU, PSU, case, cooler, storage, display and accessory. The shopper UI has twelve selection slots. Those counts describe different layers. In particular, a UI slot does not automatically imply a one-to-one source rule template.
The category classifier uses the deepest recognized category in the assigned lineage. A memory-card leaf under a broad memory ancestor remains in the memory-card family; it must not inherit a broader RAM classification. A confirmed wrong-family assignment is excluded, while missing or unresolved category information is not itself proof of a mismatch and can remain available with a pending compatibility state. SSDs, HDDs and NVMe drives remain valid storage examples when their assigned categories and drive facts support them. No brand or product-title exception should be added to solve a category assignment problem.
A correct RAM category does not prove motherboard fit. DDR generation, module format, supported module class, module count, total capacity and CPU capacity are separate checks. The RAM slot rule should preserve legitimate SODIMM and other module formats when board and module facts support them; board-specific rules decide fit.
Reading compatibility outcomes
| Outcome | Meaning | Shopper or operator response |
|---|---|---|
| Pass for a check | Current, applicable evidence establishes the condition for that check. | Continue to other applicable checks; one pass is not a whole-build certificate. |
| Incompatible | Evidence establishes that the rule condition is false for the selected combination. | Correct the selection or governed product facts. A known negative must not be erased by an unrelated unknown. |
| Pending | Current evidence is missing, stale, malformed, ambiguous, conflicting or not adequately reviewed. | Keep the result unresolved and identify the fact or review needed. Pending is neither a pass nor proven incompatibility. |
| Advice | A recommendation or diagnostic that does not make a purchase ineligible. | Show useful guidance without converting it into a purchase block. |
A complete, valid evidence set can establish a particular check. If a board is verified as DDR4 and a memory module is verified as DDR5, the generation comparison is a known mismatch. An unknown CPU socket elsewhere does not change that result. If one side's DDR generation is missing or not verified, the comparison remains pending rather than guessing.
How component rules depend on one another
A rule evaluates only when the slots in its scope are present. Multiple checks can apply to the same selected product. The examples below describe rule relationships, not manufacturer-specific specifications.
| Relationship | Common checks | Evidence to maintain |
|---|---|---|
| CPU and motherboard | Socket match; soldered-CPU board exclusion | Exact socket and whether a board already includes a processor. |
| Memory and motherboard | DDR generation, module format and class, DIMM count and capacity | Supported generation and format, accepted module class, physical slots and capacity limits. |
| CPU and memory | CPU memory-capacity limit | CPU-supported maximum and installed total capacity. |
| Motherboard and case | Form factor and board cavity fit | Board footprint and supported case formats or explicit dimensions. |
| GPU, motherboard and case | Board slot count, GPU length/height, panel/cable space, radiator scenario and case openings | Exact card dimensions, usable board slots and the selected case/radiator arrangement. |
| Cooler, CPU, memory and case | Socket mount, thermal suitability, RAM overhang, cooler height and radiator/fan stack depth | Separate socket, heat and geometric facts. A thermal rating is not electrical power. |
| Storage and motherboard | M.2 presence, lane sharing and enabled SATA-port capacity | Drive interface/form factor, board lane configuration and enabled connectors. NVMe M.2 is not a SATA drive. |
| PSU, system and case | Continuous rating, native connector coverage and PSU dimensions | Electrical demand, connector type and PSU cavity dimensions. Preferred headroom is advice, not the minimum electrical check. |
| Headers and display path | Lighting voltage/header count, front-panel header and display output | Header pin/voltage details and whether CPU or GPU provides display output. Display-path guidance is advisory. |
Quantities and memory kits
Compatibility checks use the physical quantity selected, not just one representative item per slot. For example, if a memory kit contains two modules and the shopper selects quantity two, the configuration represents four physical modules. If each kit is 2 × 16 GB, that would represent four modules and 64 GB, subject to the board's supported generation, format, module class, slot count and total capacity. Quantity three would represent six modules and 96 GB; a four-slot board cannot fit six modules.
This arithmetic is illustrative. Advertised kit capacity may mean total capacity per package rather than per module. Confirm the catalog model before multiplying; if package composition is unclear, keep the capacity check pending.
Two SATA SSDs need two enabled SATA connections, plus the required mounting space and power connectors. The catalogue includes M.2 slot/lane-sharing and SATA-port rules; it does not list a separate drive-bay or SATA-power rule. An NVMe M.2 drive consumes a compatible M.2 slot and can share board lanes, so it should not be counted as a SATA drive.
Shared space and power
GPU and cooler clearances can share case space. A graphics card that fits without a front radiator may not fit in the selected radiator arrangement. Evaluate the GPU against the chosen radiator scenario and the radiator/fan stack against its case mount depth. Separately evaluate cooler height against the case limit and RAM height against the cooler overhang. Keep each measurement tied to its own geometry; do not reuse or subtract a margin twice.
The PSU electrical ledger compares component demand to the unit's continuous rating. Native connector coverage is a separate physical requirement. A preferred-headroom recommendation cannot be turned into a blocking rule by changing its wording. Thermal capacity concerns heat removal; wattage concerns electrical power.
Product facts and evidence in PIM
PIM stores facts used by compatibility checks, such as socket, DDR generation, memory format, supported capacity, case clearance, storage interface, ports, power demand and connectors. Each fact needs a defensible source and a clear scope. A correct value attached to the wrong product revision can still be unsafe to use.
Two evidence paths have different requirements:
| Evidence path | What supports a current fact | What is insufficient |
|---|---|---|
| Legacy revision path | A complete governed provenance record, a valid positive product revision, matching source applicability and a valid evidence path. | A provenance grade alone, a missing or mismatched revision, stale/imported-only data, or a source that does not apply to the product revision. |
| Current snapshot path | A validated current server read tied to the exact product and the applicable fact-source scope. | A serialized snapshot header, stale or incomplete capture, mixed identity or scope, or unsupported snapshot data. |
Category lineage is separate from a hardware specification. It can establish that an item belongs in RAM or storage without requiring a manufacturer datasheet, but it does not establish DDR generation or physical fit.
A legacy compatibility channel may use trained attributes, knowledge-base values and text-derived data as aids. A trained value is not automatically canonical evidence. Per-field validated overrides govern the documented hard socket and TDP checks in that legacy channel. In the structured evidence path, validated PIM facts and their source/applicability checks determine whether a value can support a rule. A product title, fuzzy match, image or source grade alone does not prove a physical fit.
When a required fact is missing or conflicts with another applicable value, keep the check pending. An operator should inspect the exact fact and source scope, correct the product record through governed PIM workflows, then rerun the evaluation. Do not change an unrelated rule to compensate for a data issue.
Rules and policy lifecycle
A rule has a stable identity and version, a category, severity, applicable slots, a typed condition and the required facts it consumes. The policy combines rule results without promoting an advice rule into a purchase gate.
Protected baselines preserve their identity and safety predicate. Normal policy tools can let an administrator add an existing protected template to a draft and configure only the fields allowed for that template. Protected identity and predicate are not freely editable. Validation checks the document and protected baseline invariants; draft save alone is not publication.
A typical administration workflow is:
- Create or open a draft. Start from the active policy, current templates or an empty draft, according to the available workflow.
- Add or edit a rule. Choose a typed template and configure its permitted fields while preserving stable identity and protected predicates.
- Validate. Resolve structural, semantic and protected-baseline issues before continuing.
- Simulate. Compare active and draft behavior on explicit fixtures and a bounded product sample. Review changed outcomes, pending rates and block deltas.
- Approve. Policies that can block purchases require the configured independent approval step.
- Publish. Publication applies the approved policy as the effective version; policy history and audit records make the change reviewable.
- Roll back if needed. Rollback points the active policy to a prior published version with an auditable reason; it does not rewrite the prior revision.
PIM edits and policy changes are separate operations. A fact correction should be reviewed in the product-data workflow. A policy change should use the policy lifecycle. Neither should be used as a shortcut for the other.
From picker to checkout
The shopper-facing journey contains multiple rechecks because catalog identity, stock, price and policy can change after a build is saved.
- Picker GET returns current candidates for a slot after category, catalog and availability filters.
- Picker POST resolves the selected references in the context of other choices and can annotate candidates with eligibility or pending information.
- Reference resolution accepts product IDs or exact SKUs and resolves them within the tenant. An unknown reference remains unknown; it should not silently become another product through a name match.
- Quote re-resolves parts and quantities and reports current exclusions, price/stock state and compatibility or verification status. A recommendation token is not a product guarantee.
- Save, share and export restore or re-resolve current components. If an item is no longer eligible or its identity changed, the saved build can require review; export requires a current eligible quote.
- Cart groups current line quantities with build context and rechecks catalog identity and applicable policy.
- Checkout checks signed build context against current data before reservation and order creation. When enforcement is enabled, proven incompatible builds are blocked and missing policy/evaluation authority fails closed. Pending evidence is surfaced rather than invented into a fit result.
When compatibility enforcement is in shadow mode, rule results are observed but do not themselves refuse purchase. Separate known taxonomy admission checks can still exclude a product from the wrong slot. These are different controls and should be described independently.
Troubleshooting
| What appears | What it usually means | Next step |
|---|---|---|
| A product is missing from a slot | It may be unpublished, disabled, unavailable, filtered by price or stock, outside the category query, in the wrong product family or beyond the bounded candidate set. | Check the product's assigned category lineage and current sellable/stock state. Do not add brand or title exceptions. |
| Compatibility is being confirmed | A needed fact may be missing, stale, ambiguous, conflicting or not adequately evidenced; policy coverage or read capability may also be incomplete. | Inspect the authorized diagnostics, then review the exact product fact and source scope. Keep the check pending until resolved. |
| A rule says incompatible | Current evaluated evidence establishes that the condition is false for this selection. | Confirm the exact product identities, quantities, hardware revision and evidence scope. Correct bad facts in PIM or change the selection. |
| A draft saves but cannot be published | Save, validation, simulation, approval and publication are separate stages. | Resolve validation issues, review simulation and use the configured approval workflow. |
| A known memory-card category is absent from the RAM picker | Its assigned category lineage places it in a different product family, even if a broad ancestor contains the word memory. | Keep the product in its correct category. Review the assigned category lineage rather than adding brand or title exceptions. |
| A quote says compatible while another check is pending | One rule or slot-resolution result may be positive while a different required fact still needs review. | Read compatibility, pending and verification fields together; do not treat one positive flag as whole-build certification. |
Source catalogue: 45 rule templates
This is the source catalogue inventory, not a statement that all 45 templates are active for every tenant. “Protected” describes the source baseline property. Severity advice is non-blocking; block rules have a blocking severity when present in an enforcing policy. Slot names are the template's applicability scope.
| Rule ID | Version | Catalogue title | Category | Severity | Protected | Applies to |
|---|---|---|---|---|---|---|
| cpu.slot.eligibility | 1 | Every cpu item belongs in the cpu slot | physical | block | Yes | cpu |
| motherboard.slot.eligibility | 1 | Every motherboard item belongs in the motherboard slot | physical | block | Yes | motherboard |
| ram.slot.eligibility | 1 | Every ram item belongs in the ram slot | physical | block | Yes | ram |
| gpu.slot.eligibility | 1 | Every gpu item belongs in the gpu slot | physical | block | Yes | gpu |
| psu.slot.eligibility | 1 | Every psu item belongs in the psu slot | physical | block | Yes | psu |
| case.slot.eligibility | 1 | Every case item belongs in the case slot | physical | block | Yes | case |
| cooler.slot.eligibility | 1 | Every cooler item belongs in the cooler slot | physical | block | Yes | cooler |
| storage.slot.eligibility | 1 | Every storage item belongs in the storage slot | physical | block | Yes | storage |
| display.slot.eligibility | 1 | Every display item belongs in the display slot | physical | block | Yes | display |
| accessory.slot.eligibility | 1 | Every accessory item belongs in the accessory slot | physical | block | Yes | accessory |
| cpu.socket.match | 1 | CPU socket matches motherboard socket | physical | block | Yes | cpu, motherboard |
| cpu.combo_board.exclusion | 1 | Combo board with soldered CPU cannot take a separate CPU | physical | block | No | cpu, motherboard |
| ram.ddr.match | 2 | RAM generation matches motherboard memory generation | physical | block | Yes | ram, motherboard |
| ram.dimm_format.match | 2 | RAM module format matches motherboard memory slots | physical | block | Yes | ram, motherboard |
| ram.module_class.support | 2 | Every RAM module class is explicitly accepted by the motherboard | physical | block | Yes | ram, motherboard |
| ram.dimm_slots.capacity | 2 | RAM module count and capacity fit the board | physical | block | Yes | ram, motherboard |
| ram.cpu_memory.capacity | 2 | Installed RAM capacity is within the CPU memory limit | physical | block | Yes | cpu, ram |
| motherboard.formfactor.case_fit | 1 | Motherboard form factor fits the case | physical | block | Yes | motherboard, case |
| motherboard.dimensions.case_cavity_fit | 1 | Board dimensions fit the case motherboard cavity | physical | block | No | motherboard, case |
| cooler.socket.support | 1 | Cooler mounting supports the CPU socket | physical | block | Yes | cooler, cpu |
| display.path.available | 1 | The build has a usable display output path (advice only — never a purchase block) | recommendation | advice | No | cpu, motherboard |
| cooler.thermal.suitability | 1 | Cooler thermal rating covers CPU heat output (advice only — thermal is never electrical) | recommendation | advice | Yes | cooler, cpu |
| cooler.ram.overhang | 1 | Tallest selected RAM module fits under the cooler overhang | physical | block | No | cooler, ram |
| cooler.height.clearance | 1 | Cooler height fits the case | physical | block | No | cooler, case |
| storage.m2.slot_presence | 2 | Board has enough M.2 slots for the selected M.2 drives | physical | block | Yes | motherboard, storage |
| storage.m2.sata_lane_sharing | 2 | M.2 lane sharing does not disable a needed SATA port | physical | block | Yes | motherboard, storage |
| storage.sata_port_capacity | 1 | Enough enabled SATA ports for selected drives | physical | block | Yes | motherboard, storage |
| gpu.length.clearance | 1 | GPU length fits the case | physical | block | No | gpu, case |
| gpu.radiator.scenario_fit | 1 | GPU fits with the mounted radiator scenario | physical | block | No | gpu, case |
| psu.capacity.sufficient | 1 | PSU continuous rating covers the electrical ledger | electrical | block | Yes | psu |
| psu.headroom.preferred | 1 | PSU keeps the preferred headroom above the ledger (advice only) | recommendation | advice | No | psu |
| psu.connector.coverage | 1 | PSU natively covers every required power connector | physical | block | Yes | psu |
| gpu.height.panel_clearance | 1 | GPU height fits the case side-panel opening (including cable room) | physical | block | No | gpu, case |
| psu.dimensions.case_fit | 1 | PSU body length fits the case PSU cavity | physical | block | No | psu, case |
| lighting.header.voltage_match | 1 | Peripheral lighting connectors match the board header voltage and count | electrical | block | No | motherboard, cooler |
| front_panel.header.compatibility | 1 | Case front-panel connector matches the motherboard header | physical | block | No | case, motherboard |
| cooler.purchase.recommendation | 1 | Suggest a cooler when none is included or selected (advice only) | recommendation | advice | No | cpu |
| ram.mixed_kit.advisory | 1 | Selected RAM kits share consistent specifications (advice only — never a purchase gate) | recommendation | advice | No | ram |
| motherboard.ram.qvl.positive_signal | 1 | Manufacturer Qualified Vendor List signal (advice only — absence never implies incompatibility) | recommendation | advice | No | motherboard, ram |
| gpu.slot_count.capacity | 1 | Board has enough physical x16 slots for the selected GPUs | physical | block | No | motherboard, gpu |
| gpu.multi.scaling_advisory | 1 | Multi-GPU performance scaling is advice only — never a purchase gate | recommendation | advice | No | gpu |
| cooler.radiator_fan.mount_depth | 1 | Radiator + fan stack fits the case mount depth | physical | block | No | cooler, case |
| case.gpu_expansion_slot_capacity | 1 | Case has enough expansion openings for the selected graphics cards | physical | block | Yes | case, gpu |
| motherboard.raid.drive_count_advisory | 1 | Selected drive count matches documented RAID support (advice only) | recommendation | advice | No | motherboard, storage |
| storage.boot_support.advisory | 1 | Selected drives are documented boot-capable (advice only) | recommendation | advice | No | storage |
Looking for a detailed walkthrough?
The companion guide includes one tenant-specific example and a deeper operational walkthrough.