Mint · Integration authors
Realize a capability. Do not take apply.
An integration is how Mint realizes a promise for a service. Execute stays fail-closed unless a privileged runtime is allowed. Protocol and authoring live on mint.opsdevco.de/reference— this page is the company adoption path, not the spec.
Authoring plus conformanceIntegration Protocol v0
Problem
Service adapters often ship with implied apply. Reviewers cannot tell observation from mutation. A Marketplace listing is not the contract.
Benefit
Contributions are a manifest, a stdio protocol server, fixtures, and fail-closed execute. Catalog records bind digest pins. Standalone wheels are GitHub Releases, not PyPI.
Directory
Official records live in the immutable mint-registry v0.2.0-alpha.0 snapshot. Cache that tag with mint integrations update --registry. Offline search against an already-cached catalog is not a registry refresh. There is no hosted registry service. The company integrations listing, when generated, stays owned by mint-registry — this journey does not recreate it.
No Kubernetes snapshot integration. No live AWS, Azure, GCP, GitHub, or SaaS mutation from Mint.