Bluefly Shared Platform & Product Map¶

Status: Canonical Platform & Architecture Standard
Authority: Live GitLab project verification, OSSA/DUADP specifications, Gas City runtime architecture, and Bluefly Engineering Standards.
Purpose: Authoritative inventory of shared agent assets, standards, operator tooling, governance, domain schemas, infrastructure, core products, and service convergence targets.

1. The Core Architecture Equation¶

================================================================================
LAYER                  AUTHORITATIVE COMPONENT
================================================================================
DEFINE                 OSSA
DISCOVER               DUADP
PACKAGE                AgenticTools
BROWSE                 Agentic Marketplace
AUTOMATE               BluCity Packs / Gas City Formulas
WORK                   Gas City + Beads
ATTEND                 CMUX
PERSIST                tmux
CONTEXT                ContextControl
HUMAN UI               Drupal / Canvas
AUTHORIZE              ContractPlane + Cedar
SOURCE                 GitLab
BUILD                  gitlab_components
DISTRIBUTE             GitLab Registries
VERIFY                 Dragonfly / Witness / framework tests
COMPOSE                agent-docker
PROVISION              IaC
RUN                    replaceable cloud/Linux compute
DURABILITY             NAS + tested backups
================================================================================

Operational Principle: A CMUX or tmux event is a signal, not authority. Event → wake BLU → re-read Gas City/Beads/GitLab/runtime truth → act.

That prevents us from replacing one pile of custom services with a new pile of clever event scripts.

2. Shared Agent Asset Frameworks & Ecosystem¶

AgenticTools¶

Repository: blueflyio/agentictools/agentictools
Role: The foundational standard library and dependency ecosystem for autonomous agent development.
Boundaries: AgenticTools is the framework and standard; Marketplace is the registry.

Agentic Marketplace¶

Repository: blueflyio/agent-platform/tools/agentic-marketplace
Role: Web-based catalog and registry UI (accessible at marketplace.blueflyagents.com) serving AgenticTools and OSSA-compliant agent packages.
Integration: Consumes DUADP discovery (discovery.duadp.org). Not a duplicate registry authority.

3. Agent Standards & Discovery¶

Open Standard Agents (OSSA) [FLAGSHIP]¶

Repository: blueflyio/ossa/openstandardagents
Role: Canonical specification and tooling for defining, validating, packaging, and deploying portable software agents.

DUADP (Decentralized Universal AI Discovery Protocol) [FLAGSHIP]¶

Repository: blueflyio/duadp/duadp
Role: The decentralized DNS and discovery layer for the AI agent ecosystem.

4. Operator Tooling & Execution Engine¶

Gas City Supervisor Execution Plane¶

Role: Central multi-agent process supervisor, dispatch engine, and event broker.
Automation Center: Gas City is the actual automation center handling formulas, packs, agents, sessions, Beads, events, orders, connected clients, and reusable factory behavior.
Events & Observability (gc events): Exposes typed HTTP and SSE streams (/v0/events/stream). Replaces external polling daemons with real-time event subscriptions.

CMUX (Attention & Event Plane)¶

Role: CMUX functions as the attention/event plane using its real hooks, Feed, reconnectable event streams (cmux events), notification hooks, and config-backed automation rules rather than terminal polling.
Function: CMUX can surface agent permissions/questions/plans and emits agent/Feed/browser/workspace events. Do not build another watcher; use CMUX primitives.

tmux (Remote Persistence)¶

Role: Remote terminal/session persistence with hooks/events/monitors used for low-level facts only, not as another scheduler.
Capabilities: tmux 3.8+ has first-class events, hooks, monitors, and wait-for -E. Agents must verify Oracle's installed version before depending on these capabilities.

BluCity Packs¶

Repository: blueflyio/blu/blucity-packs
Role: Canonical reusable Gas City Packs, formulas, orders, agent profiles, doctor checks, and factory capabilities.

5. Governance, Policies & Infrastructure¶

GitLab (Distribution & Refinery Plane)¶

Role: The distribution/refinery plane with a placement model for containers, Composer/npm/Python packages, Terraform modules, generic release bundles, and actual trained models via GitLab Registries.
Components: blueflyio/gitlab_components is the single reusable CI/CD implementation library. All estate projects consume components rather than duplicated pipeline scripts.

Cedar & ContractPlane (Authorization & Compliance)¶

Role: Cedar provides shared authorization policy libraries for runtime/application authorization. ContractPlane enforces it. Compliance Engine remains a focused compliance service without being casually deleted.

Agent Docker & IaC¶

Agent Docker: blueflyio/agent-platform/infra/agent-docker — Canonical runtime composition. Produces versioned, immutable OCI and config bundles.
IaC: blueflyio/agent-platform/infra/iac — Projects immutable platform releases onto target hosts (Oracle, AWS, Bare Metal).

6. Applications & Factory Products¶

ContextControl.ai & Drupal¶

Role: ContextControl and Drupal act as the sellable frontend over Gas City/Beads rather than another control plane.
Strategy: ContextControl and the Bluefly Factory — umbrella concept document; ContextControl is the commercial product and governed control surface, Contract Plane the authorization/assurance capability beneath it (not a second product).
Boundaries:
Drupal / ContextControl = Human & Customer Interface Plane (sellable UI).
Gas City = Backend Operator / Execution Plane.
Beads = Durable Work Graph.
GitLab = Source, Refinery, CI Release Train, Provenance.
Agent Brain = Now strictly vector/context plumbing via ContextControl.

Bluefly.io¶

Canonical Repository: blueflyio/assets/bluefly.io
Role: Production customer-facing web platform.

7. The Three Feedback Loops¶

Development Loop¶

Bead -> Gas City -> agent -> MR -> CI -> review -> merge -> next Bead

Runtime Loop¶

deployment -> observation -> finding -> Bead -> remediation -> redeploy -> re-observe

Learning Loop¶

execution evidence -> reviewed lesson -> ContextControl/shared skill -> next execution

8. What Bluefly Should Stop Owning (Negative Roadmap)¶

Stop owning	Prefer
custom agent router	Gas City dispatch/routing
custom workflow engine	Beads + formulas + events
separate "agent brain"	ContextControl + vector adapters + harness reasoning
duplicate policy stores	Cedar
duplicate policy integration	ContractPlane
generic LLM router	LiteLLM/OpenClaw where proven
duplicate telemetry stack	OpenTelemetry/OtterMon integration
custom CI in every repo	gitlab_components
private package copies in repos	GitLab registries
workstation-only operator scripts	blu-cli / governed projection
manual terminal polling	CMUX hooks/events + Gas City/GitLab events
manual "what next?" coordination	Beads readiness + Gas City dispatch

9. Repository Decision Matrix¶

Legacy / Source Repository	Decision	Target / Canonical Owner	Asset Type
`blueflyio/agent-router`	ARCHIVE	`blueflyio/blu/blucity-packs` (Gas City dispatch)	Infra
`blueflyio/workflow-engine`	ARCHIVE	`blueflyio/blu/blucity-packs` (Beads/Formulas)	Infra
`blueflyio/agent-brain`	MERGE	`blueflyio/context-control` (Vector/context plumbing)	Shared Library
`blueflyio/compliance-engine`	KEEP	Remains focused compliance service (ContractPlane SDK + Cedar)	Infra
`blueflyio/agent-mesh`	ARCHIVE	`blueflyio/duadp/duadp` + Agent Tailscale	Infra
`blueflyio/foundation-bridge`	ARCHIVE	LiteLLM / OpenClaw upstream	Infra
`blueflyio/agent-tracer`	ARCHIVE	OpenTelemetry / OtterMon	Infra
`blueflyio/node-agent-marketplace`	MERGE	`blueflyio/agent-platform/tools/agentic-marketplace`	Product
`blueflyio/technical-documentation`	MERGE	`blueflyio/blu/blucity-docs`	Documentation
`blueflyio/assets/bluefly.io`	KEEP	Live customer-facing platform	Product
`blueflyio/blu/blucity-packs`	KEEP	Gas City Automation & Capabilities	Shared Library
`blueflyio/blu/blucity-docs`	KEEP	Engineering Authority & Playbooks	Documentation