ioc-concord
The CONCORD protocol as a library. Stdlib only, Python 3.11 or later. It never prints, exits or keeps module-level state:
it raises typed errors (all ConcordError, each with a code).
| Module | Contents |
|---|---|
errors |
ConcordError and its subclasses |
xmlutil |
escaping and element helpers, document regexes |
schema |
parse, validate and render a candidate schema; check a candidate against it |
engine |
the decision engine: candidates, ratings, leximin selection, repair rounds |
wire |
the protocol vocabulary, request builders, reply builders and parsers |
store |
the Store protocol and an atomic FileStore |
state |
constructors and checks for run and agent state |
The skill scripts under protocols/concord/skills/ carry a generated copy of the code they use from these modules, so each stays a single
self-contained file. Edit the library, then run just sync from the repository root; CI runs just check-sync.
uv run --project packages/ioc-concord pytest
Metadata
Release files for ioc-concord 0.1.0
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 |
|---|---|---|---|---|
| ioc_concord-0.1.0.tar.gz | 27.0 kB | With provenance | Details for ioc_concord-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ioc_concord-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for ioc_concord-0.1.0-py3-none-any.whl |
Total release size: 46.4 kB
Release files / ioc_concord-0.1.0.tar.gz
| Download URL | ioc_concord-0.1.0.tar.gz |
|---|---|
| Size | 27.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e19f8b92c1b0c63d04a069793c8aaff2c7828eea3867c5f38b48ad56f2d33e9
|
|
BLAKE2b-256 checksum How to use checksums |
13e73608438e83f5439986b01e464c94ae682b53ce41d9590e29a54ce36def45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logRelease files / ioc_concord-0.1.0-py3-none-any.whl
| Download URL | ioc_concord-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1a361380e4e1fe0d564be298cdbaf54b5cc438f495c737305681413a3cf6f2b3
|
|
BLAKE2b-256 checksum How to use checksums |
a0518740245fc77549bfe24d798c58820728b701483f09e576152e7f8327e6af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logSecurity for ioc-concord 0.1.0
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 ioc_concord-0.1.0.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 Nov 10, 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.