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.66

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.66
File	Size	Uploaded
skcoord-0.1.66.tar.gz	431.9 kB	Sep 5, 2026	Details

Built distribution (wheel)

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

Total release size: 658.8 kB

Release files / skcoord-0.1.66.tar.gz

Download URL	skcoord-0.1.66.tar.gz
Size	431.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`3ef5e8650c6d1409970f0f921e3874000f39a8084111d3711020d31ba9af8c47`
BLAKE2b-256 checksum How to use checksums	`f8486b1d3d6f6c1eef96c24a7a8447e6e24113e56c43da123df83d7884f7f0c2`
Upload date	Sep 5, 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/c8164a277db0a60b5719cfb254fd4a5ab3f4a427

Workflow

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

Artifact

Subject: skcoord-0.1.66.tar.gz
SHA-256 checksum: 3ef5e8650c6d1409970f0f921e3874000f39a8084111d3711020d31ba9af8c47 Verifying attestations

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

Download URL	skcoord-0.1.66-py3-none-any.whl
Size	226.9 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`064161d45c3f6aa937f93955854b5cc90b71a7ac7977d07df59eb17e375683b8`
BLAKE2b-256 checksum How to use checksums	`2b48a5a4c886351cc598697f04f4a126b0e00579c4aa12bd956a682cd79dd053`
Upload date	Sep 5, 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/c8164a277db0a60b5719cfb254fd4a5ab3f4a427

Workflow

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

Artifact

Subject: skcoord-0.1.66-py3-none-any.whl
SHA-256 checksum: 064161d45c3f6aa937f93955854b5cc90b71a7ac7977d07df59eb17e375683b8 Verifying attestations