Skip to content

AMCS Roadmap

Current execution directive: Founder Decisions in Engineering-Standard/glossary/platform-glossary.md plus Architecture.md. Ship the Drupal Launch Factory (two customer-shaped governed sites from site_template_amcs, no hand assembly) before marketplace / OSSA / Cedar / ContractPlane build-out. MASTER-PROMPT.md does not exist and must not be recreated.

The August 2026 Drive Roadmap.md still lists OSSA → Cedar → ContractPlane as the critical sequence. That is not the AMCS product roadmap. It is a later moat sequence and must not gate the Drupal vertical.

AMCS product sequence (now)

  1. Drupal CMS 2.1 + Drupal 11.4 as the product base.
  2. recipe_blucity — shared foundation (entities, Key, moderation primitives; later the composed Drupal AI contrib stack without drupal_cms_ai / Amazee).
  3. recipe_amcs — AMCS domain only (amcs_managed_article, roles, Content Moderation, FlowDrop ^2.5, bounded ECA, AI Context / Tool when required). Drop duplicate ai / ai_agents once the foundation provides them.
  4. site_template_amcs — installer-facing assembly. GitLab path: blueflyio/agent-platform/drupal/site-templates/amcs/site_template_amcs.
  5. Narrow vertical proof — draft → agent_qa → FlowDrop QA → needs_revision | human_review → authorized human publish. Failure + success + zero recursion. hq-b1m / hq-b1m.5.
  6. Customer #2 portability — a second independently created customer-shaped site from the same template, without Bluefly-specific copies. bluefly.io is a later reference consumer, not Customer #2 and not AMCS itself.
  7. Do not nest recipe_digital_service_baseline under AMCS. It is a sibling Site recipe.

Later moat sequence (not AMCS MVP)

These remain valid platform work. They do not define AMCS and must not block the vertical above.

  1. OSSA schema / Drupal OSSA import (ai_agents_ossa) as interoperability.
  2. DUADP discovery (discovery ≠ execution).
  3. Cedar / ContractPlane only when a concrete requirement and existing owner justify them.
  4. Marketplace packaging, if and when a real AMC schema exists (none is canonical today).

Delivery Phases

Phase 1: AMCS Launch Factory (active)

  • Goal: One reusable site template produces two governed Drupal sites. Narrow FlowDrop QA vertical proven from clean install.
  • Key Deliverable: site_template_amcs clean install + failure/success receipts. Not a "Hello Contract" OSSA demo.

Phase 2: Operate + reuse

  • Goal: Recurring assurance on the customer-owned Drupal service; expand only what repeats.
  • Key Deliverable: Operate retainer evidence, not a marketplace alpha.

Phase 3: Moat / federation (deferred)

  • Goal: OSSA/DUADP/Cedar/ContractPlane where they have owners and requirements.
  • Key Deliverable: Interop proof. Kagent remains an optional Drupal integration, not an AMCS deliverable. AMC Bundle v2 is blocked until a canonical schema exists.

Real-World Deliverables

ID Deliverable Purpose
D1 AMCS vertical + Launch Factory Prove recipe_blucity → recipe_amcs → site_template_amcs → two sites.
D2 Customer #2 portability Second site from the same template; no Bluefly-only forks.
D3 Moat adapters (later) OSSA/DUADP/evidence only after D1/D2, via existing owners.