Skip to main content

deepseek-cordis

A lightweight Python plugin runtime for services, reactive dependencies, owned effects and events. Python 3.11+; no runtime dependencies.

PyPI distribution: deepseek-cordis. Python import: deepseek_cordis.

Version 0.1.0 is an alpha API. deepseek-cordis adapts the ownership model of the vendored Cordis 4.0.4 runtime used by DeepSeek Harness at commit 639ed015397290b3745d163aafe02ffee4aa3f84. It is an independent implementation, not the Harness application or an affiliated Cordis/DeepSeek product.

First plugin

import asyncio
from deepseek_cordis import Context


def greeter(ctx: Context, config: object) -> object:
    ctx.on("hello", lambda name: print("Hello,", name))
    return lambda: print("Greeter stopped")


async def main() -> None:
    root = Context()
    fiber = await root.plugin(greeter)
    root.emit("hello", "Cordis")
    await fiber.dispose()


asyncio.run(main())

The Fiber owns the listener and returned cleanup. Disposal removes the listener and joins teardown. Named services can gate consumers through declared dependencies; provider loss unloads them and restoration starts a new activation. Context views share an owner unless a new plugin is mounted.

Features and boundaries

  • Sync/async setup, owned cleanup, generator effects and nested plugin lifetimes.
  • Scoped service bindings, reactive injection, caller intercept options and Service classes.
  • Owned events with emit, parallel, serial, bail and waterfall dispatch.
  • Explicit plugin metadata, synchronous config validation and deterministic loader batches.
  • Typed package with a py.typed marker.

Compatibility is partial. Transparent method/property proxies, method injection, LoggerService exporters, kernel publication hooks, Fiber.update and advanced loader configuration/HMR remain unimplemented. Passing Python tests does not establish full Cordis or live DeepSeek Harness compatibility. There are no schema adapter extras.

Documentation

MIT licensed, copyright 2026 Ikram Ali. Cordis (Shigma) and DeepSeek Harness (DeepSeek) are MIT-licensed behavioral references. The distribution includes the project license and retained third-party notices; the full attribution is also available in the source repository.

Metadata

Release files for deepseek-cordis 0.1.0

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

Source distribution (sdist)

Source distribution for deepseek-cordis 0.1.0
File Size Uploaded
deepseek_cordis-0.1.0.tar.gz 206.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for deepseek-cordis 0.1.0
File Interpreter ABI Platform
deepseek_cordis-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 237.1 kB

Release files / deepseek_cordis-0.1.0.tar.gz

Download URL deepseek_cordis-0.1.0.tar.gz
Size 206.4 kB
Tags Source
SHA-256 checksum
How to use checksums
8d7c4079b18e2478f61983a90b5494a63e1eb529f42ebacaa394db5f108efac0
BLAKE2b-256 checksum
How to use checksums
f178dee24b8bd93f7e2f8efdb855b1cb74a4c2af27dbe24a324dead91c33bf5d
Upload date
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.

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 Oct 4, 2026.

Transparency log

Release files / deepseek_cordis-0.1.0-py3-none-any.whl

Download URL deepseek_cordis-0.1.0-py3-none-any.whl
Size 30.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
622df07061fd551a86fd34e75b77fa36f1f8475336774cc4f46f8d39f6898239
BLAKE2b-256 checksum
How to use checksums
17bebecfa43414427d29fd955d6d8a47842f082a8b64383e1dfe47f514693dce
Upload date
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.

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 Oct 4, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.1

2 release files

This release

0.1.0 This release

2 release files

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