[sunilp]

Summary

Cross-link Engram with JamJet so the funnel between the two projects exists.

Changes

1. New "Use with JamJet" section in README

Inserted between the 60-second tour and Core concepts. Explains:

• Engram = "what does this user/agent remember?"
• JamJet = "what happens when the process restarts mid-execution?"
• Three composition patterns: Python + JamJet Python SDK; Java/Spring + engram-spring-boot-starter + JamJet Java Runtime; anything-MCP-aware
• Engram still works fine standalone

2. New examples/06_with_jamjet.py

End-to-end working example: a JamJet @durable workflow that uses Engram for memory. Two @tool-decorated functions wrap Engram operations (remember, answer_with_memory); the durable workflow composes them into a single conversation_turn. Demonstrates per-category routing — preference questions route to Reader(mode="synthesis") with role_filter=("user",).

The example is the proof-of-fit. Without it, "JamJet + Engram" is two separate libraries; with it, it's a stack.

Why now

PR #4 shipped v0.1.0 GA. PR #5 made the README OSS-friendly. But the README didn't yet make the connection to the broader JamJet ecosystem — meaning Engram could draw stars without converting any of that attention into JamJet adoption. This PR fixes that.

A complementary PR in jamjet-labs/jamjet updates that repo's "Sub-products" entry to point at jamjet-labs/engram (the new Python library) alongside the existing references to the Rust crate, MCP server, and Spring Boot starter.

Test plan

• README link to examples/06_with_jamjet.py resolves
• Example file lints clean (ruff check + format)
• Example file compiles (python -m py_compile)
• No CI scope changes

[coderabbitai]

Warning

Rate limit exceeded

@sunilp has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 51 minutes and 59 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 49a8875d-af5e-49d5-8ba3-164ce35004e4

📥 Commits

Reviewing files that changed from the base of the PR and between ccba890 and d3b63d6.

📒 Files selected for processing (2)

• README.md
• examples/06_with_jamjet.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/jamjet-cross-link

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}