Skip to main content
Loss of provenance

A previous release had provenance metadata, but this release does not. View details.

Cordis Runtime v0.4

Cordis Runtime is the minimal host bridge for Cordis Core. It does not call a model and it does not split tasks.

The semantic boundary is explicit:

user language
    -> host/main model interprets intent
    -> structured Task Contract
    -> Cordis Runtime + Core
    -> difficulty policy + model context
    -> optional Planner proposes PlanIR
    -> Runtime admits plan, advances steps, then closes Core feedback

For an agent with tool calling, the host/main model fills the task contract as part of its normal turn. The optional cordis-planner can use a model callable to propose a PlanIR. Neither Runtime nor Planner executes a tool: Runtime owns the deterministic workflow state and the host remains the executor.

Minimal use

from cordis_core import CordisRuntime
from cordis_runtime import CordisHostRuntime

runtime = CordisHostRuntime(CordisRuntime("cordis-state.json"))

turn = runtime.begin({
    "task": {
        "goal": "Fix the login integration test",
        "domain": "software",
        "project_id": "my-app",
        "strategy_id": "inspect_logs_first",
        "stakes": "medium",
    },
    "complexity": 0.4,
    "current_step": "Inspect the failing test and logs",
    "constraints": ["Do not change the database schema"],
    "acceptance_evidence": ["login integration test passes"],
})

# Send turn["model_context"] to the host's existing planner or main model.

The host calls check_action(...) before an action, observe(...) for any plan/tool/artifact/test/error event, and finish(...) with observable evidence after execution. When constructed with a CognitiveStore, Runtime retrieves a small project-safe snapshot on begin, supports deduplicated query(...), and persists the final episode through finish(...).

Managed host lifecycle

Hosts should normally use CordisManagedSession instead of asking a model to construct separate begin, observe, and finish calls. The host creates the task once, translates its own tool/test telemetry into a small typed event set, then closes from accumulated evidence:

from cordis_runtime import CordisManagedSession

session = CordisManagedSession(runtime)
turn = session.start(task_payload)

# The host, not the model, emits this after its test runner returns.
session.record({
    "type": "test_passed",
    "summary": "pytest tests/test_login.py passed",
    "acceptance_id": "criterion-1",
    "tool": "pytest",
})
result = session.complete(lesson="The login integration test now passes.")

tool_succeeded, tool_failed, test_passed, test_failed, verification_passed, verification_failed, and note are supported. The session rejects malformed, unknown, and out-of-order events; it derives the final result from declared acceptance evidence rather than trusting a model to claim success.

Workflow boundary

Runtime provides:

  • structured Task Contract validation through Core;
  • task-local Focus State;
  • deterministic control modes;
  • compact model context;
  • an experimental lexical drift heuristic, never a safety or attention guarantee;
  • evidence-bound feedback delegation.
  • optional CognitiveStore retrieval, event capture, and episode write-back.
  • a durable workflow controller for task contracts, six-axis difficulty, PlanIR admission, active steps, results, explicit replan, and feedback closure.

Runtime does not provide natural-language interpretation, model selection, provider SDKs, tool execution, parallel scheduling, durable conversation memory, or an HTTP service. The optional planner can propose plans but cannot approve or execute them.

check_action is deliberately conservative metadata: it reports lexical overlap and obvious destructive terms. Hosts must not treat it as semantic understanding, an authorization decision, or a complete attention-drift guard.

Metadata

Release files for cordis-runtime 0.5.1

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

Loss of provenance

These files do not have provenance metadata, despite files in a prior release including this data.

We recommend further investigation before installing these files. View details.

Source distribution (sdist)

Source distribution for cordis-runtime 0.5.1
File Size Uploaded Provenance Actions
cordis_runtime-0.5.1.tar.gz 22.7 kB Without provenance Details for cordis_runtime-0.5.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cordis-runtime 0.5.1
File Interpreter ABI Platform Actions
cordis_runtime-0.5.1-py3-none-any.whl Python 3 none any Details for cordis_runtime-0.5.1-py3-none-any.whl

Total release size: 41.3 kB

Release files / cordis_runtime-0.5.1.tar.gz

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL cordis_runtime-0.5.1.tar.gz
Size 22.7 kB
Tags Source
SHA-256 checksum
How to use checksums
faefdb4528761410b633db7f24b9674ea1cb4d4d78c3ec49ffe6d94aac3a6f0c
BLAKE2b-256 checksum
How to use checksums
c7a544b79979ac985e0596909d5be577e3052d116a747e688ba723d6acae16ee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / cordis_runtime-0.5.1-py3-none-any.whl

Loss of provenance

This file belongs to a release without provenance metadata, despite a prior release including this data.

We recommend further investigation before installing this file. View details.

Download URL cordis_runtime-0.5.1-py3-none-any.whl
Size 18.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d93b4e54819f56983168e958cc6a9a895eee7192e48c9364466deada73504555
BLAKE2b-256 checksum
How to use checksums
c961f739ed6861113d64fdc1bbd8cd092c033b26757202203d29205d2f23d645
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Security for cordis-runtime 0.5.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.

Loss of provenance

A previous release of these files had provenance metadata, but this release does not.

While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.

Release comparison

  • Removed 0.4.0 2 files With provenance
  • Added 0.5.1 2 files Without provenance

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.

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