Task-based documentation

Choose the workflow before the command.

Arcane keeps app ownership, shared runtime work, and native toolchains separate. Pick the guide whose boundary matches what you are changing.

Developer paths

Each guide begins with its authority and ends with the exact artifact or evidence it creates.

First project

Use published arcane-os@0.5.18, scaffold one browser app, install it, and start the browser loop.

One request

Use new AI(), supply your runtime key, and display the complete response. Includes saved-preference migration.

On-device speech

Configure Kokoro, load and unmute, stream audio in exact order, and inspect the selected device.

Independent source

Own source, tests, adapters, licensing, and one deterministic release bundle in a separate repository.

Arcane checkout

Develop one built-in app or run one exact shared/Core test through the fixed Arcane provider.

Explicit toolchain

Pair one declared target with one compatible Arcane OS checkout and keep the selected artifact and its owning process explicit.

Boundary check

I need to…	Workspace	Guide	Result
Create my first app	New external repository	Quick start	Running browser app
Keep application source outside Arcane	External repository	External app	Selected app package or bundle
Change a built-in Arcane app	Arcane OS checkout	Integrated	One selected app check/package
Change shared runtime or Core	Arcane OS checkout	Integrated shared scope	One focused test or canonical check
Produce a native development artifact	App plus compatible Arcane checkout	Native builds	One selected target artifact

No implicit all-application loop.

No inferred format or architecture.

Every background operation surfaces its result.

Build only the selected application artifact.