Capture one selected source snapshot
The installer reads the committed asset manifest and examines each referenced source digest. The manifest includes transitive Markdown references and necessary companion files. It preserves repository-relative paths inside the snapshot. External URLs remain citations that need network access. The destination must already exist as a real directory. Installation needs uv and Python 3.12 or 3.13. The explicit destination can represent a host instruction directory or a repository root. The tool does not select the user’s destination implicitly.AGENTS.md beside .slopsentral/<manifest-sha256>/.
That snapshot contains the pinned source map and referenced assets.
The installed root file links to those local references.
A source checkout is unnecessary for later document reads.
Publish without replacement
Source bytes enter a prepared representation only after digest examination. The installer stages the snapshot, examines its written assets, and publishes the root instructions last. Publication rejects an existing target instead of replacing it. A different existing installation is preserved as a conflict. An identical installation returnsUNCHANGED without another write.
If publication fails, cleanup removes only the unchanged new snapshot that the operation owns.
Unproved cleanup ownership produces RECOVERY_NEEDED and preserves paths for inspection.
A process interruption can leave a partial snapshot without AGENTS.md.
The next installation rejects that partial state instead of guessing its ownership.
Examine agreement and refresh deliberately
Use the same explicit destination for inspection:manifest --write.
New linked files must first enter Git’s index.
The refresh changes expected source digests without changing installed snapshots.
A different installed snapshot needs its own deliberate installation choice.
SHA-256 establishes agreement with the selected manifest.
It does not authenticate an attacker-controlled script and manifest.
The procedure assumes a trusted destination parent and does not prove crash durability or resistance to a hostile concurrent writer.
Installer tests exercise real file effects.
A successful installation does not prove that a fresh agent session loads or obeys the instructions.