Feature: configurable cross-agent reflection inheritance (prevent main→other agent bleed)

[stanleeyY]

Problem

isOwnedByAgent() in src/reflection-store.ts hardcodes a fallback that allows all agents to inherit reflection slices from the main agent:

function isOwnedByAgent(metadata: Record<string, unknown>, agentId: string): boolean {
  const owner = typeof metadata.agentId === "string" ? metadata.agentId.trim() : "";
  if (!owner) return true;
  return owner === agentId || owner === "main";  // ← hardcoded
}

This means every agent (sysadmin, boss, designer, etc.) receives main agent's reflection invariants and derived lines, even when their workloads are completely unrelated.

Impact

• Derived lines (recent session deltas) from main bleed into specialized agents, injecting irrelevant context
• Invariants from main may or may not be relevant to other agents
• No way to opt out via config

Proposed Solution

Add a config option to control cross-agent reflection inheritance:

// In memoryReflection config
{
  "reflectionInheritFrom": ["main"],  // explicit list, or empty [] for full isolation
  // OR
  "reflectionIsolation": true  // simple toggle: only own reflections
}

Minimal alternative (lower effort)

Split the inheritance logic for invariants vs. derived:

• Invariants: keep main fallback (stable cross-session rules are usually generic)
• Derived: strict agent-only ownership (recent deltas are agent-specific)

This would prevent the most harmful bleed (irrelevant derived context) while preserving useful shared invariants.

Current Workaround

Manually patch isOwnedByAgent() to remove || owner === "main".

Environment

• memory-lancedb-pro 1.1.0-beta.10
• Multi-agent setup (6 agents with separate workspaces)
• injectMode: "inheritance+derived"

[AliceLJY]

Good catch — the hardcoded || owner === "main" fallback was a quick pragmatic choice for single-user setups, but it clearly doesn't scale to multi-agent deployments with isolated workloads.

On the two approaches:

The "minimal alternative" (split invariants vs. derived) is the right first step:

• Invariants from main are usually generic cross-session rules that are useful to other agents — keeping the fallback here is reasonable
• Derived lines are session-specific deltas that should be strict agent-owned — these are where the bleed hurts most

The full reflectionInheritFrom config is more powerful but adds configuration surface area. Suggest starting with the invariant/derived split as a default behavior improvement, and adding the config option only if users need more granular control.

If you'd like to contribute a PR:

1. Split the ownership logic in isOwnedByAgent() to check the reflection kind (invariant vs. derived)
2. Add a config flag (e.g. reflectionInheritance: "invariants-only" | "all" | "none", default "invariants-only")
3. Include a test covering multi-agent scenarios

This would be a clean, backward-compatible change.