Editorial policy

Sources before claims

Software identity, components, release channels, and license statements are based primarily on the Open-Shell repository, releases, wiki, and project-linked documentation. Microsoft documentation is used for Windows lifecycle and PowerShell verification guidance. A user report is evidence of a reported symptom, not proof that every user has the same problem.

Separate facts from suggested checks

Procedural guidance is written to be reversible and testable. A suggested baseline or troubleshooting sequence is not presented as a guaranteed fix. Each guide names a verification step and a limitation. No ratings, download totals, endorsements, or test certificates are copied from an unrelated publisher.

Updates and corrections

The displayed date is the date this website content was prepared or materially checked, not the software release date. A later program release requires a deliberate review of links, version-specific advice, and the download configuration. It must not silently turn a preview into the stable recommendation.

Corrections should identify the page, disputed statement, software version, Windows build when relevant, and a primary source or repeatable observation. The operator needs to publish a working editorial contact before claiming an active correction service.

AI assistance and review scope

AI-assisted drafting was used to assemble these guides. Source checks do not equal hands-on execution of Windows software. The testing methodology explains that distinction. No project maintainer is represented as the author or reviewer of this website.