Gemini integration with a visible adapter boundary.
Gemini belongs in the integrations cluster with honest adapter boundaries and clear cross-links to cost and security. Teams can evaluate fit and usage without a one-size-fits-all control promise.
Keep the page tied to cost and security, not just runtime naming.
Describe Gemini as a runtime with visible boundaries.
Focus on where the control plane can observe or influence behavior.
Track how much the runtime is used and where spend can drift.
Keep the state you can prove separate from the state you only infer.
Call out what is still runtime-specific.
Bind the runtime to a repository or client boundary.
Use Gemini as part of the integrations cluster, not the whole story.
The page serves comparison and discovery, not encyclopedic overload.
A practical fit page is better than a fake parity promise.
How the control plane learns about usage and state.
Acknowledge the portions that remain external.
Keep the page connected to cost, security, and compare.