Worked examples for standardized, vendor-neutral IaaS APIs on Platform Mesh: a consumer orders against one generic API, and the resource-broker routes the order to a matching provider by capability/policy — the "API extraction" idea made concrete.
How an order crosses from the generic API into a provider's API (and where fields actually get mapped) is documented in generic-to-provider-api.md.
The example providers live in providers/, one cloud provider per directory.
Resources installed into the provider workspace go into providers/<provider>/manifests/.
The broker and platform setup happens in platform/.
The example resources deployed for the consumer are in consumer/.
The generic API and coordination CRDs are vendored under config/.
The consumer's binding and order are in consumer/.
kind/manifests/ holds the floci fake-cloud storage backends.
The overarching play-by-play resource changes are documented in DEMO.md.