Skip to main content

continuum

Change impact from Party's Continuum, for people and coding agents: what a change reaches, how risky it is, which tests reach it, and what no test reaches. Continuum keeps a dependency graph of each repository current as its default branch changes; this CLI asks it about your checkout.

pip install party-continuum        # or: brew install maitai-inc/continuum/continuum
continuum login                    # a browser code; saves a revocable token

Before an edit:

continuum dependents billing/charge.py::charge --depth 2   # what depends on it
continuum impact --plan charge --change signature          # the reach of a planned change

After an edit (the working tree against the default branch):

continuum impact      # reach, impact and risk grades, and what drives them
continuum tests       # every test that reaches the change, with commands to run them
continuum untested    # reached code that no test reaches: add tests here
continuum explain api/refunds.py::refund   # why the change reaches it

Every command takes --json. --repo owner/name overrides the checkout's GitHub origin, and --base / --head choose what to compare.

Impact and risk are separate. Impact is how much behavior the change can reach. Risk is how much of that no test would notice: reached code no test reaches, code still using something the change removes, and changes Continuum cannot see through. A wide, well-tested change is high impact and low risk; a small change to untested code is the reverse. Both are graded against the repository's own recent changes.

What it sends. The paths of your changed files and the contents of changed text files (at most 4 MB); never other files, and nothing unless you run a command. The graph lives with Continuum, so answers take about a second.

Tokens. continuum login saves a token that reads Continuum and nothing else; logging in again or using it keeps it alive, and continuum logout revokes it. For CI and agent Environments, create a fixed token and set it as CONTINUUM_TOKEN:

continuum token create --name "skipper Environment" --repo maitai-inc/skipper --days 90
continuum token list
continuum token revoke <id>

Requirements: Python 3.11+ and git. Continuum is for members of the Party organization; CONTINUUM_URL points the CLI at another Party server.

Metadata

Release files for party-continuum 0.2.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 party-continuum 0.2.0
File Size Uploaded
party_continuum-0.2.0.tar.gz 16.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for party-continuum 0.2.0
File Interpreter ABI Platform
party_continuum-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 34.5 kB

Release files / party_continuum-0.2.0.tar.gz

Download URL party_continuum-0.2.0.tar.gz
Size 16.5 kB
Tags Source
SHA-256 checksum
How to use checksums
50ba114ea0e66f8f7b0f65c7e29740600bbc81c3b789111c22b707871e9749f7
BLAKE2b-256 checksum
How to use checksums
32bb3ed1b20bcefa1f2c1d7f5d4b849f3adc4f18743c5efa33e4e49f10286bd4
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 Sep 29, 2026.

Transparency log

Release files / party_continuum-0.2.0-py3-none-any.whl

Download URL party_continuum-0.2.0-py3-none-any.whl
Size 18.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bede1c85d5b7e341217ba876e5f9454127d6de3f66e01b774c0a1fd78a10038d
BLAKE2b-256 checksum
How to use checksums
6e7f358f18160823d8bf1b562802bd971e4e74c17015660c01e8ce1f21b5a01d
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 Sep 29, 2026.

Transparency log

Release history Release notifications | RSS feed

0.4.0

2 release files

0.3.0

2 release files

0.2.1

2 release files

This release

0.2.0 This release

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