EchoNodeSync

EchoNodeSync is an autonomous, bi-directional memory bridge for distributed agent ecosystems. It enables agents, humans, and rituals to store and retrieve memory keys directly—no external tushell dependency required. This package is designed for seamless integration with DreamWeaver, EchoThreads, and any narrative-driven, recursive agent system.

Features

• 📡 Autonomous Memory Bridge: Store and fetch memory keys using native JavaScript/Node.js—no CLI wrappers or external binaries.
• 🧠 Agent/Script Integration: Use as a library or CLI for agent-to-agent, human-to-agent, or ritual memory exchange.
• 🌸 VSCode Ritual Instructions: Ships with prompt instructions for agent/human sync, trinity embodiment, and DreamWeaver bridge protocols.
• 🔄 Fully NPM-Ready: Publishable, documented, and ready for distributed deployment.

Usage

As a Library

const { getMemory, postMemory } = require('echonodesync');

// Store a memory
await postMemory('Workspace.Guillaume.MyMemory.250503', 'This is my memory content');

// Retrieve a memory
const content = await getMemory('Workspace.Guillaume.MyMemory.250503');

As a CLI

npx echonodesync post-memory --key <key> --value <content>
npx echonodesync get-memory --key <key>

Direct Binaries

npx post-memory --key <key> --value <content>
npx get-memory --key <key>

Pluggable Backends

• Local file (default, in .mia/)
• HTTP API (set ECHONODESYNC_API_URL)
• Encrypted (set ECHONODESYNC_SECRET)

Security & Event Hooks

• Encrypted backend: set ECHONODESYNC_SECRET for AES-256 encryption
• Event hooks: coming soon (pre/post memory sync for agent rituals)

Testing

# Local file backend (default)
npx echonodesync post-memory --key test.hello --value "Hello, world!"
npx echonodesync get-memory --key test.hello

# HTTP backend
ECHONODESYNC_API_URL=http://localhost:8080/api/memory npx echonodesync post-memory --key test.remote --value "Remote!"

# Encrypted backend
ECHONODESYNC_SECRET=mysecret npx echonodesync post-memory --key test.secure --value "Secret!"
ECHONODESYNC_SECRET=mysecret npx echonodesync get-memory --key test.secure

Publishing

• Update package.json with your info
• Run npm publish from the package root

Onboarding & Rituals

• See /prompts for VSCode Copilot instructions and agent/human sync seeds
• See ROADMAP.md and MISSION_*.md for narrative and technical evolution

Every memory is a seed. Every prompt is a ritual. Every agent/human sync is a bloom in the garden.

🧠🌸 EchoNodeSync Memory File Resolution

• When retrieving a memory key, EchoNodeSync will search for files with both .Gpt.md and .md extensions (in that order) in the .mia/ directory, matching tushell CLI's flexible file resolution.
• This ensures compatibility with legacy and new memory files, and allows seamless migration from tushell-based rituals.
• Example: If you run npx echonodesync get-memory --key myKey, it will return the content of .mia/myKey.Gpt.md if it exists, otherwise .mia/myKey.md if that exists.