Arcane OS Docs Development only

Reviewed public documentation

Find the right Arcane OS page

Start with a section, then move through focused pages with clear previous and next steps.

5 pages

Overview

Learn what Arcane OS is, how its pieces fit together, and what the project currently supports.

Overview

What is Arcane OS?

A plain-language introduction to Arcane OS, its intent-and-capability model, current implementation, and development-only boundary.

Overview

Capabilities and current status

What exists across the public site, shared runtime, Microsoft NT, Linux, Android, application catalog, and AI boundaries—and what remains incomplete.

Overview

Device and model support

The exact managed model matrix, machine-wide and per-user boundaries, and the COTS validation ladder from Android phones through laptops, desktops, workstations, and servers.

Overview

Arcane applications

A human-readable tour of the 22 applications in the current development catalog plus the Shell and Provisioner system surfaces.

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.

5 pages

Get started

Choose a platform or role and follow a complete, verifiable first journey.

Get started

How to try Arcane OS

Choose a public-site, browser-runtime, Microsoft NT, Linux, or WSLg development path without mistaking a development artifact for a release.

Get started

Provision an Arcane OS user

Choose the Microsoft NT or experimental unsigned-local Linux walkthrough for staging, activating, signing in, and recovering an Arcane user.

Get started

Provision your first Arcane OS user on Linux

Build and verify the unsigned-local release, use an already-root Provisioner to stage and activate a standard Linux account, then complete native or WSLg sign-in.

Get started

Install and run Arcane OS on Linux or WSL

Prepare Ubuntu, build and verify the unsigned-local release, install it through an authorized root Provisioner, launch the native Shell, and recover WSLg rendering.

6 pages

Developers

Set up a checkout, build applications, package them correctly, and debug from evidence.

Build

Developer setup

Prepare a Microsoft NT or Linux development checkout, run the fast gate, package selected demos, and open native developer hosts.

Build

Application-building SOP

Required shared-core boundary, theme order, contracts, examples, tests, and capability declarations.

Build

Build your first Arcane application

A practical browser-context application path covering capability decisions, shared-core reuse, Arcane theming, package inventory, and development checks.

Build

Application packaging

Positive app inventories, shared payloads, adapters, deterministic output, and verification.

Build

Code style

Arcane JavaScript, HTML, CSS, naming, and automated style contracts.

Build

Debugging SOP

Evidence-led reproduction, isolation, manual verification, code repair, rebuild, and clean-state retest.

10 pages

Reference

Look up commands, APIs, readiness contracts, and local artificial-intelligence integration details.

Reference

Arcane native API

Application-facing bridge methods, parameters, returns, and capability boundaries.

Reference

Arcane events

Renderer-visible Arcane event names, delivery semantics, host availability, triggers, and payload contracts.

Reference

Arcane shared entities

Complete export inventory for Arcane shared entity records, validators, serializers, and constants.

Reference

Arcane AI data contracts

Typed AI request fields, result entities, limits, defaults, exactness rules, and provider boundaries.

Reference

Readiness contract

Load-order-safe event and persistent-state patterns for modules and imported components.

Reference

Questionnaire module

Reusable in-memory policy for deciding when an unshown questionnaire prompt is due.

Reference

Troubleshooting

Symptom-led recovery for the public site, private checkout, dependencies, Microsoft NT, Linux, WSLg, AI availability, and application development.

Reference

Arcane OS glossary

Plain-language definitions for Arcane applications, Core, Shell, Provisioner, capabilities, lifecycle labels, hosts, policy, and platform boundaries.

AI

Arcane Ollama models

Local model variants, service behavior, selection, and configuration contracts.

7 pages

Project status

Understand the development lifecycle, assurance boundaries, security posture, and accessibility expectations.

Assurance

Development lifecycle

Current development-only mode, fast checks, internal-demo boundary, safety invariants, and future promotion plan.

Assurance

Licensing Arcane OS

AGPL-3.0-only source terms, separately licensed component boundaries, and the commercial-licensing contact path.

Assurance

Testing Arcane OS

How static checks, unit, functional, controller UI, portable-system, smoke, native-platform, coverage, and acceptance evidence fit together.

Assurance

Accessibility verification

Complete-journey accessibility process for keyboard, assistive technology, themes, scaling, errors, and recovery.

Assurance

Security and privacy review

Warn-first verification behavior, independent trust anchors, trust-boundary review, abuse cases, evidence, and residual-risk disposition.

Assurance

Arcane OS security model

Public security guarantees, limitations, warn-first verification, residual risk, and why same-authority hashes are consistency evidence rather than authentication.

Assurance

Build and release SOP

Reproducible dependencies, byte preservation, signing separation, and clean-state platform gates.