Using it
Once connected, just ask your assistant questions in natural language. The gateway works best for questions about how the platform works and what's available — getting started, environment setup, deployment and promotion, and the archetype catalog.
Ask the way you'd ask a teammate. Mention the gateway by name if your assistant has other tools available — e.g. "Using the knowledge gateway, ..." — so it knows where to look.
Questions that work well
Each of these returns real platform documentation today:
"How do I onboard a new developer to the platform?" Returns the onboarding walkthrough — workstation setup, cloning a project, configuring your local environment, and making a first contribution.
"What are the prerequisites for setting up my dev environment?" Returns the required tools and workstation setup, including containerized local development.
"How do I promote a release to an environment?"
Explains the promotion model — the same image digest that passed in DEV is
promoted to PRD via a manifest dispatch that ArgoCD/Kargo syncs — and points at
the release-promote-to-environment action that does it.
"How do I create a new Python service?"
Points you at the right platform archetype and the archetect command to
scaffold it — e.g. the Python REST or gRPC service templates — so you start from
a production-ready project instead of an empty repo.
Tips
- Ask follow-ups. The gateway can read the full documents it finds, so drill in: "Show me the workstation setup steps for macOS."
- Be specific about the topic, not the file. You don't need to know where a doc lives — describe what you want to know.
- It's read-only. The gateway answers questions; it won't change code, infrastructure, or configuration.
What it can't help with
- Private application source code outside the curated set of privileged repositories.
- Internal-only or customer-specific systems.
- Live infrastructure state (it reads documentation, not your running clusters).