TYPESCRIPT SDK
Own the agent loop.
Record executions, recall applicable memory, request bounded influence, and submit outcomes with typed contracts.
→Developer surface · local first
Give agents memory. Keep authority bounded.
Install the SDK, connect MCP, and let a fresh session reuse verified experience without replaying raw history or expanding its power.
QUICKSTART · ENGRAM AGENT SURFACELOCAL · VERIFIED
$ npm install engram-agent-surface // MCP client config { "command": "npx", "args": ["--yes", "engram-agent-surface@1.0.2"] } // one canonical lifecycle record → recall → influence → outcome
~/.sibyl-memory/engram-hackathon.dbCOPY CONFIG
01 · Choose your surface
One runtime. Three ways in.
SDK · MCP · REST / HTTP
MCP STDIO
Let agents call Engram.
Connect a tool-using agent to the same lifecycle through a local installable MCP command.
→REST / HTTP
Bring your own runtime.
Use the OpenAPI boundary from a worker, service, or language-independent application.
→02 · The integration loop
Teach the next session what mattered.
NO RAW HISTORY · NO NEW AUTHORITY
01 / RECORD
Complete execution
Capture what happened, the outcome, interpretation, and evidence.
02 / RECALL
Applicable memory
The agent actively requests a bounded MemorySlice.
03 / AUTHORIZE
InfluenceGrant
Engram names exactly what the memory may influence.
04 / UPDATE
Outcome evaluation
The result creates the next immutable memory version.
03 · Boundaries and proof
Start local. Verify every claim.
Agent usage guide
SKILL.md
Copy the usage guide for an agent: when to record, when to recall, how to cite a slice, and when to stop on refusal.
Deployment modes
Local MCP ≠ Hosted Worker
Local MCP uses local Sibyl persistence. Hosted REST uses the separately deployed Wrangler Worker and D1. Choose the mode intentionally.
04 · Submission checklist
Everything a judge needs to run it.
PUBLIC · REPLAYABLE · EXPLAINED
01 · Public repo
Clone the source.
Clean commits, complete setup instructions, runnable proofs, SDK, REST, MCP, and canonical evidence are available in the public repository.
OPEN REPOSITORY ↗02 · 2–5 minute demo
Replay the fresh session.
Start with the problem, follow the Engram lifecycle, and watch a fresh Session B request memory and change its provider decision.
WATCH REPLAY ↗03 · Team & partner stacks
Name what is real.
Builder: Jason / Jaydearcadian.
Partner stacks: no Base or Virtuals usage is claimed or independently verified in this submission.
04 · Memory implementation note
Explain the memory.
Engram persists completed executions through Sibyl, recalls an eligible MemorySlice, applies a bounded InfluenceGrant, and evaluates the outcome into an immutable update.
READ THE USAGE NOTE ↗