Skip to content
refereekit

The session directory

A session is one folder that holds one paper and everything refereekit made from it. It sits inside your reviews folder’s work/, which keeps it out of any repository. You can open its files in a text editor. In the agents with hooks, the hook guard refuses the agent’s ordinary tools there. It is not a sandbox.

Layout

Section titled “Layout”
<session>/
  paper.pdf       the original submission, bound to the session
  doc.json        the text refereekit extracted from it
  binding.json    the fingerprints that bind the session to that PDF
  revisions/      revised PDFs, stored beside the original
  form.json       the venue's OpenReview review form
  state.json      the claim pool, your verdict and the venue
  questions.json  each question you asked, and how it stands
  answers.json    every answer, as the model gave it and as checked
  verdicts.json   every check of every answer's evidence
  questions.txt   your own questions for this paper, if you write any
  index.html      the questions and answers, as a page
  ours/           drafts written for you
    history/      earlier versions of each draft
  theirs/         documents others sent you
  evidence/       crops of an equation's place in the PDF, made in pi

A file appears only once a step has something to write in it. The tutorial’s session has no form.json or theirs/, because only an OpenReview fetch writes them.

Only checked evidence joins the claim pool in state.json. A quotation that passes joins with its words. A page pointer joins as a bare pointer. A quotation of fewer than four words joins as its page alone. A FAIL never joins. Every verdict, FAIL included, is kept in verdicts.json.

ours/ and theirs/

Section titled “ours/ and theirs/”

ours/ holds every draft written for you: the report, the editor letter, the OpenReview form and the analysis of the replies. refereekit records each draft as it writes it. So it knows when you have edited one, and asks before it replaces it. Every earlier version goes into ours/history/, and nothing there is ever overwritten.

An edited draft is only a changed file. It does not say you read it, agreed with it or approved it.

theirs/ holds what others sent you: a co-referee’s report, or the replies an OpenReview fetch brings. It is written once. A second file under a name already there is refused, never written over. A received file that could be replaced silently would look like one refereekit wrote.

The two are kept apart because a co-referee’s report is evidence, and your draft is not.

What deleting destroys

Section titled “What deleting destroys”

Ask the agent to delete a session when the review is over, and the venue’s terms allow it. Deleting removes the whole session folder:

  • the paper, its extracted text and every revision;
  • the claim pool, your questions, the answers and your verdict;
  • every draft, with its history;
  • everything others sent you.

Before it deletes, refereekit shows you how many of each it will remove. It deletes only on your yes, on your own screen. It cannot be undone.

Deleting never touches what lies outside the session. The PDF you started from stays where it was. So do your venue notes, your style guide and anything you copied out. A session from an older version may hold venue notes of its own. You then choose first whether to keep them in a notes file outside the session, or discard them.

See also

Section titled “See also”