Skip to content

The README says what phase 2 is now - #21

Merged
ddehilster merged 2 commits into
mainfrom
docs/the-readme-says-what-phase-2-is-now
Sep 17, 2026
Merged

ddehilster merged 2 commits into
mainfrom
docs/the-readme-says-what-phase-2-is-now

Conversation

@ddehilster

@ddehilster ddehilster commented Sep 17, 2026 •

Copy link
Copy Markdown
Member

Three stale spots, found by reading the README against what the app actually does:

Said Actually
phase 2 is "started — the editor, and running analyzers through a local run server" it is deployed at studio.visualtext.org/studio/ (401s for anyone not invited, so it is really there), opens analyzers from GitHub and commits them back as pull requests
the shared package is "the pass sequence and knowledge base" seven views — output files, parse trees, code, log and values too — and released for other pages to install
— the values a run found were not mentioned anywhere. It is the first thing the Output tab shows, and without it the quick start reads as though the studio only says what a run wrote, not what it found

The -DEV per-pass trees and rule matches went in with #20 and are already described.

Also in the package's own README: "NLP Studio uses it today, and the admin console's Browse and run is next" — which has shipped, from a release, so the line described a plan that had already happened. It now names the three rules that made one package worth having: no .kb files in the knowledge base, a switched-off pass keeping the number the engine gives it, and a -DEV run's per-pass trees and rule matches read the same way in both pages. No customer, repository or host is named — it still says "the admin console", as it did before.

🤖 Generated with Claude Code

ddehilster and others added 2 commits September 17, 2026 19:35
Three things had gone stale while the work moved:

  * phase 2 read "started -- the editor, and running analyzers through a local
    run server". It is deployed at studio.visualtext.org/studio/, opens
    analyzers from GitHub and commits them back as pull requests.
  * the shared package was described as "the pass sequence and knowledge base".
    It is seven views now -- output files, parse trees, code, log and values as
    well -- and it is released for other pages to install.
  * the values a run found, which is the first thing the Output tab shows, were
    not mentioned at all. A person reading the quick start would not know the
    studio answers "what did the analyzer find" and not only "what did it write".

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
"NLP Studio uses it today, and the admin console's Browse and run is next" --
which has shipped, from a release, so the sentence was describing a plan that
had already happened.

Named with it are the three rules that made one package worth having: the .kb
files nobody edits are never listed, a switched-off pass keeps the number the
engine gives it, and a -DEV run's per-pass trees and rule matches are read the
same way in both pages.

No customer, repository or host is named: the line says "the admin console", as
it did before.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@ddehilster
ddehilster merged commit 8debc1f into main Sep 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant