xbom.wiki

A living wiki for every bill of materials: software, hardware, data, models, media, policy, claims, energy, and provenance cut from the same artifact.

follow the vein

artifact

II

vein map

The artifact does not sit in a table. It opens like stone.

One object carries many inventories at once. The main vein traces the material path; branch veins expose dependency, lineage, license, owner, and version as geological facts instead of dashboard rows.

source → artifact → lineage → claim

III

SBOM

software strata

packages, build tools, firmware, transitive dependencies, release channels, hashes, maintainers.

HBOM

hardware strata

chips, boards, sensors, suppliers, factory lots, minerals, replacement tolerances.

DBOM / MBOM

data & model strata

datasets, weights, labels, prompts, licenses, evaluations, embedded policy constraints.

xBOM

IV

material choir

Software hums with silicon. Datasets echo legal claims. Energy leaves a pale seam.

The wiki treats bill-of-materials language as a choir, not a taxonomy war. A single page can hold dependency, source, artifact, media, license, model, policy, and risk without flattening them into one format.

componentdatasetmodellicenseenergyowner

V

provenance chamber

Every claim gets a shadow, a source, and a versioned cut mark.

xbom.wiki follows the evidence: who declared a component, which source substantiates it, when the artifact changed, and how risk travels through the vein when one ingredient fractures.

claim: declared source: observed owner: accountable version: cut-2026.05

VI

living glossary

A wiki of cuts, not a frozen dictionary.

Terms breathe as new inventories appear. The vein keeps expanding: new BOM types, new evidence practices, new domains, and new questions about what a thing is made from.

artifactmateriallineagesourceclaimxBOM