From 2ecc0e91a4b6744d30252945fb36cf611f2ce42b Mon Sep 17 00:00:00 2001 From: techman Date: Wed, 16 Sep 2026 23:30:39 -0700 Subject: [PATCH] Correct the instrument-simulation non-goal in README Scope MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit v0.2.0 shipped `lablink-sim`, a simulated bench documented in the README quickstart, which made the "No instrument simulation" non-goal false a few hundred lines below the feature contradicting it. State the distinction that is actually true: LabLink does not simulate your instrument and no driver carries a simulation code path; `lablink-sim` is a separate optional bench the real drivers reach over real protocols. The other non-goals still hold as written — there is no hosted endpoint, no GUI, no Dockerfile, and no driver parses protocol syntax — so they are left untouched. Co-Authored-By: Claude Opus 5 --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 59e3dd9..ee3bf3d 100644 --- a/README.md +++ b/README.md @@ -372,8 +372,9 @@ one `serial` driver. - **No server component.** LabLink runs on your local machine. There is no cloud deployment or hosted endpoint. -- **No instrument simulation.** Tests mock the driver libraries; real use needs - real hardware. +- **No simulation of your instrument.** No driver has a simulation code path; + `lablink-sim` is a separate optional bench that the real drivers connect to + over real protocols, to evaluate LabLink without hardware. - **No GUI.** The CLI is the only interface beyond MCP. - **Not a protocol library.** LabLink sends commands and returns responses; it does not parse or interpret SCPI or any other protocol syntax. That knowledge