Defined in the meeting,in the glossary by lunch
Every project grows a private language: settlement windows, soft holds, “active” users who are three different things in three different tickets. Khint turns the moment a term finally gets pinned down into a glossary entry: shape the definition with a saved AI action, then append it to your Confluence glossary page without leaving the notes it was born in.
One concept, three names,
five conflicting tickets
Undefined terms are the quietest source of rework a BA deals with. The workshop agrees on what a “chargeback” covers, nobody writes it down, and a month later two tickets, a spec, and a support macro each mean something slightly different by it. New joiners learn the language by guessing. The glossary page exists, but updating it means leaving what you were doing, so it froze last quarter. Khint closes the gap between where terms get defined (calls, threads, workshops) and where they should live (one Confluence page): Agents shape the raw sentences into a proper entry, Memorykeeps the project's context riding along, and the Atlassian integration appends the entry to the glossary without you switching windows.
A glossary that keeps up, step by step
A discovery week full of new words, one current Confluence page at the end of it.
Connect Atlassian once
On the MCP page, flip on the Atlassian card and enter your email, an API token, and your Confluence domain. The credentials stay on your machine. In the card's palette-rows list, Append to page is on out of the box and Comment on page is one switch away, so the palette is ready to write to your wiki.
Open a session for the language work
Start a Memory session named for the project: “Payments discovery: language”. Every Confluence pull and append is logged into it, and Khint keeps a compact running summary that rides along on your AI Actions, so the sixth definition of the week is written knowing the five before it. How Memory works →
Catch the definition where it lands
Mid-workshop, someone finally pins it down: “a settlement window is the gap between authorization and the funds landing, ours is T+2”. Select those sentences right there, hit Cmd+Shift+K, and run a saved Action like “Glossary entry” that returns a clean definition: the term, what it means in plain language, what it is often confused with. No prompt yet? Type a one-line description in the Action editor and press Generate.
Append it to the glossary page
Pick Append to pageunder Confluence. Khint asks which space and which page (your last-used space floats to the top, and you can always paste the page's link instead), and it asks before any AI runs, so backing out costs nothing. The entry lands at the end of the glossary page; the rest of the page, macros and tables included, is never touched, and a concurrent edit by a teammate makes the write fail cleanly instead of being overwritten.
Chain it, and pull the glossary back into your tickets
In the Workflow editor, add your “Glossary entry” Action and an Append to Confluence page integration step pinned to the glossary, so raw sentences → formatted entry → filed is one keystroke. Before refinement, run Pull page to bring the glossary into your session: the actions that draft your tickets now use the agreed words. How that improves ticket quality →
From a rambling explanation to an entry the team can cite
The shape of the entry is yours to set. This is one example of what a “Glossary entry” Action might return.
The fields are just an example: the judgment lives in the prompt you save. A domain that needs a “not the same as” line for every term, a regulated team that records who agreed, and a team that tags each term with the flows it appears in each get their own template, and Improve tightens the prompt in place as the glossary matures. Because the entry is appended as normal page content, the glossary stays a normal Confluence page: link terms from specs, anchor them from tickets, comment on entries like anything else in your wiki.
Why not just edit the Confluence page directly?
You can, and that is the glossary that froze last quarter. Terms do not get defined inside Confluence; they get defined in the middle of something else, and the switch (find the page, open the editor, match the house format, save without stepping on someone's draft) is exactly the friction that kills the habit. Khint keeps you where the term surfaced: the shaping is a saved Action, the filing is an append from the same palette, and when you would rather propose than write, Comment on pageposts a suggestion at the foot of the page for the glossary's owner instead. It also composes with the rest of your week: the same session feeds requirements elicitation during discovery, and meeting write-ups get their own pages in meeting notes to a Confluence page.
Common questions
How does the Confluence connection work?
Connect once from the MCP page (Khint's integrations hub) by flipping on the Atlassian card and entering your email, an API token, and your Confluence cloud domain. The credentials are stored on your machine, not on Khint's servers. The palette then gains Confluence rows: Pull page, Create page, Comment on page, and Append to page, each switchable per row from the card, so the palette only shows the moves you actually use.
What happens if a teammate edits the glossary at the same moment?
Nothing gets overwritten. Append to page uses Confluence's page version as a lock: Khint reads the page, adds your entry at the end, and writes it back at the next version number. If someone else saved an edit in between, Khint's write fails with a clear message instead of silently replacing their change. You rerun the append; the teammate's edit survives either way.
Will AI rewrite or reformat the rest of my page?
No, and that is deliberate. Khint never sends your existing page content through a model and never reformats it: the current body is carried over exactly as it is, macros, tables and layouts included, and only your new entry is added at the end. If Khint cannot read the page's current version or title, it refuses to write rather than guessing, because a wrong guess could damage a shared page.
When should I use Comment on page instead of Append?
Use Append when you maintain the glossary and the entry should land in the page body. Use Comment on page when someone else owns it and you would rather propose than write: it posts a comment at the foot of the page for the owner to fold in. A comment is a pure addition, so it can never alter or corrupt the page body. Both rows pick the target the same way: choose the space, then the page, or paste the page's link directly.
Give every term one agreed meaning
Free with 10 AI actions and 5 captures per day. No credit card. The next term gets its definition before the workshop ends.