Q: How do toolkit-catalog distribution, EA catalog storage, and rendering layer ownership interact for a digital talent delivery?

Q: How do toolkit-catalog distribution, EA catalog storage, and rendering layer ownership interact for a digital talent delivery?

Pulled from TFD-0019, TFD-0021, TFD-0022.

Short answer

Three orthogonal but composable layers, governed by the foundry independence rule and the single-owner principle:

Layer Concern Owner Decision
Content & rendering of framework artifacts (e.g. Macroscope A100/A230) What's in the deliverable + how it's rendered Francois TFD-0022
Customer-specific data storage (EA catalog) Where validated catalog data lives + how it's queried agent-ea pipeline + factory infrastructure TFD-0019 — per-customer Cloudflare D1 + Pages
Packaging & distribution of the talent itself How the bundle reaches the customer Pablo (convention) + Diego (release) TFD-0021 — toolkit-catalog bundle via GitHub Releases

How they compose for a real delivery (e.g. STM EA handover)

  1. Production-line Stage 4 build — Francois's rendering templates produce the Macroscope HTML artifacts (A100, A230, A280). Content authored by Elena per the EA mandate.
  2. Production-line Stage 5 emit — Pablo's bundle convention assembles the digital talent: agent + skills + hooks + .mcp.json + CONTEXT.md + README + (per TFD-0023) Maya wiki + /lint-wiki.
  3. Per-customer D1 export — wrangler d1 export produces a portable .sqlite + CSV bundle of the validated EA catalog. Foundry rule: this is the contractual deliverable, not the live factory-hosted instance.
  4. Diego packages and releases — .zip published to GitHub Releases with SHA256, install path --plugin-url.
  5. Customer installs and runs — independently of the factory, with the LLM of their choice (Anthropic-compatible endpoints).

Cross-cutting principles holding it together

  • Foundry independence — every layer's deliverable runs without the factory.
  • Customer data isolation — STM and Transgesco can never share infrastructure even if both delivered via the same bundle format.
  • Document-before-shipping — applies to TFD-0022 framework gabarits (spec before code) and TFD-0021 bundle convention (spike-first gate before broad retrofit).
  • Single-owner principle — each layer has a clear owner; operation and consumption can be distributed but ownership cannot fork.

What's still open

  • Post-delivery hosting (how long factory keeps customer's D1 + Pages running after handover) — deferred. TFD-0019 Open items
  • Custom-domain strategy per customer — deferred.
  • Plugin manifest security/signing — Pablo/Elena domain, separate work. TFD-0021 Actions §5
  • Maya M1 wiki contents at production scale — being validated in this sandbox.