decision on SOW

Coordinated Publication Decision

Fri, 14 Aug 2026 00:00:00 +0000

Decision finalized for SOW 0.4.0

An earlier version of this record proposed an rclone executor, publish --dry-run, and a separate sow audit command. None of those surfaces shipped in 0.4.0. SOW has no rclone dependency, publish has no --dry-run, and sow audit is not a command.

This page preserves the decision boundary so a historical proposal cannot be mistaken for the current product. The normative behavior is documented in sow publish and Publication & Recovery.

SOW Design Evolution: From Route Graphs to the Repository Core

Mon, 10 Aug 2026 00:00:00 +0000

This record dates to the 2026-08-10 consolidation of SOW around its Repository core. It distills the useful decisions from the earlier planning, ADR, review, migration, and verification trees without turning every intermediate artifact into maintained product documentation.

Some sealed folders use “v0.2” and “v0.3” for consecutive pre-release design lines. The version labels below refer only to released Git tags: the C2 hardlink line was replaced before v0.2.0 was tagged.

The short history

Line	Design center	Historical status
v0.1	Git/CAS ownership, route-aware materialization, edge authorization, provider workflows, and Pigsty migration	Released as v0.1.0; superseded
v0.2	Local Plain/Managed engine, Repository-scoped single-payload tree, metadata-only views, retained Generations, and target-scoped publication	Released as v0.2.0; public layout remains current
v0.3	V1 removal, package-facts caching, one-pass Plain builds, and bounded payload commits	Released as v0.3.0; same public layout
v0.4	Single-pass verification, independent RPM trust rings, explicit target rebind, and migration/recovery hardening	Current released baseline when this record was updated

The exact code and claims for each released line remain available in the v0.1.0, v0.2.0, v0.3.0, and v0.4.0 source tags.

Why SOW Uses One Payload Tree per Repository

Wed, 05 Aug 2026 00:00:00 +0000

This decision was drafted on 2026-08-05 during the pre-v0.2 release design consolidation and shipped in SOW v0.2.0 on 2026-08-08. It remains the layout contract in v0.3 and v0.4. It records an architecture choice, not a blanket compatibility claim: protocol closure, ordinary package clients, mirror tools, static hosting, and object storage are verified as separate evidence layers.

Decision

Each SOW Repository owns one public tree:

<repository>/
  pool/                         # canonical package bytes
  dists/
    <dist>/
      <architecture>/           # protocol metadata only

A Package Object has one canonical payload path inside one Repository. Adding the same object to several Dists or architecture views adds membership and metadata references; it does not create another canonical package file.