The front page barely mentioned the AI assistant bridge - #174
Conversation
The AI assistant bridge is one of the things nothing else in this field does, and the README sold it as half a sentence inside the Virtual DSP bullet — written before typed operations, the engines, the junction tune and the probes existed, so it undersold what shipped as well as burying it. It gets a bullet of its own in "Why Resonalyze?", the Highlights clause now says what the bridge actually does, the assistant's guide and the protocol are linked from Documentation instead of from nowhere, and the FAQ answers the question anyone reading "AI" will ask first: no account, no key, no network request, nothing applied without a tick — and what the package does and does not carry, word for word as PROTOCOL states it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The bridge was correct in three places a reader reaches on the way down. It now leads: the one-paragraph description under the title names it, the intro says what it does before the development notice, "Why Resonalyze?" carries it second rather than last, and it has its own Highlights bullet instead of a tail on Virtual DSP's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 42c68e956b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| And it can hand that whole diagnosis to a **chat assistant**. Copy the system to | ||
| the clipboard, paste it into whichever assistant you already use, and its reply | ||
| comes back as typed operations you tick one at a time — or as a **probe**, which |
There was a problem hiding this comment.
For a valid proposal, admissible operations already start checked, as pinned by AgentProposalDialogTests.Rows_StartTickedWhereApplicable_AndRejectedRowsCannotBeTicked; clicking Apply selected can therefore apply every valid row without the user ticking any box. Describing this as operations the user must “tick one at a time,” and repeating that the tune remains untouched “until you tick a box,” incorrectly presents an opt-in review when the actual workflow is opt-out. Please say that operations are preselected for review and can be unticked before applying.
AGENTS.md reference: AGENTS.md:L155-L160
Useful? React with 👍 / 👎.
Four figures show what the program does and none of them showed the feature the page now leads with. This one is a real reply — the owner's own, twelve crossover candidates on each side of a C-D junction plus every channel's excess group delay — reviewed against his v6 session. It is taken by the screenshots tool rather than by hand, so it cannot go stale silently: a new scene presses Copy for AI (which is what mints the package id), rewrites that id into ai-proposal.json beside the tool, and captures the review. A reply carrying any other id draws the amber warning about a package the session cannot vouch for, and a session without a C-D junction draws refused rows — the scene stops with the reason in both cases instead of committing a figure of the program arguing with itself. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…ticked Admissible rows arrive ticked — REFERENCE says so, a test pins it, and the new figure shows it — so "typed operations you tick one at a time" and "the tune stays yours until you tick a box" described an opt-in review the program does not have, in five places, one of them directly above a picture contradicting it. The review is opt-out and its guarantee is Apply, not the tick: rows are judged against the values the channels hold now, any of them can be unticked, and nothing is written until Apply is pressed. Said that way in all five, and in the manual's "applies only what you tick" beside them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 participant
The bridge was one subordinate clause inside the Virtual DSP bullet, written
before typed operations, the engines, the junction tune and probes existed — so
it both buried the feature and described an older version of it.
Where it says so now
analysis it already listed.
as typed operations you tick one at a time, or a probe that measures what a
change would do and changes nothing; no account, no key, no network request.
it is the item nothing else in this field has.
current values, engine requests instead of invented numbers, probes that
measure a variant without touching the tune.
docs/agent/AGENT_GUIDE.mdanddocs/agent/PROTOCOL.md, which were linked from nowhere.goes, what the package carries and what it never carries — word for word as
PROTOCOL §3 states it.
Documentation only; no code touched.
Not done
There is no screenshot of the review dialog or a probe result in
assets/images/, so the Showcase still shows none. That is the strongestremaining way to sell this, and it needs the app driven over a real session —
say the word and I will capture one.
🤖 Generated with Claude Code