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 kanban Card projection over tasks + ITIL, plus the per-writer overlay log coordination/card_events/<host>.jsonl.
card_store: the event-sourced Card store (~/.skcapstone/cards/<id>/core.json written once, plus append-only per-writer event logs folded on read). SKCOORD_CARD_STORE is its kill switch, not an opt-in: post Phase-4e the store is default-ON and is disabled only by 0, off, false, or no (dual means 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.

Release files for skcoord 0.1.57

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

Source distribution (sdist)

Source distribution for skcoord 0.1.57
File	Size	Uploaded
skcoord-0.1.57.tar.gz	412.7 kB	Sep 1, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for skcoord 0.1.57
File	Interpreter	ABI	Platform	Reset
skcoord-0.1.57-py3-none-any.whl 215.8 kB Sep 1, 2026	Python 3	none	any	Details

Total release size: 628.5 kB

Release files / skcoord-0.1.57.tar.gz

Download URL	skcoord-0.1.57.tar.gz
Size	412.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`6c2d09fd3d6b7bc4b6f6f2cb3994e4b8b6484f78b471cff032afb6d8106aba9b`
BLAKE2b-256 checksum How to use checksums	`18c45a8b239a2cd0338f9931269878dcee100b12205cd750ab565df72c12e05d`
Upload date	Sep 1, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/smilinTux/skcoord
Publishing commit: github.com/smilinTux/skcoord/tree/d5c20dc2e9c01544a702e9c416b5add8d9f2808f

Workflow

Publishing configuration: github.com/smilinTux/skcoord/blob/d5c20dc2e9c01544a702e9c416b5add8d9f2808f/.github/workflows/publish.yml
Publishing logs: github.com/smilinTux/skcoord/actions/runs/33504886242/attempts/1

Artifact

Subject: skcoord-0.1.57.tar.gz
SHA-256 checksum: 6c2d09fd3d6b7bc4b6f6f2cb3994e4b8b6484f78b471cff032afb6d8106aba9b Verifying attestations

Release files / skcoord-0.1.57-py3-none-any.whl

Download URL	skcoord-0.1.57-py3-none-any.whl
Size	215.8 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`978b11611ed49f5a0613d7a90856c6f82425d3aa196b5ddcac9348e11d85b677`
BLAKE2b-256 checksum How to use checksums	`bb40aeb09d3913ecb24c16db56cf97d793e969ed8aa14047ba402218343e9c4b`
Upload date	Sep 1, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/smilinTux/skcoord
Publishing commit: github.com/smilinTux/skcoord/tree/d5c20dc2e9c01544a702e9c416b5add8d9f2808f

Workflow

Publishing configuration: github.com/smilinTux/skcoord/blob/d5c20dc2e9c01544a702e9c416b5add8d9f2808f/.github/workflows/publish.yml
Publishing logs: github.com/smilinTux/skcoord/actions/runs/33504886242/attempts/1

Artifact

Subject: skcoord-0.1.57-py3-none-any.whl
SHA-256 checksum: 978b11611ed49f5a0613d7a90856c6f82425d3aa196b5ddcac9348e11d85b677 Verifying attestations