Foundry independence rule

Foundry independence rule

The customer must be able to run a delivered digital talent independently of the factory and independently of any specific LLM/tooling vendor.

How it constrains design

  • Deliverable is a portable artifact, not a hosted service. The contractual deliverable is what the customer can run themselves, not the factory-hosted instance. TFD-0019 §3
  • SaaS lock-in is rejected even when convenient. Atlassian Assets and headless CMS were considered for EA catalog storage and rejected because the customer cannot run the deliverable without the SaaS. TFD-0019 Alternatives
  • LLM flexibility required. Maya and any delivered talent must accept Anthropic-compatible local model endpoints, not hard-code a model. [memory: model-config-pattern]
  • Distribution mechanism (RD-0024 + RD-0031, TFD-0021) — .zip + --plugin-url install path, GitHub Releases for v1 with SHA256 integrity, so customers can install without factory infrastructure.

Tension with factory operations

During an active engagement, the factory does host live customer infrastructure (Cloudflare D1 + Pages per customer). Foundry rule applies to the delivered artifact, not the in-flight working environment. TFD-0019 §3

Post-delivery hosting question (whether/how long the factory keeps a customer's live site running) is deferred. TFD-0019 Open items

Linked