publish: the public projection begins here

This is a projection, not a development branch. The tree above was constructed
from the internal source named below under a manifest that decides which paths
may leave, then scanned as a whole tree rather than as a series of patches, and
only then published.

Public history starts here because the history before it was not admissible,
and neither was the tree. What used to stand in this repository included a
rescue copy of another machine, a directory of phone handoffs, deployment
wired to one house, and a submodule pointing at a forge no stranger can reach.
None of that was ever the product. It stays in the private forge, which is
allowed to hold the whole working organism, and this is what was deliberately
sent out instead.

Three mechanisms produced this tree, in decreasing order of trust. A top-level
path the manifest does not name never arrives at all, which is the one that
catches directories nobody has thought of yet. Named internal files inside
admitted roots are dropped. A short, reviewed table replaces deployment
defaults that a public build must not carry -- an endpoint aimed at one LAN, a
VPN profile belonging to one phone, packaging built from one checkout path.

Everything after this commit is an ordinary publication with the same three
trailers, so a force push stops being routine and starts meaning that
something deliberate happened. The trailers bind the projection to its source
without pretending the public SHA is the private one: same lineage, different
tree, and the record says so.

Source-Sha: 8f27b1e76a8fef560a336aba18e6990713ff1047
Policy-Sha: 6b261d2f3e6e1fb19874846ba4bb1dfe15565d25b8618c1c1afba0419c101d27
Tree-Digest: 18ec3563c5e5ef9a414993a9f6734b251ff9ed3cd56eebdd6cac01e45c6e3067

packaging/souveraine-machined.service

@@ -0,0 +1,54 @@
+# Souveraine machine identity — SYSTEM unit (contrast souveraine.service,
+# which is a user unit). Runs from boot, before any human authenticates;
+# owns the machine seed and serves signatures over a Unix socket.
+#
+# Access control is the socket: /run/souveraine (0750 souveraine:souveraine)
+# + machined.sock (0660). Add session users to the `souveraine` group:
+#   usermod -aG souveraine <user>
+#
+# Provision the seed before first start:
+#   sudo souveraine machine init --fresh
+#   sudo souveraine machine init --migrate-from /home/<user>/.souveraine/seed-id
+[Unit]
+Description=Souveraine machine identity (system tier)
+
+[Service]
+User=souveraine
+Group=souveraine
+ExecStart=/usr/bin/souveraine-machined
+Restart=on-failure
+RestartSec=5
+
+# /var/lib/souveraine — the seed. /run/souveraine — the socket.
+StateDirectory=souveraine
+StateDirectoryMode=0700
+RuntimeDirectory=souveraine
+RuntimeDirectoryMode=0750
+UMask=0007
+
+# Network-less signer, RedFlag-executor posture: nothing to reach, nothing
+# reachable. AF_UNIX only, no privileges, no writable system.
+NoNewPrivileges=yes
+CapabilityBoundingSet=
+RestrictAddressFamilies=AF_UNIX
+IPAddressDeny=any
+ProtectSystem=strict
+ProtectHome=yes
+PrivateTmp=yes
+PrivateDevices=yes
+ProtectKernelTunables=yes
+ProtectKernelModules=yes
+ProtectControlGroups=yes
+ProtectClock=yes
+ProtectHostname=yes
+LockPersonality=yes
+MemoryDenyWriteExecute=yes
+RestrictRealtime=yes
+RestrictNamespaces=yes
+RestrictSUIDSGID=yes
+SystemCallArchitectures=native
+SystemCallFilter=@system-service
+SystemCallErrorNumber=EPERM
+
+[Install]
+WantedBy=multi-user.target