Knowledge for your app
For citizen developers
Greenlight keeps a small set of notes about each app. The notes are called Knowledge, and they’re how the agent remembers what your app is for, how it’s put together, and what it has learned along the way.
You and your agent both edit Knowledge. The agent reads it at the start of every session, so the second conversation about your app is smarter than the first.
What’s in app Knowledge
When the agent first registers your app, Greenlight seeds two Knowledge entries from the description you gave:
- Architecture — what the app does, what it’s built with, what data it touches.
- Runbook — the README the agent wrote, with the basics of how to operate the app.
Over time, both grow. The agent appends notes as it builds new features. You can edit either entry from the app’s detail page — fix a wrong assumption, add a detail the agent missed, or write down a gotcha you discovered.
What you might add
You don’t have to add anything. But a few things tend to help:
- What “done” looks like. “This app is for the finance team during their monthly close. It doesn’t need to be fast the rest of the month.”
- Decisions you’ve made. “We decided to do email notifications, not Slack. Slack is too noisy for this team.”
- Gotchas you’ve discovered. “If the Snowflake query takes more than 5 seconds, switch to the materialized view; the live data is fine being a few minutes stale.”
- People to ask. “The product manager for this is Priya. Anything about scope, ask her first.”
The agent reads everything you write here at the start of the next session. It’ll catch a lot of “wait, why is the agent suggesting that?” moments.
When the agent proposes a change
As the agent builds, it sometimes learns something it thinks is worth remembering. When that happens, it’ll propose a Knowledge change — a new note, or an edit to an existing one. The proposal shows up in the dashboard for you to accept, edit, or reject.
You don’t have to act on a proposal immediately. They stack up and you can review them on your schedule. The agent doesn’t write directly; it always proposes, and you decide.
Org Knowledge and integration Knowledge
There are two other kinds of Knowledge you’ll occasionally bump into:
- Org Knowledge — IT’s notes about how your organization works. Conventions, design system, security policies. You can read these but only IT edits them.
- Integration Knowledge — notes attached to a data source, like Snowflake. What warehouses your app can use, idiomatic queries, gotchas. IT seeds these; you and the agent can propose changes.
The agent reads all three kinds whenever it works on your app.