Build with Nova
Rather not read it all? Ask Nova this. It walks you through each step and does the ones it can when you approve.
The build work of a platform team, asked in plain words and grounded in charts, docs and your own runbooks.
Who does what: Alice (platform engineer, org owner) builds with Nova and approves each change. Each skill and what it can do: Skills.
1. Find a chart and deploy it
The Helm skill finds public charts and shows their values and manifests; it changes nothing. To run the chart, Alice deploys it as an app with the Helm chart source, or asks Nova to, and the deploy waits for approval.
The chart and its retention values, read from the published chart.
2. Check a Terraform argument
The Terraform skill looks up provider docs, verified modules, versions and policies. It does not plan or apply; Alice runs Terraform as before.
The argument, from the provider's documentation.
3. Check a cloud fact
The AWS Knowledge skill searches AWS documentation and checks which services each region offers. It reads only public information.
Whether that instance type is offered there, from AWS's public data.
4. Open a pull request
With the GitHub skill, Nova works with your repositories and pull requests. Writing to a repository is a change, so it asks first under the default guardrails.
The change on an approval card first; nothing is written to the repository until someone approves.
5. Ask your runbooks
On the Enterprise plan, the Operational Memory skill reads your runbooks, docs and postmortems from a GitHub repository, and Nova cites them (Operational Memory).
An answer that cites the runbook it came from.