Skip to main content
Slopsentral authors assets once, composes them by reference, and projects them into native host packages. The developer docs explain how to change those assets.

One source per asset

Generated provider trees and installed caches consume authored source. Change the source owner, then regenerate its consumers. The architecture reference explains the detailed mechanisms.

From source to a host

A plugin manifest selects canonical references, such as skills/semantic-ratchet. The graph resolver admits their identities, paths, and dependencies. The projector freezes source bytes, evaluates provider models with Pkl 0.32.0, and seals the output digests. It rejects an existing output directory. The Slopsentral command then uses the host’s installation path. Native host discovery, trust, and event delivery remain host responsibilities. See plugins and profiles and hooks and resources for concrete examples.

Host support

The projection guide owns exact provider details. A projected file establishes packaged content. A real host session establishes discovery and consumption.

Delivery and evidence

package.json owns the shared product version. Harness publication updates moving provider branches. Release publication promotes qualified retained bytes into versioned artifacts. These operations have separate owners in the release procedure. Tests and schema gates support specific contract claims. Decision evaluations examine supplied instructions. Execution evaluations need pinned repositories and independent host evidence. See schemas and evaluations for those limits. docs/site.json maps canonical pages into docs/public for Mintlify. OpenWiki keeps its native Claims and lifecycle. The documentation procedure connects source review, links, coverage, and freshness.