Skip to main content

Cordis Bridge v0.4

cordis-bridge exposes the existing CORDIS cognitive loop to a real host. It has no model, planner, HTTP server, or execution permission of its own.

The bridge provides one shared Service behind two transports:

  • a JSON-only CLI for local hosts and scripts;
  • an optional stdio MCP server for agent hosts.
host -> begin -> compact context + control signal
host -> observe / check-action -> workflow evidence
host -> finish -> Core feedback + Memory episode
later host -> begin -> changed cognition

workflow host -> workflow-begin -> task contract + difficulty policy
workflow host -> workflow-submit-plan -> active step
workflow host -> workflow-submit-step-result -> next step / replan / terminal
workflow host -> workflow-finish -> Core feedback + Memory episode

By default, durable state lives in .cordis/ below the current directory:

.cordis/state.json      Core learning state
.cordis/cognition.db    Memory and relationship graph
.cordis/focus.json      Active host-task focus for CLI/MCP process recovery
.cordis/workflow.json   Durable workflow task, plan, active step, and results

CLI

Every command reads one JSON object from a file or standard input and emits one JSON object. The input file defaults to - (standard input).

cordis begin task.json
cordis query query.json
cordis observe event.json
cordis check-action action.json
cordis finish feedback.json
cordis workflow-begin task.json
cordis workflow-submit-plan plan.json
cordis workflow-approve-step approval.json
cordis workflow-submit-step-result step-result.json
cordis workflow-finish finish.json
cordis status

Use --data-dir PATH before the command to keep a project-specific state directory elsewhere.

MCP

Install the optional transport dependency and run:

pip install "cordis-bridge[mcp]"
cordis-mcp --data-dir .cordis

The server exposes the core cordis_begin, cordis_query, cordis_observe, cordis_check_action, cordis_finish, and cordis_status tools, plus the workflow lifecycle: cordis_workflow_begin, cordis_workflow_submit_plan, cordis_workflow_submit_step_result, cordis_workflow_replan, cordis_workflow_approve_step, cordis_workflow_finish, and cordis_workflow_get. MCP tools expose their task, event, action, plan, and evidence fields directly so hosts do not need to construct transport-specific payload wrappers. For event provenance, the service/CLI field id is exposed as event_id by cordis_observe.

Concurrency boundary

CORDIS assumes one mutating host per state directory. Run one MCP server per .cordis directory and keep CLI mutations for that directory sequential. The Core JSON state and Bridge focus snapshot are deliberately small local stores; multi-writer coordination is not part of this release.

Metadata

Release files for cordis-bridge 0.5.1

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

Source distribution (sdist)

Source distribution for cordis-bridge 0.5.1
File Size Uploaded Provenance Actions
cordis_bridge-0.5.1.tar.gz 18.9 kB Without provenance Details for cordis_bridge-0.5.1.tar.gz

Built distribution (wheel)

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

Total release size: 33.4 kB

Release files / cordis_bridge-0.5.1.tar.gz

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

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

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

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

No provenance found

None of the files in this release were uploaded with provenance metadata.

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