The inspector

greenline inspect opens the workspace as one readable document in your browser, served by the CLI on your own machine. Nothing leaves the machine, and starting it adds nothing to the repository.

npx greenline inspect

It prints one line with the address, http://127.0.0.1:7433/ unless --port <n> says otherwise, and stays up until you stop it with ctrl-c. It refuses outside a Git repository, and in a repository without .greenline/manifest.json; run greenline init first.

What you can read#

Eight screens, on the keys 1 to 8.

  1. Overview: what is installed and on, what greenline wrote since your last review (the "worth a look" list, from the offers file), and doctor's checks.
  2. Resolver: type a path and read the eight ranks that apply to it, from your written rules down to background reading. A section you turned off shows as a gap on its rank.
  3. Reader: any installed file, whole, at a reading measure, with its claims in the margin and a gap where a section is turned off.
  4. Changes: every installed skill file that differs from its committed copy, as a whole-file diff.
  5. Provenance: every claim in scope, with its id, kind, source, the date it was verified, its pin, and its ruling.
  6. Clocks: the dated pins, armed or fired against today.
  7. House rulings: the stanza's dash lines, parsed and editable.
  8. Manifest: profile, stack, targets, skills on and off, sections off, the law list, and the review date.

? opens the shortcuts-and-words sheet, which defines every word the surface coins. p jumps to the resolver's path field, / focuses the filter in view, o takes the file in the reader to its sections in the manifest, d switches dark and light, and ⌘↵ (or ctrl-enter) saves.

What it writes#

Two things, both of which you could type yourself.

It never writes shipped prose. A shipped section is turned off in the manifest, or overruled by a House ruling; the text greenline installs stays what the corpus says.

When it refuses#