CONTEXT+

Build the mesh through node identities, typed relations and retained evidence. Record a proposal, its observed result or its rejection, then reopen the verified context for the next action.

Each node names one component; a typed relation explains its connection. Edit the example and export your JSON record. Public exploration runs locally; server discovery and retained owner records remain separate operations.

Mesh context

{
  "schema": "keddeh.context.mesh.v1",
  "nodes": [
    {
      "id": "kex:identity",
      "role": "KEX",
      "context": "Stable node identity and state addressing"
    },
    {
      "id": "braink:coordination",
      "role": "BRAINK",
      "context": "Capability dispatch and namespace coordination"
    },
    {
      "id": "illlm:relations",
      "role": "IL-LLM",
      "context": "Typed semantic relationships"
    },
    {
      "id": "vfs:retention",
      "role": "VFS",
      "context": "Retained source, context and verified checkpoints"
    }
  ],
  "relations": [
    {
      "from": "braink:coordination",
      "to": "kex:identity",
      "kind": "requires",
      "status": "proposed",
      "evidence": "Owner Web4 architecture: identity precedes coordinated action"
    },
    {
      "from": "illlm:relations",
      "to": "vfs:retention",
      "kind": "requires",
      "status": "proposed",
      "evidence": "Owner directive: mesh assimilation needs retained context"
    }
  ]
}

Import context JSON