Skip to main content

mirra-sdk

One wrapper call gives any agent a persistent recognized identity, tamper-evident portable memory of its relationships, behavior that adapts per relationship, and execution that only happens when verified.

import mirra

wrapped = mirra.wrap(my_agent, principal="team-key-1", profile="dev_balanced")

wrapped.identity                     # recognized across sessions, not met fresh
wrapped.remember("alice", "…")       # signed scroll — verify-on-read, fail-closed
wrapped.recall("alice")              # only cryptographically verified memories
wrapped.interact("alice", "hi")      # context built from alice's own history
wrapped.execute("shell.exec", "…")   # deterministic, signed decision record

This is Edge 1 (the SDK) of the MIRRA platform's one-core/three-edges architecture. The SDK speaks only the frozen v1 core contract (mirra-core-contract); the enforcement engine (MVAR via ClawZero) and the signed memory store (ClawSeal) plug in beneath it, and optional capability providers can be injected at runtime for identity enrichment and epistemic verification.

The four pillars

Pillar API Guarantee
Recognition wrapped.identity Same principal → same identity + fingerprint across sessions; keys generated on first run, never stored in a repo
Portable signed memory remember / recall / verify Sign-on-write, verify-on-read; tampered memories are dropped, never returned
Per-relationship behavior interact / build_context The agent sees each subject's own verified history
Permissioned execution execute / protect_tool Deterministic allow/block with an Ed25519-signed witness; forged records fail verification; no engine → refuse

Profiles: build against dev_balanced (safe actions allow, hostile ones block, risky ones step up). The default is prod_locked — the fail-closed production posture where every action is refused unless the caller supplies risk context or step-up approval. If you omit profile and everything blocks, that is the lockdown working as designed.

LangChain (whole-agent, not just tools)

Existing security adapters wrap individual tools. This wraps the whole agent — identity, signed memory, per-user context, and enforcement — in LangChain's own idioms:

pip install "mirra-sdk[langchain]" mvar-security clawzero clawseal
from mirra.adapters.langchain import wrap_agent, MirraChatMessageHistory

# per-user signed chat history (verify-on-read), for RunnableWithMessageHistory
history = MirraChatMessageHistory(principal="acme", subject_id="alice")

# or bind a whole chain: each .invoke resolves that subject's verified history,
# hands it to the chain, and records the exchange as a new signed scroll
bound = wrap_agent(my_chain, principal="acme")
bound.invoke("what did we discuss?", subject_id="alice")
safe_tool = bound.protect_tool(shell_tool, sink="shell.exec")   # reuses ClawZero

MirraChatMessageHistory is a real BaseChatMessageHistory, so it drops into RunnableWithMessageHistory (and anywhere a chat-history store is accepted). The adapter never imports LangChain at module load — only when you use it.

Fail-closed by design

  • No enforcement engine → every action is blocked, never silently allowed.
  • No memory backend → wrap() raises, never runs with unsigned memory.
  • Damaged identity keystore → raises, never silently mints a new identity.
  • Tampered scroll or forged decision record → fails verification.

Demo

Installed (pip):

mirra-demo                   # live 5-check report; run twice — the second run proves recognition

From a checkout:

python3 demo/demo_sdk.py     # narrative version of the same proof

See DEMO.md for the five-minute walkthrough.

Tests

python3 -m pytest tests/ -q

The suite is organized by acceptance criterion: test_recognition.py, test_signed_memory.py, test_differentiated_behavior.py, test_permissioned_execution.py, test_boundary.py (public/private leak gate).

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mirra_sdk-0.1.2.tar.gz (41.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mirra_sdk-0.1.2-py3-none-any.whl (38.8 kB view details)

Uploaded Python 3

File details

Details for the file mirra_sdk-0.1.2.tar.gz.

File metadata

  • Download URL: mirra_sdk-0.1.2.tar.gz
  • Upload date:
  • Size: 41.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.0

File hashes

Hashes for mirra_sdk-0.1.2.tar.gz
Algorithm Hash digest
SHA256 42409002d099003ac4e030a5e02699cfd7e0b52f3563f7ba318f97a786c1f968
MD5 2ec7b69acb9a172f60a1f6fe33f9a2b8
BLAKE2b-256 b5af6d63ce4ed405b71d2fbfcec1394de962b69e03c3bb34cbf1f92b7e7d25e2

See more details on using hashes here.

File details

Details for the file mirra_sdk-0.1.2-py3-none-any.whl.

File metadata

  • Download URL: mirra_sdk-0.1.2-py3-none-any.whl
  • Upload date:
  • Size: 38.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.0

File hashes

Hashes for mirra_sdk-0.1.2-py3-none-any.whl
Algorithm Hash digest
SHA256 ea4516b01fb5c4b40f6fc15824fbe093293e8846ef9da043facb0b745048a8eb
MD5 a0911a9c4a033886bbc2ba9183f61f88
BLAKE2b-256 0c6537abb6724e0b1ef32200d1a5df8d43408f1fe3483d0f689fe32cb63de9ec

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page