Docs
kelve.aiGitHub

Read plainly

Plainly is how kelve reads anything: a code file, a text file, a folder, a change. Each reads in one shape, in plain words, with every part linked to the ideas it rests on and the source a click away.

One shape

A page says, in this order, and leaves out what has nothing to say:

  1. What it is: what the whole is for, in a sentence. Under it, for a file, what uses it.
  2. In this change: its kind, and what it did before and does now.
  3. How it works: its parts, in the order things happen. For text, What it says: its sections.
  4. Also here: what it brings in or what most parts use, in one line.
  5. What else: what a folder keeps true, or what a change touches.

A part

Each part has a goal of two to six words, and a sentence or two on what it does and what for. The ideas it rests on are woven into the sentence, each with its square. Click a square to read its entry.

Show the code opens the lines the part explains, with a few lines either side, and what changed. A text file’s part has Show the text instead. Once shown, the lines carry their ideas and the notes on them. Each idea is named under the lines it’s on. Select lines there to leave a note, as in the file.

What changed

In a change, every part of a file is shown, so the change reads in the context of the whole. Its marks:

MarkWhat it means
NewEvery line of it was added
ChangedSome of it was added or taken out. It says what it did Before
MovedIt’s the same, somewhere else
Taken outIt’s gone, and the page says what it did
As beforeThe change didn’t touch it

kelve works out the marks from the change itself, not from what your agent says.

A folder, and a change

  • A folder’s page gives the steps one thing takes through its parts, each by the part that does it. Where nothing goes through it in order, it gives its parts by what each does. Seven at most, each with Open it. Then What it keeps true, each with the part that keeps it.
  • A change’s page gives what it changes and why, what your agent said, and where it fits. Then How it works now: its parts by purpose, not by file, each with the files it’s in. Then What else it touches, and its files in the order to read them.

A change’s page also says how many of its ideas the shared graph already had, and which lessons your agent was given and learned. Files that tools made, such as screenshots and lockfiles, are counted in one line and not read.

A page written again because what it’s written from changed says Being brought up to date until it’s done.

Plainly or as code

A file opens Plainly. As code, on the file’s name line, shows the code. A change’s file shows what changed, with the lines as before folded away. Anything else shows whole. A text file as code reads as text. The switch is for that visit. To open some files as code every time, say so in what kelve marks.

Checked before you see it

Your agent writes each page to the same rules. kelve checks each page before it shows it:

  • Every line is in exactly one part.
  • Each part’s words are within their limits.
  • Every name in code is on that part’s lines.

kelve sets right what it can. A page that fails goes back to your agent to fix, once.

While it’s written

A page not written yet shows the code or text meanwhile. One line above it says where the page is on your agent’s list. It says “Next for Claude Code”, or how many files your agent reads before this one. Do next moves it up.

When nothing’s taking your agent’s list, the line says “Waiting for you to ask Claude Code”, with Copy what to say. Copy what to say copies the words to paste to your agent. They name what this tab has open by its number, such as “Do what’s waiting for you in kelve for “Calls to the bank that are safe to retry” (number 12).”