Skip to main content

Alpha · source preview

External acceptance pending

Give specialized agents the context to act—and the boundaries to stop.

Celladore Cognitive Mesh is a governed multi-agent execution and coordination layer for teams building auditable agent workflows. It routes bounded work to specialized roles, evaluates explicit permission conditions, and preserves execution evidence without claiming consensus, collective truth, or autonomous authority.

Inspect the CLI preview Repository (access required) Review the alpha boundary

Observable execution trace

Every activation has a reason and a record.

The workflow is a sequence of bounded decisions, not a black-box swarm. Each stage has a distinct responsibility and leaves evidence for review.

  1. 01 · CONTEXT Bound the request

    Share only the context required for the assigned role.

  2. 02 · ROUTE Select a specialist

    Match work to an explicit capability and role boundary.

  3. 03 · GATE Permit or deny

    Evaluate policy, access, and workflow conditions before action.

  4. 04 · EXECUTE Activate the role

    Run only the behavior supported by the selected engine.

  5. 05 · EVIDENCE Preserve provenance

    Retain traceable decision and execution records for review.

Implemented product boundary

Coordination with named controls.

The repository contains implemented engines and adapters alongside interfaces, experimental components, and planned integrations. A documented port is not presented as a deployed capability.

Routing and role boundaries

Coordinate specialized agents with bounded context instead of collapsing them into a generic team.

Deliberation and evaluation

Use deliberation, evaluation, or voting only where the selected implemented engine provides it.

Policy and RBAC gates

Make permission conditions explicit at execution boundaries and deny work when a required condition is absent.

Audit and provenance

Keep decision and execution evidence available for operators and downstream attribution.

CLI preview

A narrow client, not a second runtime.

The prepared @celladore/cognitive-mesh package exposes the cognitive-mesh executable. It reads documented HTTP interfaces and keeps orchestration logic in the backend. Publication is a separate authorization gate.

init stores endpoints, never credentials. doctor separates endpoint health from authenticated acceptance. run and evaluate remain local validation previews until stable server contracts are approved.

Intended commands after separately approved publication 

npx @celladore/cognitive-mesh --help
npx @celladore/cognitive-mesh init --api-url https://api.example.com
npm install -g @celladore/cognitive-mesh

cognitive-mesh doctor --json
cognitive-mesh agents --json
cognitive-mesh evaluate --sandbox --input "review this proposal"
cognitive-mesh run --sandbox --workflow demo
status: validated
mode: sandbox
executed: false
note: local validation only

A clear place in the Celladore stack.

Baton owns durable work

Tasks, handoffs, approvals, and authority receipts stay in Baton.

Cognitive Mesh governs execution

Bounded context, role activation, policy decisions, evaluation, and provenance belong here.

Sluice owns provider traffic

Model routing, provider fallback, request policy, and gateway telemetry stay in Sluice.

esc