skcoord
Sovereign multi-agent coordination + ITIL service management, extracted from
skcapstone (CR-4.1) as the standalone coordination core. A pure Python
library: one runtime dependency (pydantic), no CLI, no daemon, no network
surface.
Maturity-tier: T0, N/A (no key material, no crypto surface). Docs: SOP.md · SECURITY.md · CONTRIBUTING.md · CHANGELOG.md
What's here
coordination: the conflict-free task board (Board,Task, each agent writes only its own files under~/.skcapstone/coordination/). Task files carry no status field; status is derived.card: the read-only unified kanbanCardprojection over tasks + ITIL, plus the per-writer overlay logcoordination/card_events/<host>.jsonl.card_store: the event-sourced Card store (~/.skcapstone/cards/<id>/core.jsonwritten once, plus append-only per-writer event logs folded on read).SKCOORD_CARD_STOREis its kill switch, not an opt-in: post Phase-4e the store is default-ON and is disabled only by0,off,false, orno(dualmeans write both, read legacy). See SOP.md section 6.lifecycle: a read-only audit and explicit repair for drift between the event-sourced kanban lifecycle and mutable agent claim projections. Repairs refuse active ownership conflicts and append per-writer JSONL receipts.itil: incident / problem / change / CAB / KEDB service management.cmdb: event-sourced configuration items + relationships.cmdb_scheduler: fail-closed scheduled-reconcile configuration, overlap lease, drift escalation, and evidence-retention helpers.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.
That also means every skcapstone process runs skcoord code: the daemon, the per-agent units, the dashboard, and skoperator all reach it through those shims.
Install
~/.skenv/bin/pip install -e .
The version is derived from the git tag by setuptools-scm, so a shallow clone
without tags builds a dev version. Use fetch-depth: 0 and fetch-tags: true.
Test
~/.skenv/bin/python -m pytest tests/ -q
~/.skenv/bin/python -m ruff check src/ tests/
License
GPL-3.0-or-later. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for skcoord 0.1.84
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.1.84.tar.gz | 511.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| skcoord-0.1.84-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 781.8 kB
Release files / skcoord-0.1.84.tar.gz
| Download URL | skcoord-0.1.84.tar.gz |
|---|---|
| Size | 511.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07fa374a817cf193207a9c4a751c3cdda22400318037fb6cd2fcdd85b8a2ee8d
|
|
BLAKE2b-256 checksum How to use checksums |
f50cdf0c9a403bf9c5fdca97cbe70a917105c67b07fae44dbbf9b2490f5d988f
|
| 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 Oct 7, 2026.
Transparency logRelease files / skcoord-0.1.84-py3-none-any.whl
| Download URL | skcoord-0.1.84-py3-none-any.whl |
|---|---|
| Size | 270.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a1878250b0c45c506ba040097b97340313441c5b4578b5fdd0881af4a131f0f
|
|
BLAKE2b-256 checksum How to use checksums |
c255d91eadbb40264bf01c7147abd1feec53a318c5b160dcf6db526a07c299a4
|
| 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 Oct 7, 2026.
Transparency log
