Skip to main content
The Inbox is the work queue for your Context Factory. Every finding the knowledge flywheel produces lands here as an issue — a knowledge gap a real conversation exposed, a document that no longer matches the warehouse, an evaluation that started failing. Each issue arrives with the research behind it, so you are reading a conclusion rather than a raw failure. Most issues are filed by the flywheel agents, and many are Fixed or Dismissed by them too. What reaches your team is the remainder: the questions only a person can settle.

What an issue holds

Statuses

  • Open — live and actionable.
  • Needs input — research found something only a person can settle, and the issue records who should answer and what they need to settle. An answer to one of its questions returns it to Open.
  • Snoozed — still open, but out of the actionable view until the snooze lapses (1 to 30 days). Use it when an issue is waiting on something external.
  • Fixed — the underlying problem was addressed. You can say what was done.
  • Dismissed — set aside without a fix. You pick Won’t address, Not an issue, Duplicate, or Other. For the first three, that choice is itself the reason, and you can add a note. For Other, you write the reason.
A written reason is optional: check Submit without a reason to skip it. Everyone following the issue is told the outcome, along with the reason or that there was none. Fixed and Dismissed issues can be re-opened.

Working through the queue

The Inbox lists the issues for your workspace; My issues narrows it to the ones assigned to you. Which issues you see depends on your role (see Who can do what). Sort and filter by status, priority, assignee, or tags, and open any row for the full issue with its research and discussion. From an issue you can:
  • Start an investigation — open a chat against the issue. Delphina has the issue and its references in context, and the chat stays attached to the issue.
  • Fix the documentation yourself — use /knowledge to edit the affected documents, then mark the issue Fixed.
  • Bring in a colleague — mention them in a comment. When an issue needs a decision, the Questions to your team agent asks the right person for you. See Comments and questions.
  • Escalate to Delphina Support — hand the issue to Delphina rather than a teammate. Escalated issues are labelled as such, and you can de-escalate them again.
Bulk actions let you set status, priority, or assignment across a selection at once, which is the fastest way to clear a backlog of duplicates after a large validation run.

Comments and questions

Commenting and asking are deliberately different things. A comment is discussion. Anyone in the workspace can post one, mention colleagues, and edit or delete their own. A question is a request for a decision — an ambiguous term, a choice between two definitions, which of several directions to take. Questions are asked by the Questions to your team agent, not from the web app. It mentions the people who can settle the question in Slack, along with everyone following the issue, and follows up when a question goes unanswered. Answer in Slack or on the issue. Either way, the answer is recorded against the question on the issue rather than lost in a thread, and an answer to a question on a Needs-input issue returns it to Open.

Who can do what

Comments and answers are open to everyone on purpose: the person who knows what amt means often isn’t the person who maintains the knowledge base.