Arcane OS Docs Development only

Reference

Arcane.system

Bounded operating-system actions, metrics, health-independent ping, and failure policy.

  • Reference

This focused page is derived from the mechanically checked full member inventory.

Syntax

Arcane.system

Member kind

Namespace

Description

Bounded operating-system actions, metrics, health-independent ping, and failure policy.

Overview

Arcane.system groups bounded operating-system session lock, bridge ping, allowed metrics, and Settings-owned verification-failure policy. Ping proves only that the host admitted and answered one request; it is not a health, privilege, trust, or release-readiness result.

Availability and security

Ping is capability-free on Core and Android. Metrics require system.metrics.read; lock requires session.control and the Shell app type. Failure-policy reads and writes are Settings-only through preference capabilities, and writes are exclusive.

Example

const result = await globalThis.Arcane.system.ping();

console.log('Host answered:', result.ok);

Members

  • Arcane.system.lock() — Locks the operating-system session.
  • Arcane.system.ping() — Confirms only that the bound host bridge admitted and answered the request. It does not claim dependency readiness, system health, privilege, signer trust, or release-candidate status.
  • Arcane.system.metrics() — Gets allowed machine metrics.
  • Arcane.system.failurePolicy() — Gets the user-wide verification behavior. failFast defaults to false; application-owned repository readers may use it to choose validated-subset warnings or immediate rejection. Settings only.
  • Arcane.system.saveFailurePolicy() — Saves warn-first (false) or fail-fast (true) behavior. The preference does not expose quarantined documents or relax repository-write validation. Settings only.

Reference group

Namespace, constructor, and values

Repository and reviewed source access