Technology Registry¶
Authority: Bluefly Engineering (hand-maintained) Scope: Underlying technical building blocks and standards approved for use across the Bluefly ecosystem. Excludes the operator/developer tools that use them (see tools.md) and the outcomes they enable (see capabilities.md). Status: Authoritative Last verified: 2026-09-02
Purpose¶
The canonical inventory of approved technologies within the Bluefly ecosystem.
Classification rules¶
- Status uses the shared catalog vocabulary:
Operating(approved and in active use),Planned(candidate, not yet approved for general use),Deprecated,Retired, orNot established. - A technology is not a Tool (tools.md) and not a Capability (capabilities.md) — it is the building block those two are composed from.
Catalog¶
| Technology | Domain | Status | Owner | Verified |
|---|---|---|---|---|
| Drupal | CMS / Backend | Operating | Platform Team | OBSERVED 2026-09-11: Drupal 11.4.6 / Drupal CMS 2.x — architecture: standards/drupal/drupal-standard.md; ecosystem registry: catalog/drupal-ai-ecosystem.md |
| Next.js | Frontend | Operating | Product Team | — |
| PostgreSQL | Database | Operating | Data Team | OBSERVED blueflynas 2026-08-05 (NAS = backup/restore/cache only, not hot Gas City state) |
| ClickHouse | Analytics DB | Operating | Data Team | OBSERVED blueflynas 2026-08-05 (NAS = backup/restore/cache only, not hot Gas City state) |
| Qdrant | Vector DB | Operating | agent-brain | OBSERVED blueflynas 2026-08-05. NOTE: QDRANT_CANONICAL_OWNER=agent-brain (Cedar policy confirmed). AGENT_STUDIO_OWNS_QDRANT=NO. 7+ duplicate Qdrant instances across the estate are a violation. |
| Redis | Caching | Operating | Platform Team | OBSERVED blueflynas 2026-08-05 (NAS = backup/restore/cache only, not hot Gas City state) |
| MinIO | Object Storage | Operating | Platform Team | OBSERVED blueflynas 2026-08-05 (NAS = backup/restore/cache only, not hot Gas City state) |
| Btrfs snapshots | Storage / DR | Operating | Platform Team | OBSERVED blueflynas 2026-08-05 (daily, 5 retained) |
| Tailscale | Network / VPN | Operating | Platform Team | OBSERVED blueflynas 2026-08-05 |
| Docker Compose | Container Orchestration | Operating | Platform Team | OBSERVED blueflynas 2026-08-05 |
| LM Studio | LLM Model Runner (Mac client of NAS LLM/; not a store) |
Operating | AI Team | OBSERVED 2026-09-02 — see inference-topology.md |
| Ollama (NAS) | On-prem inference at blueflynas.tailcf98b3.ts.net:11434 |
Operating | AI Team | OBSERVED 2026-09-02: qwen2.5:7b, qwen2.5:0.5b, nomic-embed-text; weights SoR /volume1/AgentPlatform/LLM |
| Tailscale Aperture | Northbound AI front door https://ai.tailcf98b3.ts.net/ |
Operating | Platform Team | OBSERVED HTTP 200 2026-09-02 — do not build another gateway |
| Cloudflare Tunnel | Networking | Operating | Platform Team | OBSERVED blueflynas 2026-08-05 |
| TailwindCSS | Styling | Operating | Frontend Team | — |
| 1Password | Secrets | Operating | Security Team | — |
| GitLab | SCM / CI | Operating | DevSecOps | — |
| Cedar | Policy | Operating | Security Team | — |
Relationships¶
Technologies are consumed by Tools (tools.md) and underpin Capabilities (capabilities.md). ARCH-001: Drupal (CMS/business authority) is an upstream system Bluefly composes over, not one Bluefly owns.
Governance¶
Adding a technology to Operating status requires an owning team (above) and a documented use in at least one product or platform. Do not add speculative/candidate technologies as Operating — use Planned.
Verification¶
Status values above reflect current known usage; no automated verification pipeline checks this table against actual dependency manifests yet. Treat this as hand-maintained, not automatically cross-checked until such tooling exists.