AGENTS.md: Bluefly agent operating rules (projection of the Constitution)¶
Authority: BLUEFLY_CONSTITUTION.md (supreme). Conform; never redefine.
Non-negotiable 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¶
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.
What you may not do¶
- Do not build: workflow-engines, schedulers, supervisors, orchestration-runtimes, chat-frameworks.
- Do not replace AGUI, collapse the four experience surfaces, or give A2A authority.
- Do not hand-edit a generated output into authority. Regenerate from the contract.
- Do not redefine the Constitution. Nothing may redefine the Constitution. Products conform to it. Factories conform to it. Agents conform to it. Documentation conforms to it. Generated artifacts conform to it.
How to act¶
- Compose upstreams first (drupal-core, drupal-cms, drupal-recipes, drupal-site-templates, drupal-ai, agui, mcp, gas-city, bluefly-existing).
- Express every feature as Product -> Factory -> Output -> Capability -> System.
- Factory (Factory -> Pack -> Formula -> Order -> Agent -> Bead): Bluefly owns Factory; Gas City owns below.
- Operator API is blu-cli.