CLAUDE.md: Bluefly (projection of the Constitution)

Authority: BLUEFLY_CONSTITUTION.md. This file is generated; if it disagrees with the Constitution, the Constitution wins.

Mission

Bluefly exists to manufacture governed digital organizations.

The Axiom

Bluefly owns composition. Bluefly does not own implementation.

Axioms

• Bluefly owns composition. Bluefly does not own implementation.
• factory.yaml is the single source of truth; all outputs are generated and authoritative nowhere.
• Custom code is the last option. Exhaust Drupal, AGUI, MCP, Gas City, and existing Bluefly capability first.
• Bluefly ships Factories that produce Products, never technology. The customer buys a Product.

Authority Order (higher wins)

1 Bluefly Constitution 2 Product Contracts 3 Factory Contracts 4 Generated Outputs 5 Implementation Systems

If two documents disagree, the higher authority wins. Any document that contradicts the Constitution is wrong.

Architecture

PRODUCT -> FACTORY -> OUTPUTS -> DOMAINS -> SYSTEMS Rule: Product -> Factory -> Output -> Capability -> System Compile chain: Factory -> Pack -> Formula -> Order -> Agent -> Bead

Ownership (compose, don't implement)

Business authority: drupal · Execution: gas-city · Memory: contextcontrol · Contract: contractplane · Policy: cedar · Verification: dragonfly. Experience surfaces: Canvas(builder) · AGUI(user) · OpenClaw(operator) · Gas City Dashboard(admin). A2A = transport only.

Working rule

Before custom code, evaluate: drupal-core, drupal-cms, drupal-recipes, drupal-site-templates, drupal-ai, agui, mcp, gas-city, bluefly-existing. Never build: workflow-engines, schedulers, supervisors, orchestration-runtimes, chat-frameworks. Test any proposal: "Show me where this fits in the Constitution." If it can't be placed, it's off track.