Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

katalyst-core

The LinkML module every Katalyst schema module imports (src/katalyst_core/schema/katalyst_core.yaml):

  • Node: the base node. Identity (id, a URI under a declared prefix; core itself is https://w3id.org/katalyst/core/, prefix kc:), kind, name, description.
  • Lifecycle: lifecycle_state, one lifecycle for every node of every kind (draft, proposed, active, deprecated, rejected, retired). The LifecycleState enum declares it with annotations on its values (transitions_to, initial, default, hidden, gate); a kind inherits it, cannot change it, and may declare lifecycle_gates for entering a state. A record that does not say is active. See docs/user-guide/concepts/lifecycle.md.
  • Provenance: source, activity, derived_from, and forced_moves (a lifecycle move made against the rules, with who and why).
  • Two times: valid time (valid_from/valid_to) and recorded time (recorded_from/recorded_to).
  • Relation: a reified relationship (subject, predicate, object) with a confidence and its own provenance and times.
  • The extension bag (extensions): data no loaded module defines, kept and never deleted.
  • DeletePolicy (block, cascade, detach, redirect): every relationship slot carries one as its delete_policy annotation.
  • parent: the structural parent edge (child_of). A class lists it under slots: and names its parent kinds under slot_usage: parent:. No module defines parent again; one that does is refused when it loads.

A module imports it as katalyst_core:

imports:
  - linkml:types
  - katalyst_core

The Python package defines no schema. It opens modules (open_module), holds them to the core contract (contract.check_contract, kata core check), and moves records between YAML and RDF (graph.to_graph / graph.from_graph, kata core save / kata core load).

Lint the schema with the LinkML linter: just core-lint. The full linkml toolchain is a runtime dependency, so validation and linting are available wherever core is.

Metadata

Release files for katalyst-core 0.3.2a17

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

Source distribution (sdist)

Source distribution for katalyst-core 0.3.2a17
File Size Uploaded Provenance Actions
katalyst_core-0.3.2a17.tar.gz 45.5 kB With provenance Details for katalyst_core-0.3.2a17.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for katalyst-core 0.3.2a17
File Interpreter ABI Platform Actions
katalyst_core-0.3.2a17-py3-none-any.whl Python 3 none any Details for katalyst_core-0.3.2a17-py3-none-any.whl

Total release size: 93.7 kB

Release files / katalyst_core-0.3.2a17.tar.gz

Download URL katalyst_core-0.3.2a17.tar.gz
Size 45.5 kB
Tags Source
SHA-256 checksum
How to use checksums
3426014711ac1b84e6f0cb563b7b0b5d3743d31e718339ae55a771eddfcf841e
BLAKE2b-256 checksum
How to use checksums
a84653f7e83291cad2bd2236baa222a1baed515c38e65ac056d8c27a093f2c7a
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 7, 2026.

Transparency log

Release files / katalyst_core-0.3.2a17-py3-none-any.whl

Download URL katalyst_core-0.3.2a17-py3-none-any.whl
Size 48.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ce525126a1a326443a5c0e5ab8c0e5e58952537328557fd914784f39417fd00a
BLAKE2b-256 checksum
How to use checksums
2be1a827abce236b18a6676536ceaac948ec7978482f3235df7cf913be06b6c1
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 7, 2026.

Transparency log

Security for katalyst-core 0.3.2a17

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.

Select from 2 files

Attestation for katalyst_core-0.3.2a17.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 7, 2026.

Transparency log

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

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page