atom

atom is the init and service manager for Sinty OS.

The binary is sinit. Invoked as atomctl (a symlink to the same binary) it is the control CLI.

sinit boots a target from unit files, starts them in parallel by their dependencies, supervises services, handles socket activation, and answers status, log, start/stop and shutdown requests over atomctl. It reads .service, .target, .socket and .timer units and implements the common directives for ordering, restart, watchdogs and readiness.

Requirements

• Go 1.26 or newer
• Linux

Build

go build ./...
go test ./...

sinit is a single multicall binary; atomctl is a symlink to it:

go build -o sinit ./cmd/sinit
ln -s sinit atomctl

atom-probe

cmd/atom-probe is for development images only. It serves an authenticated shell over TLS and will not start unless a marker (/etc/atom/probe.enabled or /etc/atom/dev.enabled) and a token are present. Do not ship it in a production image.

Updates

atom does not manage OS updates. Boot confirmation, rollback and the update flow live in atomloops.

License

GPL-3.0-only. See LICENSE.

Use of Generative AI

Maintainers may use generative AI tools as assistants while working on atom. Non-trivial assisted commits disclose the tool, model, and scope of the work.

AI tools may assist with code comments, documentation, repetitive code, and issue triage. Maintainers make project decisions and review every assisted change before it is merged.

Use these trailers for non-trivial assisted commits:

Assisted-by: <tool>:<model-version>
AI-Scope: <what the tool generated and the prompt or a short prompt summary>

Single-line completions, renames, and formatting changes do not need trailers.

Coding agents must also follow AGENTS.md before changing files, creating commits, or opening pull requests.