AMCS Vision¶
Current execution directive: Founder Decisions in
Engineering-Standard/glossary/platform-glossary.md plus
Architecture.md on release/v0.1.x. Near-term product is
the Bluefly Drupal Launch Factory, demonstrated through AMCS: two
customer-shaped governed Drupal sites from one reusable
site_template_amcs, with no hand assembly. MASTER-PROMPT.md does not
exist and must not be recreated.
The commercial definition of AMCS — buyer, what the customer buys,
positioning, packaging, pricing logic, go-to-market, unit economics, north-star
metric and kill criteria — is
Product-Definition.md. This file owns the product
thesis; that file owns the commercial definition;
Architecture.md owns the technical architecture.
Do not collapse these identities:
- AMCS is not
bluefly.io(that site is a later reference consumer). - AMCS is not Gas City (Gas City manufactures the product; Drupal runs it).
- AMCS is not AMCS-CF-001 (that packet is a certification/proof slice).
- AMCS is not one editorial FlowDrop workflow (FlowDrop is the QA pipeline inside the domain recipe, not the product definition).
The August 2026 Drive copies of this file, Roadmap.md, and Architecture.md
are historical. They still sequence OSSA → Cedar → ContractPlane as if that
were the AMCS MVP. Current GitLab Architecture.md replaced that four-plane
model. Do not promote Drive copies over release/v0.1.x.
Product Thesis¶
Bluefly sells governed modernization outcomes: a customer-owned Drupal service, acceptance evidence, and recurring assurance. Bluefly does not sell Gas City, Beads, agents, formulas, tokens, or engineering orchestration. Those remain private factory machinery.
AMCS is the Drupal modernization / product-factory capability above any one
demonstration. It is assembled from existing owners only:
recipe_blucity (shared foundation) → recipe_amcs (AMCS domain) →
site_template_amcs (installer-facing product).
OSSA, DUADP, ContractPlane, Cedar, and ContextControl remain the longer-horizon moat and interoperability layer. They are not prerequisites for the AMCS vertical, and they are not what the customer buys first.
Bluefly Value Layer (Durable IP)¶
| Product Surface | Role now | Not this |
|---|---|---|
| AMCS (Drupal product) | Customer-facing governed Drupal CMS: recipes, site template, Content Moderation, FlowDrop QA, least-privilege agent roles. | Not a marketplace engine. Not Gas City. |
| Gas City / Beads | Private factory: how Bluefly manufactures, tests, and releases the Drupal product. | Not a sellable orchestrator. |
| OSSA / DUADP | Portable agent contract and discovery. Moat / later federation. | Not Drupal content authority. No canonical AMC schema exists to require. |
| ContractPlane / Cedar | Optional external evidence / ABAC when a concrete requirement and owner exist. | Not the default AMCS proof ledger. Drupal revisions, moderation history, FlowDrop records, and GitLab CI are the baseline. |
| ContextControl | Organizational learning product, separate from AMCS. | Not the AMCS content model. |
Infrastructure Dependencies (Interchangeable)¶
In-Drupal runtime is contrib, not Kagent/LiteLLM/agentgateway as architecture.
| Commodity Concern | Canonical Dependency |
|---|---|
| LLM Provider Abstraction | drupal/ai (\Drupal::service('ai.provider') — no direct SDK calls). Never drupal/drupal_cms_ai or ai_provider_amazeeio. |
| Agent Runtime | drupal/ai_agents |
| Typed Execution Contract | drupal/tool + drupal/tool_belt (maturity-gated) |
| External/Agent Tool Access | drupal/mcp_server / drupal/mcp_client only where required |
| Event-Driven Automation | drupal/eca (bounded reactions, not the QA graph) |
| Multi-Step Pipelines | drupal/flowdrop ^2.5 |
| Observability | OpenTelemetry + Grafana |
| Orchestration (factory/build, not runtime) | Gas City (Gas Town is a pack/configuration, not a second runtime) |
Core Operating Rule¶
Customers buy modernization outcomes, evidence, ownership, and recurring assurance. Bluefly does not sell commodity LLM routers, agent runtimes, tracing systems, service meshes, or Gas City seats.
Custom Drupal code is last. Prefer delete, then upstream, then configuration / Recipe / ECA / FlowDrop / existing Bluefly owner.