ChaseOS Studio V1.1.0: inspect knowledge before it joins the graph

ChaseOS Studio V1.1.0 is now the public Windows release. This update is about making the path from captured evidence to durable knowledge visible before anything is filed.

The public release manifest, website download and installed build on the primary test system all resolve to the same V1.1.0 candidate. The installer was downloaded back from the public URL and matched against its published SHA-256, rather than treating a successful upload as proof by itself.

Existing V1.0.9 installations can now discover V1.1.0 through Studio’s update channel. A second computer is the next useful acceptance environment: it should receive the update prompt, install the signed package and then confirm its own installed version. That second-machine completion is a test to perform, not something this article assumes has already happened.

Intake now previews the graph change

The Intake flow can hand a proposed filing plan to the graph without silently adding it. The proposed node stays highlighted, existing connections remain visible, and the operator can zoom to the affected area or return to Intake.

This is the useful distinction: the graph preview is an inspection state. It is not permission to write the note.

Research Collections keeps evidence and destination together

Research Collections now puts the reason for the suggestion, resolved evidence, target path, proposed node, new links and rewrite count into one review surface. The example above proposes one collection node linked to 17 existing notes with zero rewrites.

The interface also states the scope of the destination and keeps Inspect in Graph, Queue for approval and Dismiss suggestion as separate decisions. That separation matters because previewing a useful structure should not automatically promote it into canonical knowledge.

Approvals exposes where a request came from

Approvals now groups requests by Studio and local work, agent runtimes and external connectors. The retained signed-build capture shows the truthful empty state: nothing was waiting at the moment of QA. Separate interaction evidence covers approve and decline journeys, but an empty packaged screenshot is not mislabelled as proof that a live request was executed.

What was actually verified

• The Windows installer is Authenticode-signed and timestamped.
• The public V1.1.0 installer is 531,616,112 bytes.
• Its public readback SHA-256 matches the published release hash.
• A V1.0.9 version check reports V1.1.0 as available.
• A V1.1.0 version check reports the installation as current.
• Signed packaged-app visual QA retained distinct Intake, Research Collections and Approvals captures against a real vault.

The remaining cross-device acceptance is deliberately separate: install the update on the second computer, reopen Studio, confirm V1.1.0 there and then test that machine’s own runtime and Cloud state. A website publication cannot prove those machine-local outcomes.

Download ChaseOS Studio V1.1.0 · Read the full public changelog