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
Metadata
Release files for skcoord 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| skcoord-0.1.2.tar.gz | 81.2 kB | With provenance | Details for skcoord-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| skcoord-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for skcoord-0.1.2-py3-none-any.whl |
Total release size: 157.3 kB
Release files / skcoord-0.1.2.tar.gz
| Download URL | skcoord-0.1.2.tar.gz |
|---|---|
| Size | 81.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bb5f12545d0a10d8f56c63e3e99d12d33ee904f3b6a250dd9967f242560c437
|
|
BLAKE2b-256 checksum How to use checksums |
284d0eb10203a3b454f3caff83004f719cc266725e4c9cbbb6a9c5b611b9690d
|
| 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 13, 2026.
Transparency logRelease files / skcoord-0.1.2-py3-none-any.whl
| Download URL | skcoord-0.1.2-py3-none-any.whl |
|---|---|
| Size | 76.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9dd39dff7aacb9180076b5648940573025f67c3dd7a44fc64bd0c7f6aeadddf
|
|
BLAKE2b-256 checksum How to use checksums |
995b205138fbaa179c6481933f102558af2c08a263eb30b2dd9f289d37928d21
|
| 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 13, 2026.
Transparency logSecurity for skcoord 0.1.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for skcoord-0.1.2.tar.gz
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 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.