Build log
ChaseOS Studio V1.1.0: binding the interface, installer and update feed to one release
How V1.1.0 made knowledge intake inspectable and tied the public download, updater, installed app and visual evidence to the same signed Windows release.
Source: Public ChaseOS V1.1.0 changelog, signed release manifest and privacy-screened packaged visual evidence
- Signed build accepted
- Public release
- Build identity
20260826-230839-38ed0e4b
Technical bibliography record
The build, in five parts.
- 01 Built
- A signed V1.1.0 Windows release joining inspectable knowledge intake, graph budgets and hygiene, approval surfaces, runtime discovery and explicit Cloud routing boundaries.
- 02 Process
- The app, installer, update feed, public download, exact hashes and packaged visual evidence were bound to one release identity before publication.
- 03 Learned
- Deterministic routing tests prove the decision and request shape, not live provider capacity, rate-limit behavior or second-computer acceptance.
- 04 Skills
- Windows release engineeringknowledge-graph UXvisual QACloud routingtruthful proof states
- 05 Saved
- Signed manifest timestamps, immutable artifact identity, packaged screenshots, updater evidence and explicit unverified live-provider and second-device boundaries.
Visual QA and product evidence
See the milestone, not only the summary.
What changed#
V1.1.0 consolidates the recent Studio line around one operator workflow: evidence arrives through Intake or Research Collections, its destination and graph relationships are previewed, and no durable write occurs until approval. The release also makes graph budgets, canonical-node selection, in-place graph hygiene, runtime discovery and Cloud model modes visible rather than leaving them as hidden configuration.
The release identity problem#
A version label is not enough when the loading screen, installed executable, installer, website and update feed can drift independently. This release treats those surfaces as one contract: the public manifest names V1.1.0, the immutable installer matches its published size and SHA-256, and the retained packaged evidence comes from that accepted release lane.
Inspect before filing#
The Intake graph handoff highlights the proposed node and its planned links without silently creating it. Research Collections keeps source evidence, destination path, affected notes, collection map and approval actions in the same view. Closing the highlight returns the graph to normal inspection; approving is the separate action that permits the write.
Truthful graph scale#
The full-vault node and edge totals are different from the number of nodes drawn in the current view. Studio now reports those separately. A view budget ranks canonical roots, connected nodes and locally relevant project or runtime context before lower-signal isolated nodes, so reducing the budget is a deterministic prioritisation step rather than a hard-coded list for one user.
Cloud and runtime boundaries#
Auto, Fast, Balanced, Code and Deep are harness configuration choices, not decorative cards. Auto exposes its 120,000-token boundary and the DeepSeek overflow route for oversized context. Relocated WSL installations are discovered through a bounded scan and cached result. A live provider call and a second-computer upgrade remain separate acceptance states and are not inferred from the local package proof.
What the evidence proves#
The retained visuals prove the signed packaged surfaces for Research Collections, Intake-to-Graph inspection and the Approval Center's truthful empty state. The web release was also checked at desktop and 390-pixel mobile widths. These are interface and release-contract proofs; an empty approval capture is not presented as proof that an external connector generated a real pending approval.
Current release state#
V1.1.0 is the public Windows release. The installer is Certum-signed and timestamped, the public update feed points to the same immutable artifact, and an existing V1.0.9 installation can discover it. The primary test system is installed; the second physical computer remains the operator's next independent upgrade and Cloud-key acceptance environment.