Everything they find lands in the Inbox as an issue carrying the research behind it.
You don’t need to build a workflow to find knowledge gaps from chat history,
or to validate SQL and wiki links on a schedule. Those run for you. Reach for
a workflow only for a recurring job specific to
your organization that none of the agents covers.
Validation
Validation runs two passes on different cadences. Knowledge validation, weekly, checks the knowledge base against your live warehouse and reports:- SQL that fails or times out
- Tables and columns that no longer exist, or that exist but are undocumented
- Broken wiki links between documents
- Empty documents
Chat review
Chat review reads every conversation from the past day and files an issue for each gap in the knowledge base it exposed, ranked by how often the gap comes up. A term the agent had to guess at twice is a stronger signal than one it guessed at once. This is the agent that makes real usage drive documentation, rather than someone deciding up front what to write. It takes no settings beyond its schedule.Issue triage
Triage picks up each new issue, researches it, and ends it in one of four places: fixed, closed, snoozed until whatever it waits on changes, or moved to needs input with a specific question for a specific person. You can set:- Issues per run — the most issues one run researches. 50 by default.
- Additional fixes — kinds of change Delphina may make in your workspace without asking, on top of the standard set below.
What Delphina fixes without asking
Triage applies a deliberately narrow set of changes on its own — the kind where there is only one right answer:- Mechanical fixes: broken wiki links, typos in prose, outdated column lists, a table name that isn’t fully qualified.
- Reorganization: restructuring a document, or deduplicating a concept stated in several places by keeping one copy and linking to it.
- Filling gaps from the live schema: adding a table document the knowledge base is missing, or the columns a table document lacks, marking anything the evidence doesn’t establish as unknown.
- Removing a column the live schema no longer has, leaving a warning on each document that still uses it rather than editing the logic.
Questions to your team
When triage decides something needs a person, this agent asks them — in Slack, by mention, so the question reaches someone rather than sitting in a queue. It follows up on questions that go unanswered. Answers are recorded against the question on the issue, not lost in a thread, and an answer returns a needs-input issue to open. See Comments and questions. You can set questions per run — the most new questions one run asks, 3 by default, so a quiet week doesn’t turn into a flood. Who gets asked is set by Delphina, from what it can infer about who owns an area.Changing what they do
Schedules for chat review, issue triage, and questions are yours to set from the Context Factory page, along with the per-agent settings above. Everything else shown there — routing, re-check intervals, and any instructions specific to your organization — is set by Delphina; ask your contact to change one.Related
- Context Factory — the flywheel these agents turn
- Inbox — where their findings land
- Knowledge Base — browsing the knowledge base and its version history
- Maintenance — editing knowledge by hand