reconcilekit
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
- Enumerate targets — anything with a
name. - Fetch each target's current state.
- Compare to the desired state: already there? partly blocked?
- Dry-run → report the plan, or apply → mutate and report the outcome.
- Classify into
Status(OK,UNCHANGED,LIMITED,LIMITED_UNCHANGED,FAILED). - 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.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| reconcilekit-0.3.0.tar.gz | 9.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reconcilekit-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.7 kB
Release files / reconcilekit-0.3.0.tar.gz
| Download URL | reconcilekit-0.3.0.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b631038aa33a2a68d791a98447d4d2503469291cfea22f631df67a89ef03100
|
|
BLAKE2b-256 checksum How to use checksums |
df0547c41ebb8c14e62be3ac235de22bff1c72495f99f28cf59297c51b460eab
|
| 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 logRelease files / reconcilekit-0.3.0-py3-none-any.whl
| Download URL | reconcilekit-0.3.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5767713efe6cff321ae2254a066cd0c6ec380c1ebf28fdd38c51dd5137f33ee3
|
|
BLAKE2b-256 checksum How to use checksums |
204d5cfa64dba2048aaa1286f7194471927bfb91380a65e0b7d2b580669b8fb8
|
| 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