Skip to main content

Feedback on an answer

Prism joins several incomplete sources — Agent Router usage, a mirror of your GitHub organisation, your Jira — and infers across them. That means the person best placed to notice that an answer is wrong is usually the person reading it, holding something Prism does not have.

So every answer carries a thumbs up and a thumbs down. Thumbs down opens a short box: what's wrong with this?

Nothing leaves your deployment. Reports are written to your own database and read on an admin page inside your own Prism. There is no outbound connection, no relay, and no Tetrate endpoint involved. If you want us to see a report, you export it and send it — deliberately, as a file, after you have read it.

What a reader does​

Under each answer, two buttons. Thumbs up is one click and done. Thumbs down records immediately — before anything is typed, so a reader who thinks better of explaining has still told you something — and opens a box for what they know that Prism does not.

The thumbs appear on every answer, including one that failed or was cut off part way. Those are the ones most worth reporting.

Attaching evidence​

A reader can attach up to three files, 5 MB each: screenshots (PNG, JPEG, WebP, GIF), PDFs, and plain text or CSV. That is the case this feature was really built for — a screenshot of a news story, or an extract from a system of record, showing something Prism does not know.

Prism decides what a file is from its contents, not from what the upload claims: a file whose name and contents disagree is refused with a sentence saying so, and SVG is refused outright because it can carry scripts. A refusal happens before anything is recorded, so the reader can fix the file and send the whole report again.

What is stored with it​

The reader is never asked to copy anything back. Each report carries, taken from Prism's own record of that turn:

  • the question that was asked, and the answer that was given;
  • the provenance record for that answer — which tools ran, against which sources, how fresh each was, what window the figures covered;
  • whether the reader's browser saw the answer cut off in delivery, which is a failure the server cannot see;
  • who filed it, and when.

A report about a turn Prism has no record of is still kept, and says so rather than showing you an empty answer.

Reading and forwarding reports​

Admin → Answer feedback, or /admin/feedback directly. It needs the super admin role — a report quotes a whole answer back, and answers in this product name people, their pull requests and what they cost.

The queue lists what readers filed, newest first, with what they wrote. Open one and you get the question, the answer rendered as the reader saw it, and the same provenance footer that was under it in the chat.

Three boxes on that page are editable: the reader's comment, the question, and the answer. What you download is what those boxes contain. The stored report is not changed, so removing a name or a figure prepares a copy to send without destroying the original. This is the intended order of work:

  1. read the report;
  2. remove anything that should not leave your organisation;
  3. download it — .md to read, .json to hand to an engineer;
  4. set its status to forwarded, and leave a note for whoever else is working the queue.

The internal note is never in either download. It is for you and your colleagues.

Export all downloads every report as stored — unredacted. It is there so you can inspect the whole set inside your network; it is not the file to forward without reading.

Housekeeping​

Reports live in the same database as everything else Prism stores, and nothing prunes them — see Limits. A report on its own is small, about five kilobytes. Attachments are the part with a size worth knowing: 5 MB each and at most three per report, so a heavily-illustrated report is 15 MB and a normal evaluation's worth of feedback is tens of megabytes. That is not a capacity concern on the default volume, but it is the one thing here a reader controls the size of.

There is no notification of any kind. Nothing emails anybody when a report arrives, because nothing in Prism reaches outside your network. The count on the admin page is how you find out, so it is worth a look during an evaluation.