Recovery / Preserve the work first
Update, rollback and recovery
Recover the application installation separately from source changes or an AI candidate. Keep the previous runtime, project files and evidence until the replacement has been checked.
Before replacing an installation
- Record the current application version, platform and artifact identity.
- Save work and preserve project source, Git history, local project state and verification evidence. A Git commit alone may not contain untracked files or external artifacts.
- Keep project folders outside the application directory. Do not delete settings or project state as a first troubleshooting step.
- Read the replacement release notes. Download and verify its exact checksum and signature.
- Close SiliconForge and any application-managed activity before replacing files.
Release history → · Artifact verification →
Application update or rollback
Linux
Extract the verified archive into a new user-owned directory. Keep the runtime together; do not extract over the running or previous installation. Launch its AppRun, open a representative project and run a known small check before changing desktop shortcuts or removing the old directory.
Windows
Verify the installer's Authenticode signature and checksum, close the application and use the supported installer path. Preserve project and evidence directories. Test startup and a representative workflow before treating the update as successful.
Use only an authorized rollback target.
Do not install an arbitrary older build from Git history or an internal cache. The current signed channel must explicitly name the rollback target. Version 0.1.0 is the initial public version; this page does not authorize an older production installer.
If a replacement cannot read a project or its evidence, preserve both copies and record the error. Do not assume downgrading is compatible with data written by a newer application.
- Identify whether the problem is in the working tree, a staged/committed revision, an unapplied AI candidate or an already-applied proposal.
- Inspect the exact baseline and current project state in Changes. Preserve newer or unrelated work before taking any reversal action.
- For a proposal, use the documented local recovery/rollback action and inspect its hash-bound snapshot and applicability. Do not mistake an imported design comparison for an applicable proposal.
- If source has changed since approval or apply, resolve the stale state rather than forcing the old snapshot over newer edits.
- After recovery, inspect the resulting files and rerun the checks relevant to the reverted behavior.
An installation rollback does not automatically revert project source. Rejecting an unapplied candidate does not mean reverting a Git commit. See version control and review for these separate states.
Uninstall SiliconForge
Close the application and preserve project/evidence data first. On Windows, use the operating system's installed-apps uninstall route. For an extracted Linux installation, remove only the identified application directory and its associated desktop registration after confirming neither contains project files you need.
Do not delete broad cache/configuration directories blindly, and do not remove shared external engineering tools merely because you are removing SiliconForge. Uninstalling an application is not a billing cancellation.
Subscription cancellation policy → · Detailed recovery and diagnostics →
Record the failed step, application version, platform, relevant tool version and exact error. Include a non-secret receipt identifier for billing. Never send provider keys, activation claims, card details or unapproved private RTL.
Contact support →