Manifold
The model-provider switch
Where it stands. Built and in use: Crawl and Scribe already reach their models through it.
Manifold is not on a plane, it is the gateway at the estate’s edge to the external model market: the one contract every Tool on every plane routes its model calls through. That position is what lets Gimbal’s proposed remaps land as a config line rather than a rebuild.
A substrate member is called, never run. Everything below reads its declared contract at the moment it needs it, which is why it has no step of its own in any workflow.
- GimbalGates (proposes through)Gimbal's remaps are thrown through Manifold's switch; Manifold carries no allocation opinion of its own
- CrawlOperates (reference port)Crawl's original ModelProvider abstraction is the reference implementation Manifold generalised from
- ScribeOperates (adopted)Scribe's provider seam now routes through Manifold-shaped adapters (OpenRouter default, Moonshot rerouted)
- LatheOperates (genesis)Graduated Manifold from Crawl's one-off
- ConcordGatesA product hardcoding a vendor directly around Manifold is captured as open drift (DFT-018)
- PrismOperates (precedent)Prism's embedder seam is designed to graduate into Manifold once it grows an embedding contract
- Every deployed workflow's LLM-touching stepConsumesEstate law (the owner, 2026-07-20): every deployed workflow's model access runs through Manifold
Estate law (the owner, 2026-07-20): every deployed workflow's model access runs through Manifold. The workflows below are the ones that name it directly, the main ones, not an exhaustive account of everywhere that reach runs.