Glossary¶

Terms used throughout BitAgent's documentation, code, and dashboard. Alphabetical.

A¶

`*arr` (or arr suite)¶

Collective name for Sonarr, Radarr, Lidarr, Readarr, Prowlarr — the family of self-hosted media managers BitAgent integrates with. BitAgent presents itself to them as a Torznab-compatible indexer. See Integrations.

B¶

BEP-5¶

BitTorrent Enhancement Proposal 5: the mainline DHT protocol. The Kademlia-style routing table BitAgent participates in to find peers without a tracker. Spec: bittorrent.org/beps/bep_0005.

BEP-9¶

BitTorrent Enhancement Proposal 9: extension for peers to send .torrent metadata files directly over a peer-to-peer connection. How BitAgent fetches metadata after discovering an infohash via the DHT.

BEP-51¶

BitTorrent Enhancement Proposal 51: DHT infohash indexing — the sample_infohashes RPC. The fast-path mechanism BitAgent uses to discover new infohashes from neighbouring DHT nodes.

bitagent-ui¶

The Python FastAPI dashboard. A separate repo / image from the Go core. Read-only relative to the core — never mutates indexing state directly; all writes go through the GraphQL API.

C¶

canonical label¶

A content-type label backed by ground-truth evidence — specifically, a successful *arr grab. Stored in the torrent_canonical_labels table. Preempts the CEL classifier when present.

CEL¶

Common Expression Language. Google's lightweight, sandboxed rules language. BitAgent's classifier rules are written in CEL and bundled in the binary. Inspect with bitagent classifier show.

classifier preempt¶

Short-circuit of the CEL classifier when a canonical label already exists for the infohash being processed. See concepts/classification.md.

content filter¶

Optional two-stage opt-in pipeline that drops torrents matching non-English / non-Latin / blocked-extension / NSFW criteria. Controlled by CONTENT_FILTER_ENABLED (shadow mode) and CONTENT_FILTER_ENFORCE (apply).

CSAM blocklist¶

Pre-fetch double-hashed bloom-filter defense against CSAM infohashes. Closes the swarm-touching exposure window for the one category where post-fetch detection is too late. See concepts/csam-defense.md.

D¶

DHT¶

Distributed Hash Table. The decentralised peer routing layer underpinning the public BitTorrent network. BitAgent's discovery layer.

dual-emit¶

The transition window during which every metric fires under both bitagent_* (primary) and bitmagnet_* (legacy) namespaces simultaneously. Started 2026-04-24. Allows operators to migrate dashboards/alerts at their own pace.

E¶

evidence¶

Webhook payloads from *arr Connect → Webhook entries (and the qBittorrent poller) that record successful grabs. Evidence is the ground truth that produces canonical labels. See evidence.md.

G¶

gqlgen¶

The Go GraphQL code generator BitAgent uses (internal/gql/gqlgen.yml). The schema lives in the core repo's graphql/schema/; resolvers in internal/gql/resolvers/.

H¶

Hash20¶

The GraphQL custom scalar for an infohash — 40 lowercase hex chars representing 20 bytes of SHA-1. Equivalent to the wire info_hash.

I¶

infohash¶

40-character hex SHA-1 identifying a unique torrent (the hash of its info dictionary). Sometimes written info_hash in DB columns or Hash20 in the GraphQL schema.

K¶

k-table¶

Kademlia routing table. The structured peer cache the DHT crawler maintains in memory. Buckets organised by shared-prefix-length with the crawler's own node ID.

L¶

LLM rerank stage¶

Optional final classifier stage that calls an external LLM for ambiguous torrents that CEL couldn't classify. Two-layer opt-in (Enabled + EnableLive), aggressively gated, sha256 LRU cached. See concepts/classification.md#stage-3-llm-rerank-stage.

O¶

P¶

peer¶

Any other DHT or BitTorrent node BitAgent talks to. Peer port: BITAGENT_PEER_PORT (default 3334).

preempt¶

See classifier preempt.

R¶

release¶

A versioned metadata snapshot of a torrent in the Postgres releases table. Multiple releases can coexist for one infohash if metadata is re-observed (e.g. seeder counts change).

retention¶

Pipeline that periodically deletes torrents the predicate considers long-dead. Two-stage opt-in (RETENTION_ENABLED, RETENTION_ENABLE_PURGE) so you can validate the dry-run trend before flipping to real deletes.

S¶

swarm¶

The set of peers participating in distributing a specific torrent (i.e. announcing they have or want pieces of one infohash).

T¶

TMDB¶

The Movie Database. Optional poster + metadata enrichment source for movie/TV releases. Activated by setting TMDB_API_KEY.

Torznab¶

The Newznab-derived API spec used by *arr clients to query indexers. BitAgent serves Torznab at /torznab/api. See reference/torznab-api.md.

W¶

wantbridge¶

BitAgent's active-acquisition layer. Biases the crawler toward indexing infohashes that match active operator-defined or *arr-derived wants. See concepts/wantbridge.md.

wants¶

Operator-defined search targets. Live in the wants table; managed via the dashboard's Wants tab. See wants.md.