The canonical machine-readable claim ledger is evidence/claims.ndjson. It currently contains 85 version-bound records: 32 observed facts, 52 derived interpretations, and one explicit hypothesis. Sixteen observed claims come from isolated dynamic probes; the original static index remains 69 claims and 51 short semantic anchors. evidence/anchors.json maps those anchors within entry-module hash 45cb1eaa2b7e274ce87b1df0a1729f017ac06fffe782fac8acb42ab186243573.
Observed Claim container.bun-runtime-version records the literal embedded version string 1.3.14+2a41ca974, including its nine-character revision prefix, in provenance.json.
Derived Claim container.bun-runtime-source-resolution resolves that prefix to upstream commit 2a41ca974b7302952252a20eddbb3b5c3f2dee9b for the pinned source reference. The complete 40-character hash is not literally embedded. Both records are non-anchor claims and therefore do not add to the 51-anchor index below.
The tables below index anchor-scoped interpretations. The presence, count, and coordinates of each needle are observed. Unless a row is explicitly marked otherwise, its behavioral summary is derived and does not prove runtime activation. entrypoint.routing also participates in the ledger’s single architecture hypothesis. Offsets, occurrence counts, exact basis, and evidence references live in the machine-readable files.
An anchor supports only its written claim. For example, auth.macos-keychain proves a macOS Keychain command path exists; it does not prove what item attributes are used or that every credential is stored there. Derived architecture must cite multiple relevant anchors or CLI observations where needed.
If an anchor disappears in a new artifact, mark it unresolved before concluding the feature was removed. Minification, message changes, or a refactor can invalidate the needle while preserving behavior.