groundskeeping
groundskeeping is a reusable Textual shell for operator tools that inspect, configure, and care for a working environment. It provides page and workbench contracts, safe actions and in-process jobs, setup wizards, oa-configurator inspection and write-flow mechanics, and normalized telemetry primitives.
Consuming applications own their production pages, domain services, safety policy, persistence, and environment-specific help. Groundskeeping owns the consistent interaction around them.
Start here
| You want to… | Read… |
|---|---|
| Use an application built with Groundskeeping | Using a Groundskeeping app |
| Integrate Groundskeeping into an application | Developer quickstart |
| Add configuration inspection or a write flow | Configuration guide |
| Understand package boundaries | What belongs where |
| Browse public contracts | API reference |
Install
Groundskeeping requires Python 3.12 or newer.
uv add groundskeeping
Run the self-contained demo:
uv run groundskeeping
The self-contained Setup page demonstrates a database-style results table with highlighted-row detail, while Configuration uses a deterministic fake provider so you can try branching, review, and apply behavior without writing a file.
Minimal composition
A Groundskeeping application starts with an OperatorAppSpec. The application wires its own services into its own page factories, then gives the resulting pages to the shell.
from groundskeeping.app import OperatorApp, OperatorAppSpec
from groundskeeping.contracts import PageRegistration, PageRoute
setup_route = PageRoute(
key="setup",
label="Setup",
purpose="Check whether this environment is ready.",
)
spec = OperatorAppSpec(
app_id="my-tool",
title="My Tool",
subtitle="environment setup",
pages=(
PageRegistration(
route=setup_route,
factory=lambda context: SetupPage(setup_service),
),
),
)
OperatorApp(spec).run()
SetupPage and setup_service stay in the consuming application. Groundskeeping supplies the frame around them.
Development
uv sync --all-extras --dev
uv run pytest -q
uv run ruff check .
uv run ty check src/
The full documentation is at AustralianCancerDataNetwork.github.io/groundskeeping.
Metadata
Release files for groundskeeping 0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| groundskeeping-0.8.1.tar.gz | 211.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| groundskeeping-0.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 291.0 kB
Release files / groundskeeping-0.8.1.tar.gz
| Download URL | groundskeeping-0.8.1.tar.gz |
|---|---|
| Size | 211.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
181c5c478fbed19b94ee6e868b593930de3f1930b211797ab554c84e88eab1e2
|
|
BLAKE2b-256 checksum How to use checksums |
8b2b3a898cd1ab1ea5e5415dd2bb963f4a9f4127e5473fa20adac95a40129299
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency logRelease files / groundskeeping-0.8.1-py3-none-any.whl
| Download URL | groundskeeping-0.8.1-py3-none-any.whl |
|---|---|
| Size | 79.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6f1cd0f460f0a4ab9d64605e26274b9f09983b434131af445c165754c83f518d
|
|
BLAKE2b-256 checksum How to use checksums |
de2356ae96fea86d9e0b69c8b27a347da482b77aa7586b1cc14dab7218c481b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 31, 2026.
Transparency log