peritia-backend

Rust engines for PeritiaOS — the systems side that makes packages, declarative config, and shared types work.

Build the brains first. The installable image is the shipping box; this repo is what goes inside it.

Project context

PeritiaOS is developer-first Linux: less setup friction, build-friendly storage, rootless containers, .peritia.yaml environments, and observability aimed at people who ship software. Public status and milestones live on the site repo while the OS is under a ~6-month build.

This repository owns the backend / engine track (slow path, milestone-gated).

Related repos

Repo	Role
Peritia	Public site, docs, updates feed, MILESTONES.md
peritia-backend (this repo)	Package manager, declarative engine, shared libs
peritia-frontend	Wizard TUI, observability TUI, CLIs

Solo checklist: SOLO-CHECKLIST.md
Board: PeritiaOS Solo Board

Stack

• Rust workspace
• Declarative surface: YAML (.peritia.yaml)
• Host-first testing — cargo test / fixture rootfs; flash images only for milestone smoke

Crates

Crate	Role
peritia-core	Shared types, errors, paths
peritia-pkg	Package manager + SAT/SemVer (M1+)
peritia-declare	Declarative engine for .peritia.yaml

Develop

cargo test
cargo build --workspace

No OS flash required for day-to-day engine work. See the site’s scripts/os/smoke-m1.sh when an image artifact exists.

Build order (short)

1. peritia-core types + tests
2. Image/layout ADR (paper) + fixture path
3. peritia-pkg one real install into a fixture
4. peritia-declare minimal YAML parse
5. Then wire frontend CLIs / later milestones

Status

Scaffold + M1 foundation in progress. Source is private; visitor-facing updates post on the public site feed.

License

AGPL-3.0-only — see LICENSE.