Skip to main content

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.

Groundskeeping demo layout

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.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for groundskeeping 0.8.0
File Size Uploaded
groundskeeping-0.8.0.tar.gz 211.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for groundskeeping 0.8.0
File Interpreter ABI Platform
groundskeeping-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 290.6 kB

Release files / groundskeeping-0.8.0.tar.gz

Download URL groundskeeping-0.8.0.tar.gz
Size 211.0 kB
Tags Source
SHA-256 checksum
How to use checksums
0e6be41e809ea47771f26456566743318383d83be6a6ca1e03271a447d5f12ef
BLAKE2b-256 checksum
How to use checksums
88cc8d6187650b7fde86a8272a2213334c14a6bd74acc6d91ead4600338de431
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 30, 2026.

Transparency log

Release files / groundskeeping-0.8.0-py3-none-any.whl

Download URL groundskeeping-0.8.0-py3-none-any.whl
Size 79.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6b5fd11e0ec83ccfb6cd2950500a8b0d23477386c9d5bd72f6f4acf181a1089b
BLAKE2b-256 checksum
How to use checksums
43b768ade29bb645dfb4395caf7fcec2f1fb9275bc9f260d941a8d133608abde
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 30, 2026.

Transparency log

Release history Release notifications | RSS feed

0.9.1

2 release files

0.9.0

2 release files

0.8.1

2 release files

This release

0.8.0 This release

2 release files

0.7.0

2 release files

0.6.1

2 release files

0.6.0

2 release files

0.5.1

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page