Arcane OS Docs Development only

Reference

Arcane.requirements

Requirement inventory and authorized installation operations.

  • Reference

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

Syntax

Arcane.requirements

Member kind

Namespace

Description

Requirement inventory and authorized installation operations.

Overview

Arcane.requirements reads the installation requirement inventory and lets the Provisioner ensure selected requirements. Omitting the requirement-id array selects only requirements marked required; null and an empty array have the same default. The interruption option is exactly "deny" or "allow" and defaults to "deny".

Availability and security

Listing requires requirements.read. Ensuring requires provisioning.manage, the provisioner app type, privilege, and an exclusive mutation boundary. "allow" does not bypass native process-identity and port proof before an existing user process can be interrupted.

Example

const access = await globalThis.Arcane.capabilities.list();
const canListRequirements = access.methods.includes('requirements.list');

console.log('Requirement inventory admitted:', canListRequirements);

Members

  • Arcane.requirements.list() — Lists installation requirements.
  • Arcane.requirements.ensure() — Ensures the selected requirements are installed/configured. The guarded Provisioner-open Ollama reconciliation always uses deny; only the separately confirmed close-and-retry action uses allow, and the native handoff still re-proves exact process and port identity before any interruption.

Reference group

Namespace, constructor, and values

Repository and reviewed source access