Skip to content

Connect N MemNet servers (session pipe, not graph dump) #47

Description

@chouswei

Why

ai-investor now has two MemNet processes:

  1. Droplet — CompanyMemory / companySessionId (Role D SSOT, in-process with the desk).
  2. Pi (rpi5-syson) — OpenClaw’s local notepad for document digestion (session + pin_map so a later question does not re-read the whole PDF).

They must stay two handles. Do not mash OpenClaw’s digest session into companySessionId. Chat is never the handoff.

Problem

There is no product contract for how two MemNet servers talk.

Today the desk queue is HTTP claim/result. Gaps are supposed to ride opaque sessionId / companySessionId so a worker pin_maps. A Pi MemNet that actually holds the PDF atoms is a third place unless we define the pipe.

Wanted (model-first)

Define the connection as a session pipe, not a graph dump:

  • Handoff = session id (capability), peers re-pin_map.
  • Optional bounded import of a working-memory slice into the mission/company session (keep / reject / remint ids). Not Cypher MERGE of two live servers.
  • GQL-only mutate on the receiving session (id:'NEW', ACL who/what/bind).
  • Pi notepad may die with the digest run; droplet CompanyMemory is the durable-enough Role D SSOT (cabinet still external).

Out of scope

  • Vendoring AgensGraph/Neo4j into MemNet or onto the 2 GB droplet.
  • OpenClaw posting a graph dump in crew_prompt.
  • One global MemNet that both hosts share by accident.

Done when

  • SysML + a short wire note: who is sync owner, what id is sent, what pin_map shape the peer sees, what import is allowed.
  • No requirement that both servers share a DB.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions