Skip to content

Tool Registry

Authority: Bluefly Engineering (hand-maintained) Scope: Operator/developer-facing utilities. Excludes the underlying technologies they wrap (see technologies.md) and the capabilities they help deliver (see capabilities.md). Status: Authoritative Last verified: 2026-08-29

Purpose

The canonical inventory of approved engineering tools and utilities.

Classification rules

  • Status uses the shared catalog vocabulary: Operating (approved and in active use), Planned, Deprecated, Retired, or Not established.
  • Canonical CLI name is blu-cli (blu binary) — never bcli.

Catalog

Tool Purpose Authority Status
nas-archivist NAS Repository Steward (design, skill) Platform Team Operating
agy Antigravity CLI AI Team Operating
qmd Knowledge Retrieval AI Team Operating
blu (blu-cli) Bluefly Operator Platform Team Operating
op 1Password CLI Security Team Operating
git Version Control Platform Team Operating
codegraph Code Exploration Platform Team Operating
cedar Policy Engine Security Team Operating
source_connect Site Discovery Platform Team Operating
gc (Gas City CLI) Multi-agent orchestration — Gas City is the execution plane. NOTE: agent-platform/services/* under consolidation review (Gas City replaces most) Platform Team Operating
bd (Beads) Durable work-item / issue tracker. NOTE: All hq-* bead IDs are unverified — authoritative prefix is UNKNOWN. Platform Team Operating
context (@bluefly/context-cli) Context/memory retrieval CLI — distinct from blu-cli and agent-buildkit AI Team Operating
buildkit (@bluefly/agent-buildkit) FS/git/test/release operations CLI. NOTE: packet.manifest.json is the existing release manifest (not platform.manifest.v1) Platform Team Operating

qmd usage pattern

qmd (v2.5.3+) is the primary agent knowledge-retrieval tool (qmd://blucity-docs collection). Use before grep or direct file reads for cross-cutting questions across BluCity-Docs.

qmd query "Gas City formula step graph"        # hybrid + reranking
qmd search "named sessions"                    # BM25 keyword
qmd vsearch "city topology binding"            # semantic
qmd get "catalog/gc-orders.md"                 # exact document
qmd status                                     # index health

Agents should run qmd status first to confirm the index is current before relying on results.

Relationships

Tools wrap Technologies (technologies.md) and are consumed to implement Capabilities (capabilities.md). A tool is not itself a capability.

Governance

Adding a tool to Operating status requires an owning team (above) and a documented active use. Retired tools should move to Retired, not be deleted from this table, so historical ownership stays traceable.

Verification

Status values above reflect current known usage; no automated verification pipeline checks this table yet. Treat this as hand-maintained, not automatically cross-checked until such tooling exists.

Adoption notes

Tool Adoption Consumers Notes
blu (blu-cli) ADOPTED Operators / agent sessions Tags present (v0.3.x); not CONVERGED
context (@bluefly/context-cli) BUILT Blob refs in group RELEASED unknown until semver tag or registry publish proof
glab ADOPTED CI + operator workstation Auth via 1Password-injected GITLAB_TOKEN; no keyring drift