BKU008 / STANDARDS + ASSEMBLY EVIDENCE

Standards identify requirements. They do not issue verdicts.

BKU007 normalizes a bounded set of high-value bicycle interfaces and ties them to exact official product evidence. Matching names, dimensions or neighboring graph nodes never become a compatibility guarantee.

Compatibility boundary: established means only that a loaded source establishes that requirement at its stated scope. Missing or unknown remains unresolved. No transitive inference is allowed.

01 / NORMALIZE

Eight source-backed standard/interface nodes.

Driver bodies, rotor mounting, brake-caliper mounting, axle systems, derailleur/frame mounting and tyre/rim dimensional references are modeled separately from products.

SOURCE-BACKED

freehub driver

SRAM XD driver interface

Cassette-to-driver mounting interface described by SRAM for mountain-bike applications and 10-tooth-start cassettes.

Maintainer: SRAM
Evidence: bku.evidence.sram.xd-xdr-explained

Verification boundary

Shared XD naming is not enough to certify a cassette/hub pair. Exact product evidence remains required.

SOURCE-BACKED

freehub driver

SRAM XDR driver interface

Road-oriented cassette-to-driver interface that SRAM states is 1.85 mm longer than XD.

Maintainer: SRAM
Evidence: bku.evidence.sram.xd-xdr-explained · bku.evidence.sram.xdr-driver-service

Verification boundary

The general XD/XDR rule does not identify the hub, wheel, cassette generation or installation procedure.

SOURCE-BACKED

freehub driver

Shimano MICRO SPLINE

Shimano freehub/cassette spline interface associated with 10-tooth smallest sprockets.

Maintainer: Shimano
Evidence: bku.evidence.shimano.micro-spline

Verification boundary

BKU does not infer MICRO SPLINE compatibility from cassette speed count alone.

SOURCE-BACKED

brake rotor mount

Shimano CENTER LOCK

Disc-rotor-to-hub mounting system using a spline mount and lock ring.

Maintainer: Shimano
Evidence: bku.evidence.shimano.center-lock · bku.evidence.shimano.rt-mt800-official

Verification boundary

A CENTER LOCK label is an interface identity, not a blanket rotor/brake-system compatibility statement.

SOURCE-BACKED

brake caliper mount

Shimano Flat Mount brake interface

Low-profile disc-brake caliper mounting interface identified by Shimano on Flat Mount caliper products.

Maintainer: Shimano
Evidence: bku.evidence.shimano.br-rx820-official

Verification boundary

Mount-family identity does not certify rotor size, adapter stack, fasteners or return-to-use safety.

SOURCE-BACKED

axle

Shimano E-THRU axle system

Shimano thru-axle system with road and MTB diameter families documented by Shimano.

Maintainer: Shimano
Evidence: bku.evidence.shimano.e-thru

Verification boundary

Diameter family alone is not a complete axle compatibility record; exact length/thread/frame/hub identity still matters.

SOURCE-BACKED

derailleur frame mount

SRAM Universal Derailleur Hanger (UDH)

Standardized rear-derailleur-hanger/frame interface used on frames designed for UDH and forming the basis for Full Mount frame interfaces.

Maintainer: SRAM
Evidence: bku.evidence.sram.udh-overview · bku.evidence.sram.udh-service

Verification boundary

UDH does not fit every frame. Exact frame identity and current frame-fit documentation remain required.

SOURCE-BACKED

tire rim

ETRTO cycle tyre / rim dimensional reference

Standards-body reference system for cycle tyres and rims, including size designation, dimensions and recommended rim-width material in ETRTO publications.

Maintainer: ETRTO
Evidence: bku.evidence.etrto.cycle-tyre-rim-standards

Verification boundary

BKU007 does not reproduce paid/proprietary tables and therefore does not certify an exact tyre/rim pair from category naming alone.

02 / REQUIREMENT INSPECTOR

See the exact requirement state, not a green compatibility badge.

Choose a bounded evidence case. BKU reports every requirement as established, missing, stale, conflicting or unknown and preserves zero-count states honestly.

Evidence case

Loading exact requirement states…

NO TRANSITIVE INFERENCEA↔B and B↔C never creates A↔C. Shared manufacturer, speed count, mount family or nominal dimension is not pair certification.

03 / STATE AUDIT

Zero stale. Zero conflicting. Those states still exist.

The current requirement audit contains no stale or exact-scope conflicting standards records. BKU exposes those states because future evidence can age or disagree; it does not fabricate examples.

7ESTABLISHED

5MISSING

6UNKNOWN

0STALE

0CONFLICTING

04 / TRACE

From standard identity back to exact evidence.

Standards are graph nodes. Exact products declare standards only where official product sources do so. Procedure, torque, installation and safe-to-ride decisions stay outside this layer.

Assembly requirement inspectorInspect bounded multi-component research gaps.Product evidenceInspect exact source-backed product fields.Generic interfacesSee the component questions around each standard.WorkshopTrace observation → mechanism → interface → authoritative procedure gate.Graph explorerFollow incoming and outgoing typed edges.

BKU010 / RESEARCH PATHS

Standards can now be entered from a specific evidence gap.

The new navigator explains why a standard is relevant while preserving the rule that a shared standard never becomes a compatibility guarantee.

Research PathsStart from a missing or unknown audited requirement.Assembly EvidenceInspect the underlying audited set.

ICU-EXPEDITION-025 / EVIDENCE SNAPSHOT

Dates and availability belong beside the claim scope.

The active Bikes evidence records in this candidate are a supplied snapshot, not live web checks. The R000013 evidence ledger records source access on 2026-09-10, and the availability review records checks on 2026-09-11. Source-access dates, availability-review dates, next-review dates, blocked states and scope-review states stay visible so a reachable URL is never treated as automatic proof that a claim is still current.

Inspect availability states · Inspect freshness queue · Save a verification handoff

ICU / CONNECTED DISCOVERY

Continue through related ideas.

These are bounded editorial connections; paid placement does not influence them.

Loading public connections…

See reverse connections