Skip to content
OrkMind

Open source · MIT license

Memory that stays with the work.

OrkMind organizes typed, governed memory for agents and people. Retrieve rules, decisions and documents with explicit provenance, access and history.

Get started →GitHub ↗

Types that describe what memory means

Rules, facts, decisions and documents have their own collections. Tags describe context and access; the portfolio connects products, projects and initiatives without expanding permissions.

Read the guide →

Retrieve by context, with clear limits

Tag search is deterministic. Semantic search is complementary. ACLs, protection, expiration and budget govern what may reach an agent.

Read the guide →

Integration with explicit guarantees

Prompt-building plugins for Hermes and OpenClaw inject governance per turn. MCP and CLI query on demand. Choose the integration for the behavior you need.

Read the guide →

Durable history, bounded context

The native provider maintains Core, Recall and Wiki over PostgreSQL. The turn view is bounded; intact history remains available for retrieval and auditing.

Read the guide →

Concepts

How the pieces connect

From integration to storage: context, retrieval, governance and persistence have distinct responsibilities.

Read the guide →
From integration to memoryThe integration supplies context. SemanticLayer organizes tags and budget. GovernedStore applies access and protection before querying the backend. The integration decides how results enter the prompt. 1.IntegrationcontextDetects and queries2.SemanticLayertagsFilters and orders3.GovernedStoreaccessReads and writes4.Backendpersistence
From integration to memory. The integration supplies context. SemanticLayer organizes tags and budget. GovernedStore applies access and protection before querying the backend. The integration decides how results enter the prompt.

Start with the environment

Install the package and configure the backend. The reviewed sources describe OrkMind 0.4.0, alpha, under the MIT license.

Documentation →
pip install "orkmind>=0.4.0"
orkmind store info

A governed Company Brain

The Python core governs identity, history and access. Agents and people reach the same knowledge through the CLI, MCP server and their existing hosts.

OrkMind 0.4.0

The foundation for governance

A Python library with PostgreSQL and pgvector. Published on PyPI under the MIT license.

  • Governance above the backend

    Entry protection, ACL and constitutional ordering apply above every backend.

  • History and concurrent writes

    Append-only versions and compare-and-swap prevent stale edits from silently overwriting newer work.

  • Selective encryption

    AES-256-GCM at rest for sensitive collections such as contacts, files and docs.

  • Injection detection

    Suspicious content is held for review and excluded from automatic context injection.

  • Global snapshots

    Commit, diff and restore the memory tree while preserving embeddings.

  • Provenance and receipts

    Sources, revisions and receipts support readback, reconciliation and rollback with evidence.

Inspect your own installation with these commands.

pip show orkmind
orkmind store info
orkmind --help

A shared source of truth for the whole system

Orchestrators, subagents, sessions, documents and integrations share stable identities. Knowledge outlives a session while retaining provenance and permissions.

OrkMind company brain

Governance above the adapter

From the runtime call to disk, each layer has a specific responsibility. Governance remains above storage.

runtimes

Who consumes it

  • Claude Code
  • Codex
  • Hermes
  • OpenClaw

Hosts use official contracts; identity comes from the authenticated transport.

integrations

How it arrives

  • MCP server
  • Memory provider
  • Idempotent API
  • Company Brain B1

Adapters stay thin: identity, ACL, capture and query rules live in the cores.

semantics

Where context is selected

  • Exact tag matching
  • Context detectors
  • Token budget
  • E1, E2, E3 layers
  • Optional RRF reranking
  • prod → proj → init

SemanticLayer selects context: exact matching by default, semantic retrieval as an addition.

governance

What protects it

  • Entry protection
  • ACL through access tags
  • Append-only versioning
  • Constitutional ordering
  • CAS and pinned references

GovernedStore sits above the adapter, preserving guarantees across backends.

persistence

Where it lives

  • PostgreSQL + pgvector
  • memory (tests)
  • qdrant (optional)
  • receipts + outbox

Persistence includes history, readback and reconciliation. Fixtures and fallbacks remain explicit.

Contact

Questions, proposals and contributions are welcome.

maestro@orkastery.com

Submitting opens your email application. This form sends no data to a server.