Deployment recovery
The catalog is missing from this deployment.
The documentation catalog could not be loaded.
You can still open the reviewed source guides while the generated Pages artifact is repaired.
Arcane OS documentation
Understand the system, provision a first user, and build with the shared Arcane runtime. Start with a guided path or search the reviewed public documentation.
Search the public guide
Search titles, summaries, and tags locally. Your query stays in this browser.
Choose a path
Arcane documentation is organized by intent, so you can move from a first task to implementation detail without browsing the repository structure.
Published snapshot
Everything below is generated from the published documentation catalog; the app adds no display cap, while current shared catalog limits remain visible.
Public documentation
Search every published Arcane OS guide and reference locally.
Deployment recovery
The documentation catalog could not be loaded.
You can still open the reviewed source guides while the generated Pages artifact is repaired.
Published source without an app-owned display cap
Published entries are displayed as non-executable text without an app-owned display cap. Shared catalog behavior remains pending runtime materialization and reports current limits when present.
Deployment recovery
The reviewed source catalog could not be loaded.
Read the public repository-access notes while the generated Pages artifact is repaired.
Repository accessShared runtime, live
These specimens load the packaged files from `arcane/components`; they are not screenshots pretending to be controls.
Input + computation
Status overview
Long-running work
No app-owned content cap
Inert source text
Recorded states
Historical example captures complement the live specimens when a component needs native or provider context.
Checks run only on request
Run the focused Unit, Functional, Integration, and Regression checks against the deployed catalog, component lifecycle, project-path resolution, and configured AI behavior. These labels are app-local presentation views; they do not replace the formal Arcane OS test kinds in Testing Arcane OS. Every browser check executes once when you request it. No pasted code is evaluated.
The available checks are ready to run.
Optional and host-configured
Local catalog search is always available. AI activates only when a compatible Arcane host exposes a configured-provider profile and chat bridge.