Summary

This PR adds a new OpenViking memory configuration field: memory.agent_scope_mode.

It allows agent-level memory namespaces to be isolated in two ways:

• user+agent (default): isolate by (user_id, agent_id)
• agent: isolate only by agent_id, so users of the same agent share the same agent memory space

This change is implemented inside OpenViking, not only at the bot layer.

What Changed

• Added memory.agent_scope_mode to OpenViking memory config
• Updated UserIdentifier.agent_space_name() to derive agent space from config
• Kept existing behavior as default with user+agent
• Added tests for both isolation modes
• Updated docs affected by this change:
  • configuration guide
  • Viking URI concept
  • multi-tenant design doc

Behavior

Default behavior remains unchanged:

• memory.agent_scope_mode = "user+agent"
• agent space is derived from md5(f"{user_id}:{agent_id}")[:12]

New optional behavior:

• memory.agent_scope_mode = "agent"
• agent space is derived from md5(agent_id)[:12]

This affects agent-level namespaces such as:

• viking://agent/{agent_space}/memories/...
• viking://agent/{agent_space}/skills/...
• viking://agent/{agent_space}/instructions/...

It does not affect user memory namespaces under:

• viking://user/{user_space}/memories/...

Example

{
  "memory": {
    "agent_scope_mode": "agent"
  }
}

Testing

Validated with:

uv run --no-project --with pytest --with json-repair --with pydantic python -m pytest --noconftest -o addopts='' -q tests/cli/test_user_identifier.py

Also verified changed Python files with py_compile.

Notes

This PR only updates documentation directly impacted by this change.
It does not attempt to clean up unrelated pre-existing documentation gaps.