Overview
Repository and download access
What the public documentation includes, why the repository and builds remain private, and how authorized contributors should obtain and verify a checkout.
The Arcane OS documentation site is public. The source repository and native development artifacts are currently private.
What public access includes
The site publishes a reviewed positive inventory of documentation, selected shared-runtime source files, examples, and controlled images. It does not expose the repository tree, untracked files, private issue material, credentials, generated machine bundles, or development work that has not been selected for publication.
Public documentation therefore does not imply public source or download access.
If you do not have repository access
- Use the public documentation and its local search.
- Do not rely on unofficial mirrors, archives, installers, certificates, or binaries.
- There is no public Arcane OS installer, release channel, or supported download at this time.
- A link or command that names a repository path may describe authorized contributor work without making that path public.
The public site does not currently provide an access-request workflow. Obtain access through the project owner or organization channel already known to you; do not send credentials or protected information with an access request.
If you are an authorized contributor
Use the Git identity to which access was granted. The supported checkout is:
git clone git@github.com:TheWizardNexus/ARCANE-OS.git
cd ARCANE-OS
If cloning reports “repository not found” or permission denied, verify your granted GitHub account and SSH identity. Do not work around an access failure with a copied archive or another contributor's credentials.
Continue with Developer setup. Git LFS is required for the shared speech runtime and model assets used by native development paths.
Private developer material
Some engineering procedures refer to repository-only manifests, tools, validation records, machine-bundle notes, or design files. Public readers should use the nearest published guide instead. Authorized contributors can find the named material in their checkout and must follow the repository instructions that apply there.
Reporting a broken public link
Record:
- the complete public page address;
- the visible link text;
- the address the link attempted to open;
- whether the result was missing, private, or unsupported;
- the browser-visible error, without credentials or private page contents.
A public guide should either route to another published page, clearly label an external destination, or explain that the material is private. It should not silently send a public reader to an inaccessible repository page.