charter-core
Internal runtime package for Charter. It owns workflow schema validation, step execution, run state, event models, artifact stores, and runtime adapters used by the CLI, daemon, and gateway-facing worker code.
charter-core is not a supported embedding SDK. The package root intentionally
does not export runner lifecycle helpers such as start, resume, or
submit_input; Charter's supported product interfaces are the CLI and the
gateway/control plane.
Use This Package When
- You are developing Charter runtime packages such as
charter-cli. - You need shared run protocol, event, state, or storage models inside Charter infrastructure.
For workflow authoring and local execution, use charter-cli.
For custom provider or tool integrations, use
charter-integration-sdk.
Internal Boundaries
charter-coredepends oncharter-integration-sdkbecause the runner consumes and enforces the integration contract.charter-coremust not depend on the CLI or provider implementations.- HTTP clients, terminal UX, and provider-specific code live outside this package.
Submodule Map
runner: workflow start/resume/input execution internalsruntime: managed run lifecycle used by daemon modeschema: workflow plan and form schema modelsstate,event_store: persisted run and stream contractsstorage,stores: project storage configuration and built-in adapters
Metadata
Release files for charter-core 0.0.1
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 | |
|---|---|---|---|---|
| charter_core-0.0.1.tar.gz | 71.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| charter_core-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 156.6 kB
Release files / charter_core-0.0.1.tar.gz
| Download URL | charter_core-0.0.1.tar.gz |
|---|---|
| Size | 71.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ba3c5b9acd22d51ffb5950ad350c5d65762043afd0ceb4e3ebe7fa281d641af
|
|
BLAKE2b-256 checksum How to use checksums |
fecaee65009074ff73148eb93977a63914b80a163ebfbf7a94394b9f6e41d5a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logRelease files / charter_core-0.0.1-py3-none-any.whl
| Download URL | charter_core-0.0.1-py3-none-any.whl |
|---|---|
| Size | 85.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f331216034ee4515e9c28ed8fb12cfb0bd4baa0ae50a41222cab42c7c719a012
|
|
BLAKE2b-256 checksum How to use checksums |
5a2b230c37c8e1cd0213a2a3d1fb72860f1d8f49b7e55ab40b7aa528d0b93f3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logSecurity for charter-core 0.0.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for charter_core-0.0.1.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 May 18, 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.