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.