Slopsentral quickstart

Slopsentral composes source-owned engineering procedures by reference into five installable plugins. Generated provider packages and installed caches remain consumers. Software Engineering supplies the shared practice. Add a specialty when the task needs its tools or contracts. A plugin installation grants no authority to publish, deploy, or change personal configuration.

Choose the task

Task	Explanation	Operational guide
Understand owners and composition	Source ownership	Architecture
Install or update a host plugin	Command lifecycle	Command guide
Install or recover Pi	Consumer installation	Pi guide
Prepare a source change	Authoring	Documentation practice
Produce a provider package	Projection	Projection guide
Understand hook delivery	Hook lifecycle	Scoped instructions
Select a Codex profile	Profiles	Profile guide
Install portable instructions	Global instructions	Source map
Examine a release or failed publication	Release lifecycle	Release guide
Distinguish fixtures from live evidence	Evaluations	Evaluation guide
Adopt this practice in another project	Portable documentation	Packaged procedure
Review stale knowledge	Evidence model	Documentation workflow
Publish current documentation	Documentation workflow	Site guide
Select the decisive gate	Validation	Guide index

Prepare a maintainer checkout

Install the tools declared by mise.toml. From the repository root, use the public checkout commands:

mise install
mise exec -- slopsentral-setup
mise exec -- slopsentral-check
mise exec -- slopsentral-docs check

Setup synchronizes locked Python and Node dependencies. The Python gate runs Ruff, strict Pyright, and pytest within the declared scope. Projection also needs exactly Pkl 0.32.0 and a fresh output directory. Use the explicit runtime setup procedure. Consumers use qualified release assets instead of the maintainer toolchain. The general command uses uv and Python. The separate Pi launcher needs neither system Python nor uv: setup downloads and verifies a private hook interpreter before activating configuration. Managed hooks then run without system Python or uv and need no network access. Personal home storage owns runtime authority for project installations, too. Direct native package installation bypasses that provisioning; the Pi guide explains its external runtime requirement.

Read and change knowledge with the source

Use the catalog for exact plugin identities and composition. Use the glossary for established terms. Retrieve the smallest explanation that answers the current question, then examine its source before a material decision. These OKF pages preserve Claims and source evidence through OpenWiki. The repository gate links functional areas to explanations and compares reviewed source bytes. Neither a fresh digest nor valid Markdown proves factual accuracy, host consumption, or model compliance. Slopsentral uses the same distributed documentation runtime that the portable procedure supplies to other projects. The package assertions exercise that runtime in independent projects through all four provider projections. Historical audits keep their original evidence scope in the guide index. Documentation automation proposes generated wiki changes for review. It does not auto-merge or publish executable source changes.

Start here

Developer docs

Slopsentral quickstart

Choose the task

Prepare a maintainer checkout

Read and change knowledge with the source