Skip to main content

reconcilekit

PyPI

A tiny, stateless fetch-diff-apply reconciliation kernel — the pattern a fleet-wide config tool repeats for every resource it manages, with none of the domain specifics.

There is no state file, no backend, no daemon. Each run reads live state, compares it to what you want, and either reports the plan or applies it.

The pattern

  1. Enumerate targets — anything with a name.
  2. Fetch each target's current state.
  3. Compare to the desired state: already there? partly blocked?
  4. Dry-run → report the plan, or apply → mutate and report the outcome.
  5. Classify into Status (OK, UNCHANGED, LIMITED, LIMITED_UNCHANGED, FAILED).
  6. Run the fleet in bounded parallel, isolating per-target failures and raising them together at the end.

API

Full API reference, generated from the docstrings: hugoh.github.io/gh-workflows/reconcilekit (rebuilt on every push that touches this package -- see .github/workflows/docs.yml).

Example

import asyncio
from dataclasses import dataclass

from reconcilekit import (
    Result,
    Status,
    classify_status,
    result_line,
    run_parallel,
    run_reconcile,
)


@dataclass
class File:
    name: str
    path: str
    want: str


def make_worker(dry_run: bool):
    async def worker(f: File) -> Result[File]:
        async def fetch() -> str:
            return f.path_text()  # read current contents

        def plan(current: str) -> Result[File]:
            status = classify_status(
                at_target=current == f.want, changed=current != f.want
            )
            return Result(
                f,
                result_line(
                    f.name, "would rewrite" if current != f.want else "ok", status
                ),
                status,
            )

        async def apply(current: str) -> Result[File]:
            if current != f.want:
                f.write(f.want)
            status = classify_status(at_target=True, changed=current != f.want)
            return Result(
                f,
                result_line(f.name, "written" if current != f.want else "ok", status),
                status,
            )

        return await run_reconcile(
            dry_run=dry_run, fetch=fetch, plan_result=plan, apply_result=apply
        )

    return worker


asyncio.run(run_parallel(files, make_worker(dry_run=True)))

Consumers

repo-admin/ (in this repo) uses it for every account-wide GitHub sync command, consumed as a uv workspace member there.

Metadata

Release files for reconcilekit 0.3.1

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

Source distribution (sdist)

Source distribution for reconcilekit 0.3.1
File Size Uploaded
reconcilekit-0.3.1.tar.gz 9.1 kB Details

Built distribution (wheel)

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

Total release size: 17.9 kB

Release files / reconcilekit-0.3.1.tar.gz

Download URL reconcilekit-0.3.1.tar.gz
Size 9.1 kB
Tags Source
SHA-256 checksum
How to use checksums
f29cc95a7c8919ab1836d6050c3f7a6cc6cf1b33409501d21ebcc841ee8a2857
BLAKE2b-256 checksum
How to use checksums
b8624590d625defbe5644058cb242d989b129522566f2e831c91bebd6c8f093a
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 4, 2026.

Transparency log

Release files / reconcilekit-0.3.1-py3-none-any.whl

Download URL reconcilekit-0.3.1-py3-none-any.whl
Size 8.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5219856c200efcfe87db3ef6051e155eb86fc376635a49e4393efb2ba7dd23e0
BLAKE2b-256 checksum
How to use checksums
c1d18d37f811629125efa4c68de2d824753eba7876a252d4c98716744bce0785
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 4, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

0.4.1

2 release files

0.4.0

2 release files

This release

0.3.1 This release

2 release files

0.3.0

2 release files

0.2.0

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