Release Notes#

Digital Design Studio integration, Windows MSIX preparation, and current release boundaries.

26 September 2026 · DDS and ALcad integration#

The product guides now describe one Digital Design Studio application. ALcad retains its name and dedicated CAD interface, with installation through the shared Downloads page and workflow guidance in the ALcad docs. Cloud provides the workspace menu for switching between DDS and ALcad screens. Desktop support follows the actual published release.

September 2026 Documentation Update#

Documentation 2026.09 uses Digital Design Studio as the integrated product name, with ISA inside its workspace. Download, verification, installation, first-launch, and account guidance now cover public downloads without website sign-in. Linux references cover approved DDS 1.0.30 and Ed25519-signed CLI 0.1.9. Windows 11 public signing remains pending.

Overview#

Digital Design Studio is the integrated application for RTL, ISA, Evolve and ALcad. ALcad remains a named CAD workspace with its own interface.

Digital Design Studio integration#

  • The RTL product is named Digital Design Studio.

  • ISA is available through Flow Navigator and the ISA function navigator in the left activity rail.

  • ISA functions open tabs named for the selected function.

  • Event Trace has one shared viewer under Analysis; ISA retains a shortcut.

  • The Explorer folder view shows the complete listing supplied by the project host, including supported files outside rtl/ and tb/.

  • Search in a focused side panel and automatic visibility of newly opened sidebar tabs belong to the unified workspace.

These are product and UI integration changes, not a claim that every old Linux installer contains the new UI. The exact package and host determine availability.

Windows release status#

Windows distribution belongs to the Digital Design Studio application, including ALcad. Public installer and Store availability are shown on the shared Downloads page; development builds are separate from published releases.

Offline licensing and rollback protection remain release requirements. Installation, launch, project read/write, update, removal, and required native capabilities must be verified before an artifact is called a product MSIX. Microsoft Store submission and publication are separate and are not yet claimed.

Earlier Linux releases#

Earlier signed Linux artifacts keep their original filenames, versions, and verification material. The separate ISA application is retired as a product entry; keep its original source and release evidence when migrating.

Do not infer a current release from an old version table, a GitHub tag, or a development build. The official catalog and artifact-specific release evidence determine what is publicly distributed.

Remaining availability boundaries#

MCP, Task Center, and native integration work is tracked with Digital Design Studio. An item on that roadmap is not a shipped feature. External toolchains, measured performance, and long-running remote operations have independent availability and licensing requirements.

ALcad modes and native project persistence do not imply complete CAD editing, manufacturing export, 3D, or SI/PI implementation. See ALcad.

Update safely#

Keep the previous verified artifact and a separate project backup until the new version opens and saves the project successfully. Never migrate credentials, device-trust files, or local licence state by copying them between machines.