Skip to content

Repository Classification Standard

Source: Bluefly Native Gas City Transition Plan v1.0 Curated: 2026-07-23 from agent session evidence

Every repository under /Volumes/AgentPlatform/Applications and gitlab.com/blueflyio is classified into exactly one of the following architectural categories.

1. Packs (Reusable Capabilities & Config Packs)

Standard pack.toml configurations, agents, formulas, commands, and schemas:

  • Monorepos & Custom Packs: blucity-packs (monorepo of amcs, authority, bluefly-pack-seo, kingstown-core, lextown-criminal-core).
  • Infrastructure & Platform Packs: agent-docker (AI Gateway / LiteLLM pack), agent-tailscale (network mesh pack), security-policies (Cedar policy pack), gitlab_components (CI/CD components pack), cedar-policies / cedar_policy (Cedar schemas/policies).
  • Capability & Integration Packs: agent-brain, agent-buildkit, agent-mesh, agent-protocol, agent-router, agent-tracer, agentic-flows, compliance-engine (policy check pack), skills, skills_browser (tool packs), plugins (reusable helpers).
  • Local Substrate/Dev Packs: ddev-agent-blu, ddev-claude-drupal (local DDEV runtime packs).

2. Products (Composition of Packs)

Product configurations composing multiple reusable packs into customer-facing or internal endpoints:

  • Ecosystem Products: contextcontrol.ai (Active product), app.drupl.ai, marketplace-app.drupl.ai, agentblu.ai, agentdash_platform, demo_agentdash, alternative_services, duadp.org, duadp, ipk, indoorplantkingdom.com, sffedcu.
  • SaaS & Domain Products: dragonfly, dragonfly-saas (SaaS system).

3. Services & Tools (Shared Utilities, API Engines, & Gateways)

Long-lived gateway daemons, SDKs, and CLI controllers:

  • Agent Gateways & MCP: openclaw, mcp_gateway, gitlab-mcp-server, source_connector_mcp.
  • Command line & UI interfaces: blu-cli, blu-studio (visualizer over Gas City API), studio-ui, context-cli, dashboard.
  • Orchestrators & Workflow Engines: workflow-engine, playbook_engine, a2a-collector, agent_workflow_engine, gitlab-agent-orchestrator, blockchain_manager.
  • SDKs & Clients: contractplane-sdk, contractplane_client, dragonfly_client, duadp_client, duadp_client_drupal, ai_agents_client, copaw_bridge, agent_registry_consumer, agent_marketplace, ai_marketplace.
  • Isolate Code Execution: code_executor.
  • API Normalization & Metadata: api-schema-registry, api_normalization, apidog_integration, agent_api, agent_bootstrap_authority, kb_cache.

4. Infrastructure (IaC & Deployments)

Declarative environments and system configurations:

  • iac (Terraform & cloud-init config), ossa-deploy (OSSA deployment), deploy-oracle (Oracle deployment bindings), devops.

5. Documentation

Authoritative engineering and model guidelines:

  • blucity-docs / BluCity-Docs, blu-book, technical-docs.

6. Sandbox & Recipes (Reference implementations & Demos)

  • Frameworks & Themes: agentic_canvas_blocks, agentic_canvas_theme, contextcontrol_theme, bluefly_theme, bluefly-components, layout_system_converter, simple_age_gate, bluefly-assets.io.
  • Recipes: recipe_agent_platform, recipe_agentdash, recipe_ai_marketplace, recipe_amcs, recipe_contextual_memory, recipe_contractplane_intent, recipe_blucity, recipe_onboarding, recipe_secure_drupal.
  • Demos & Templates: demo_agent_marketplace, demo_agent_marketplace_drupal, project-template, master-template, cc_seed_content, site_template_amcs, moltbook, claude-desktop-agents.
  • Audit Tools: drupal_audit, drupal_patch_framework, repository-governor, rfp-automation, external_migration.

7. Archive (Deprecating / Retired)

  • cc.drupl.ai / cc-drupl-ai (Retired — superseded by contextcontrol.ai).
  • copaw / copaw-social-web / copaw-upstream (Retired / Archived).
  • agent-protocol.bak (redundant backup), apidog_integration_v1, agent-platform-security-policies (legacy repo).

Product Composition Map

Product Constituent Packs
ContextControl authority (Governance) + bluefly-security (Auth) + amcs (Knowledge/Drupal)
AMCS amcs (Drupal) + bluefly-pack-seo (SEO) + bluefly-gitlab (Workflow)

Governance Rule

A repository is never an architectural boundary. It is an implementation boundary. Every capability has exactly one authoritative Pack owner. Before creating a new repository, prove no existing Pack already owns the capability.