A previous release had provenance metadata, but this release does not. View details.
Cordis Core
Cordis Core is a persistent, model-agnostic cognitive core for AI agents. It does not call models, execute tools, or own an agent loop.
Version 0.1 has one narrow purpose: make evidence from a completed task change the cognitive constraints of a later task. See ROADMAP.md for the planned Runtime and optional plugin layers.
Its closed loop is:
Task -> Preflight -> Cognitive IR -> external execution -> Evidence + Outcome
-> Difference + Attribution -> state update -> next Preflight
Attribution is evidence-backed. A workflow can provide a reviewed attribution
hint only when it agrees with the evidence kind; otherwise Cordis uses
transparent evidence-kind rules and falls back to unknown rather than
inventing a causal claim. Cordis then calculates the prediction difference and
updates only the matching cognitive state.
Feedback is deliberately terminal and evidence-bound:
- each task ID is immutable and may receive exactly one feedback event;
- success must prove every required acceptance criterion from Preflight;
- outcomes, scores, and evidence cannot contradict one another;
- world patterns require independent observation sources, not duplicate evidence in one execution.
The core retains only state that can change a later decision:
- episodic memory: evidence-backed task experience;
- world patterns: repeated, evidence-backed external regularities;
- strategy statistics and normalized strategy entropy.
status() exposes aggregate domain and strategy state plus the most recent
failed events, so a host can surface a learning failure rather than silently
storing it.
Quick example
from cordis_core import CordisRuntime
runtime = CordisRuntime("cordis-state.json")
first = runtime.preflight({
"task": {
"goal": "Start an HTTP adapter in a clean environment",
"domain": "software",
"project_id": "cordis",
"strategy_id": "import_runtime_dependencies",
},
"acceptance_evidence": ["clean-environment test passes"],
})
runtime.feedback({
"task_id": first["task"]["id"],
"outcome": "failure",
"attribution": "strategy",
"lesson": "Avoid import-time runtime initialization in reusable modules.",
"evidence": [{"kind": "test", "passed": False, "summary": "clean import failed"}],
})
second = runtime.preflight({
"task": {
"goal": "Start an HTTP adapter in a clean environment",
"domain": "software",
"project_id": "cordis",
"strategy_id": "import_runtime_dependencies",
},
})
assert "repeat_failed_strategy:import_runtime_dependencies" in second["strategy"]["avoid"]
Development
cd cordis-core
python -m pip install -e .
python -m unittest discover -s tests -v
For a source-tree-only run, use $env:PYTHONPATH='src' before the test
command. The package has no runtime dependencies.
Public API
CordisRuntime.preflight(task)returns a serializable Cognitive IR.CordisRuntime.feedback(result)finalizes one task and updates state.CordisRuntime.status()returns observable aggregate state and recent failures.
Boundaries
Cordis Core intentionally excludes task intake, planning, model routing, tool
execution, HTTP serving, and agent-specific adapters. Those belong in optional
packages such as cordis-socrates, cordis-workflow, and host adapters.
Metadata
Release files for cordis-core 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)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cordis_core-0.5.1.tar.gz | 24.3 kB | Without provenance | Details for cordis_core-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cordis_core-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for cordis_core-0.5.1-py3-none-any.whl |
Total release size: 44.6 kB
Release files / cordis_core-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_core-0.5.1.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
801ae52d26eebcb8efec4e4bceffc1ded34e94a32ec8285ccdf89f9b467a73ec
|
|
BLAKE2b-256 checksum How to use checksums |
5ba7363004d21c7e03f2b20beb182fcb29bd292fe6eca306e717259a4792a907
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / cordis_core-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_core-0.5.1-py3-none-any.whl |
|---|---|
| Size | 20.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19b31cdc986eaa526bd2af903c57e8dad92161ec2b2beed218b7c825fa6928af
|
|
BLAKE2b-256 checksum How to use checksums |
80daa236b8c1a5407464e34ef7f5c4bedb55bd1bf5299057f507f5506b727239
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for cordis-core 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.