This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 0.1.82 instead.
Reason given by maintainers: Spurious: CI tag job walked ancestry and cut 0.0.2 below the existing 0.1.0. Not a real release.
skcoord
Sovereign multi-agent coordination + ITIL service management, extracted from
skcapstone (CR-4.1) as the standalone coordination core.
What's here
coordination— the conflict-free task board (Board,Task, each agent writes only its own files under~/.skcapstone/coordination/).card— the read-only unified kanbanCardprojection over tasks + ITIL.card_store— the event-sourced Card store (cards/<id>/core.json+ append-only per-writer logs), gated bySKCOORD_CARD_STORE.itil— incident / problem / change / CAB / KEDB service management.cmdb— event-sourced configuration items + relationships.agent_card— the shareable sovereign identity vCard for the mesh.atomic_io— atomic file-write helper shared by the above.
Dependency direction
Import-time dependencies flow one way: skcapstone depends on skcoord.
The few reverse edges into skcapstone internals (skjoule, active_agent_name,
gtd_tools, pubsub, activity) are runtime-lazy inside the methods that use
them, so there is no import-time cycle. In skcapstone, skcapstone.coordination
/ .card / .card_store / .itil / .cmdb / .agent_card / .atomic_io remain
as re-export shims, so every existing importer keeps working byte-identically.
Install
~/.skenv/bin/pip install -e .
Test
~/.skenv/bin/python -m pytest tests/ -q
1 maintainer
Release files for skcoord 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| skcoord-0.0.2.tar.gz | 73.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skcoord-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 145.8 kB
Release files / skcoord-0.0.2.tar.gz
| Download URL | skcoord-0.0.2.tar.gz |
|---|---|
| Size | 73.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
346abd52818594993dce815988944227cc6c4f1a19e8d747dbcf9d79f80f4ad4
|
|
BLAKE2b-256 checksum How to use checksums |
898bb3c4e64cd72a6f15eb3baff84f54b1a8d8d7caf5dd0da44f30542abbe67e
|
| 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 8, 2026.
Transparency logRelease files / skcoord-0.0.2-py3-none-any.whl
| Download URL | skcoord-0.0.2-py3-none-any.whl |
|---|---|
| Size | 72.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
591782301dc8e13e2b35b5fa2f8604dad4b40562e65bf3131f178f8d32fef359
|
|
BLAKE2b-256 checksum How to use checksums |
98bc9c1ba36913a6b542d0f9555dc8f14c1e37591e7ed73124297e089013f574
|
| 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 8, 2026.
Transparency log
