Categories: Feature

Each read surface answers a different question. Command Question Writes? status What state is the Repository in? no check Does the selected Repository satisfy the complete delivery contract? no changes What physical files differ between Built …

This page explains how Managed mode prevents a live pointer from naming missing content and how it coordinates SQLite state with filesystem changes. The invariant On a supported local POSIX filesystem, a client following a Managed protocol pointer …

There are two different questions a client can ask about a repository, and SOW answers them with two separate mechanisms. Confusing them is the most common source of “I signed it but dnf still complains”, so this page starts by pulling them apart. …

Policy is the answer to “I dumped a build directory into this Dist and I do not want the debuginfo packages, and I only want the latest version of each package.” Two rules do that work, they run in a fixed order, and they run over the whole candidate …

The invariant Within one Repository, every live Package Object has one canonical payload path under pool/. Dists and architecture views own metadata, not aliases of package bytes: <repo>/pool/... canonical package payloads …

Managed mode is what you use when the same repository will be updated for months: packages arrive in batches, policy decides what stays, and you need to prove afterwards what changed and when. This page explains the three-tier model, the layout it …

SOW has two isolated execution paths. Plain mode is a stateless rebuild of one directory; Managed mode records package membership and immutable repository generations in a workspace. Neither path silently adopts state from the other. Capability …

sow create takes a directory that already contains .rpm and .deb files and writes flat repository indexes beside them. Plain mode has no workspace, configuration file, database, desired state, or operation journal. The package directory is the …