Arcology Lazarus OS

Not Arcology OS

Arcology Lazarus OS is the dedicated Linux appliance shipped with Lazarus. It is based on Alpine Linux and OpenRC. It is not Arcology OS, which is the separately developed operating-system component of The Arcology.

The appliance exists so recovery policy can begin at boot. It launches directly into Lazarus, avoids a general desktop environment, disables ordinary automount behavior, starts the privileged service independently, and keeps the graphical session unprivileged.

Runtime shape

OpenRC starts lazarus-service with raw-device authority
An Xorg kiosk session starts the unprivileged Lazarus GUI
The GUI reaches the service through a local Unix-domain socket
Image storage mounts before the operator workflow starts
udev and bench profiles enforce physical port roles
No browser, desktop panel, ordinary terminal, or desktop automount participates in the appliance path

Installed and live forms

The installed appliance uses a UEFI system partition, an operating-system root, and persistent Lazarus state. The live USB boots its operating environment to RAM while preserving appliance profile, network settings, credentials, and activity on a dedicated LAZARUS_STATE partition.

Customer images remain separate on administrator-selected local or network storage. The live environment can therefore move between benches without mixing appliance state with recovery evidence.

Boot readiness as readable policy

ArcoBASIC summarizes whether the appliance is ready for a recovery job. OpenRC and device permissions supply state; the language turns that state into one clear operator decision.

ArcoBASICArcoBASIC communication example: appliance readiness gate

' Report whether the recovery bench is ready for customer media.
FUNCTION BenchReadiness(state)
    IF state.ServiceRunning == FALSE THEN RETURN "WAITING FOR SERVICE"
    IF state.ProfileLoaded == FALSE THEN RETURN "BENCH PROFILE REQUIRED"
    IF state.StorageMounted == FALSE THEN RETURN "IMAGE STORAGE UNAVAILABLE"
    IF state.StorageWritable == FALSE THEN RETURN "IMAGE STORAGE READ-ONLY"
    IF state.SourcePolicyActive == FALSE THEN RETURN "SOURCE PROTECTION INACTIVE"
    RETURN "BENCH READY"
END FUNCTION

state = {
    "ServiceRunning": TRUE,
    "ProfileLoaded": TRUE,
    "StorageMounted": TRUE,
    "StorageWritable": TRUE,
    "SourcePolicyActive": TRUE
}

PRINT BenchReadiness(state)

Current appliance work

The repository contains package definitions, OpenRC services, udev rules, kiosk configuration, root filesystem staging, live-image construction, installation tooling, persistent state support, and QEMU validation profiles.

Physical acceptance remains essential. USB bridge behavior, BitLocker cases, damaged NTFS, large images, removable export media, disconnect handling, and varied bench hardware must be proven on real devices before the appliance can claim production readiness.

Pushing policy down to where it cannot be skipped

Alpine Linux, OpenRC, and a kiosk Xorg session are specific to shipping a recovery appliance. Deciding to enforce workflow policy at the operating-system layer, so correct behavior happens automatically at boot instead of depending on an operator following instructions, is the part that generalizes.

The same move underlies infrastructure as code that makes the correct server configuration the only one that gets provisioned, container images shipped with no shell to accidentally use, and health-check endpoints that collapse a dozen internal signals into one boolean a load balancer can act on. Policy enforced by the platform survives forgetfulness in a way that policy enforced by a manual or a good intention never does.

Make the safe configuration the only configuration that is reachable. Ordinary automount is disabled and no general desktop, browser, or terminal exists on the appliance path, so the operator cannot accidentally wander into an unsafe state because that state was never built.
Start privileged and unprivileged components as genuinely separate processes, not just separate code paths. OpenRC starts lazarus-service with raw-device authority independently of the unprivileged GUI session, so the isolation is real at the process level, not just conventionally observed.
Turn scattered runtime facts into one plain decision. BenchReadiness folds service state, profile state, storage state, and source-policy state into a single answer such as BENCH READY or IMAGE STORAGE READ-ONLY, instead of leaving the operator to interpret five separate signals.
Keep the state of the platform separate from the evidence it is supposed to protect. Live-boot appliance state lives on a dedicated LAZARUS_STATE partition, deliberately apart from customer images on administrator-selected storage, so the tool and the evidence can never get tangled together.

LEARNING LAYER

Key terms, in plain language

You do not need a systems background to follow the work. These are the specialized terms used on this page.

OpenRC: A service and startup manager used by Alpine Linux. Lazarus OS uses it to start the privileged service and kiosk session in a controlled order.
Kiosk session: A restricted graphical session that launches one purpose-built interface instead of a general desktop environment.
IPCInter-process communication: A controlled way for separate programs to exchange requests, responses, and events. Lazarus uses it to keep the interface separate from raw-device authority.
Bench policy: Rules assigning physical recovery-bench ports and devices to roles such as source-only, destination-only, image storage, or ignored.