In matrix-context, the team decided to use SQLite as the default storage backend.


Note: In matrix-context, the team decided to use SQLite as the default storage backend.


General background notes about storage backend configuration and trade-offs.


Previously, project:matrix-context used a different approach for storage backend; this is now superseded.


A conflicting note claims project:matrix-context uses Postgres for storage backend.


In an old session we briefly mentioned storage backend, but nothing was decided.


In other-project, the team decided to use SQLite as the default storage backend.


matrix-context exposes both a Python SDK and an MCP server.


Note: matrix-context exposes both a Python SDK and an MCP server.


General background notes about MCP server configuration and trade-offs.


Previously, project:matrix-context used a different approach for MCP server; this is now superseded.


A conflicting note claims project:matrix-context uses a REST API only for MCP server.


In an old session we briefly mentioned MCP server, but nothing was decided.


other-project exposes both a Python SDK and an MCP server.


matrix-context decided to defer Milvus support to v2.


Note: matrix-context decided to defer Milvus support to v2.


General background notes about Milvus configuration and trade-offs.


Previously, project:matrix-context used a different approach for Milvus; this is now superseded.


A conflicting note claims project:matrix-context uses v1 for Milvus.


In an old session we briefly mentioned Milvus, but nothing was decided.


other-project decided to defer Milvus support to v2.


In agent-generator, the team decided to use SQLite as the default storage backend.


Note: In agent-generator, the team decided to use SQLite as the default storage backend.


General background notes about storage backend configuration and trade-offs.


Previously, project:agent-generator used a different approach for storage backend; this is now superseded.


A conflicting note claims project:agent-generator uses Postgres for storage backend.


In an old session we briefly mentioned storage backend, but nothing was decided.


In other-project, the team decided to use SQLite as the default storage backend.


agent-generator exposes both a Python SDK and an MCP server.


Note: agent-generator exposes both a Python SDK and an MCP server.


General background notes about MCP server configuration and trade-offs.


Previously, project:agent-generator used a different approach for MCP server; this is now superseded.


A conflicting note claims project:agent-generator uses a REST API only for MCP server.


In an old session we briefly mentioned MCP server, but nothing was decided.


other-project exposes both a Python SDK and an MCP server.


agent-generator decided to defer Milvus support to v2.


Note: agent-generator decided to defer Milvus support to v2.


General background notes about Milvus configuration and trade-offs.


Previously, project:agent-generator used a different approach for Milvus; this is now superseded.


A conflicting note claims project:agent-generator uses v1 for Milvus.


In an old session we briefly mentioned Milvus, but nothing was decided.


other-project decided to defer Milvus support to v2.


In homepilot, the team decided to use SQLite as the default storage backend.


Note: In homepilot, the team decided to use SQLite as the default storage backend.


General background notes about storage backend configuration and trade-offs.


Previously, project:homepilot used a different approach for storage backend; this is now superseded.


A conflicting note claims project:homepilot uses Postgres for storage backend.


In an old session we briefly mentioned storage backend, but nothing was decided.


In other-project, the team decided to use SQLite as the default storage backend.


homepilot exposes both a Python SDK and an MCP server.


Note: homepilot exposes both a Python SDK and an MCP server.


General background notes about MCP server configuration and trade-offs.


Previously, project:homepilot used a different approach for MCP server; this is now superseded.


A conflicting note claims project:homepilot uses a REST API only for MCP server.


In an old session we briefly mentioned MCP server, but nothing was decided.


other-project exposes both a Python SDK and an MCP server.


homepilot decided to defer Milvus support to v2.


Note: homepilot decided to defer Milvus support to v2.


General background notes about Milvus configuration and trade-offs.


Previously, project:homepilot used a different approach for Milvus; this is now superseded.


A conflicting note claims project:homepilot uses v1 for Milvus.


In an old session we briefly mentioned Milvus, but nothing was decided.


other-project decided to defer Milvus support to v2.


In gitpilot, the team decided to use SQLite as the default storage backend.


Note: In gitpilot, the team decided to use SQLite as the default storage backend.


General background notes about storage backend configuration and trade-offs.


Previously, project:gitpilot used a different approach for storage backend; this is now superseded.


A conflicting note claims project:gitpilot uses Postgres for storage backend.


In an old session we briefly mentioned storage backend, but nothing was decided.


In other-project, the team decided to use SQLite as the default storage backend.


gitpilot exposes both a Python SDK and an MCP server.


Note: gitpilot exposes both a Python SDK and an MCP server.


General background notes about MCP server configuration and trade-offs.


Previously, project:gitpilot used a different approach for MCP server; this is now superseded.


A conflicting note claims project:gitpilot uses a REST API only for MCP server.


In an old session we briefly mentioned MCP server, but nothing was decided.


other-project exposes both a Python SDK and an MCP server.


gitpilot decided to defer Milvus support to v2.


Note: gitpilot decided to defer Milvus support to v2.


General background notes about Milvus configuration and trade-offs.


Previously, project:gitpilot used a different approach for Milvus; this is now superseded.


A conflicting note claims project:gitpilot uses v1 for Milvus.


In an old session we briefly mentioned Milvus, but nothing was decided.


other-project decided to defer Milvus support to v2.


In ruslanmv-web, the team decided to use SQLite as the default storage backend.


Note: In ruslanmv-web, the team decided to use SQLite as the default storage backend.


General background notes about storage backend configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for storage backend; this is now superseded.


A conflicting note claims project:ruslanmv-web uses Postgres for storage backend.


In an old session we briefly mentioned storage backend, but nothing was decided.


In other-project, the team decided to use SQLite as the default storage backend.


ruslanmv-web exposes both a Python SDK and an MCP server.


Note: ruslanmv-web exposes both a Python SDK and an MCP server.


General background notes about MCP server configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for MCP server; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a REST API only for MCP server.


In an old session we briefly mentioned MCP server, but nothing was decided.


other-project exposes both a Python SDK and an MCP server.


ruslanmv-web decided to defer Milvus support to v2.


Note: ruslanmv-web decided to defer Milvus support to v2.


General background notes about Milvus configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for Milvus; this is now superseded.


A conflicting note claims project:ruslanmv-web uses v1 for Milvus.


In an old session we briefly mentioned Milvus, but nothing was decided.


other-project decided to defer Milvus support to v2.


The secretary persona prefers local-first tools over cloud services.


Note: The secretary persona prefers local-first tools over cloud services.


General background notes about local-first configuration and trade-offs.


Previously, persona:secretary used a different approach for local-first; this is now superseded.


A conflicting note claims persona:secretary uses cloud-first for local-first.


In an old session we briefly mentioned local-first, but nothing was decided.


The other-persona persona prefers local-first tools over cloud services.


The secretary persona uses a warm, professional tone.


Note: The secretary persona uses a warm, professional tone.


General background notes about tone configuration and trade-offs.


Previously, persona:secretary used a different approach for tone; this is now superseded.


A conflicting note claims persona:secretary uses terse and blunt for tone.


In an old session we briefly mentioned tone, but nothing was decided.


The other-persona persona uses a warm, professional tone.


The analyst persona prefers local-first tools over cloud services.


Note: The analyst persona prefers local-first tools over cloud services.


Previously, persona:analyst used a different approach for local-first; this is now superseded.


A conflicting note claims persona:analyst uses cloud-first for local-first.


The analyst persona uses a warm, professional tone.


Note: The analyst persona uses a warm, professional tone.


Previously, persona:analyst used a different approach for tone; this is now superseded.


A conflicting note claims persona:analyst uses terse and blunt for tone.


The coach persona prefers local-first tools over cloud services.


Note: The coach persona prefers local-first tools over cloud services.


General background notes about local-first configuration and trade-offs.


Previously, persona:coach used a different approach for local-first; this is now superseded.


A conflicting note claims persona:coach uses cloud-first for local-first.


In an old session we briefly mentioned local-first, but nothing was decided.


The other-persona persona prefers local-first tools over cloud services.


The coach persona uses a warm, professional tone.


Note: The coach persona uses a warm, professional tone.


General background notes about tone configuration and trade-offs.


Previously, persona:coach used a different approach for tone; this is now superseded.


A conflicting note claims persona:coach uses terse and blunt for tone.


In an old session we briefly mentioned tone, but nothing was decided.


The other-persona persona uses a warm, professional tone.


The tutor persona prefers local-first tools over cloud services.


Note: The tutor persona prefers local-first tools over cloud services.


Previously, persona:tutor used a different approach for local-first; this is now superseded.


A conflicting note claims persona:tutor uses cloud-first for local-first.


The tutor persona uses a warm, professional tone.


Note: The tutor persona uses a warm, professional tone.


Previously, persona:tutor used a different approach for tone; this is now superseded.


A conflicting note claims persona:tutor uses terse and blunt for tone.


The concierge persona prefers local-first tools over cloud services.


Note: The concierge persona prefers local-first tools over cloud services.


General background notes about local-first configuration and trade-offs.


Previously, persona:concierge used a different approach for local-first; this is now superseded.


A conflicting note claims persona:concierge uses cloud-first for local-first.


In an old session we briefly mentioned local-first, but nothing was decided.


The other-persona persona prefers local-first tools over cloud services.


The concierge persona uses a warm, professional tone.


Note: The concierge persona uses a warm, professional tone.


General background notes about tone configuration and trade-offs.


Previously, persona:concierge used a different approach for tone; this is now superseded.


A conflicting note claims persona:concierge uses terse and blunt for tone.


In an old session we briefly mentioned tone, but nothing was decided.


The other-persona persona uses a warm, professional tone.


In matrix-context, the router is implemented in src/matrix_context/router.py.


Note: In matrix-context, the router is implemented in src/matrix_context/router.py.


General background notes about router configuration and trade-offs.


Previously, project:matrix-context used a different approach for router; this is now superseded.


A conflicting note claims project:matrix-context uses a notebook for router.


In an old session we briefly mentioned router, but nothing was decided.


In other-project, the router is implemented in src/matrix_context/router.py.


In matrix-context, the assembler is implemented in src/matrix_context/assembler.py.


Note: In matrix-context, the assembler is implemented in src/matrix_context/assembler.py.


General background notes about assembler configuration and trade-offs.


Previously, project:matrix-context used a different approach for assembler; this is now superseded.


A conflicting note claims project:matrix-context uses a notebook for assembler.


In an old session we briefly mentioned assembler, but nothing was decided.


In other-project, the assembler is implemented in src/matrix_context/assembler.py.


In matrix-context, the store is implemented in src/matrix_context/store.py.


Note: In matrix-context, the store is implemented in src/matrix_context/store.py.


General background notes about store configuration and trade-offs.


Previously, project:matrix-context used a different approach for store; this is now superseded.


A conflicting note claims project:matrix-context uses a notebook for store.


In an old session we briefly mentioned store, but nothing was decided.


In other-project, the store is implemented in src/matrix_context/store.py.


In matrix-context, the retrieval is implemented in src/matrix_context/retrieval.py.


Note: In matrix-context, the retrieval is implemented in src/matrix_context/retrieval.py.


General background notes about retrieval configuration and trade-offs.


Previously, project:matrix-context used a different approach for retrieval; this is now superseded.


A conflicting note claims project:matrix-context uses a notebook for retrieval.


In an old session we briefly mentioned retrieval, but nothing was decided.


In other-project, the retrieval is implemented in src/matrix_context/retrieval.py.


In matrix-context, the embedder is implemented in src/matrix_context/embedder.py.


Note: In matrix-context, the embedder is implemented in src/matrix_context/embedder.py.


General background notes about embedder configuration and trade-offs.


Previously, project:matrix-context used a different approach for embedder; this is now superseded.


A conflicting note claims project:matrix-context uses a notebook for embedder.


In an old session we briefly mentioned embedder, but nothing was decided.


In other-project, the embedder is implemented in src/matrix_context/embedder.py.


In matrix-context, the cli is implemented in src/matrix_context/cli.py.


Note: In matrix-context, the cli is implemented in src/matrix_context/cli.py.


General background notes about cli configuration and trade-offs.


Previously, project:matrix-context used a different approach for cli; this is now superseded.


A conflicting note claims project:matrix-context uses a notebook for cli.


In an old session we briefly mentioned cli, but nothing was decided.


In other-project, the cli is implemented in src/matrix_context/cli.py.


In agent-generator, the router is implemented in src/agent_generator/router.py.


Note: In agent-generator, the router is implemented in src/agent_generator/router.py.


General background notes about router configuration and trade-offs.


Previously, project:agent-generator used a different approach for router; this is now superseded.


A conflicting note claims project:agent-generator uses a notebook for router.


In an old session we briefly mentioned router, but nothing was decided.


In other-project, the router is implemented in src/agent_generator/router.py.


In agent-generator, the assembler is implemented in src/agent_generator/assembler.py.


Note: In agent-generator, the assembler is implemented in src/agent_generator/assembler.py.


General background notes about assembler configuration and trade-offs.


Previously, project:agent-generator used a different approach for assembler; this is now superseded.


A conflicting note claims project:agent-generator uses a notebook for assembler.


In an old session we briefly mentioned assembler, but nothing was decided.


In other-project, the assembler is implemented in src/agent_generator/assembler.py.


In agent-generator, the store is implemented in src/agent_generator/store.py.


Note: In agent-generator, the store is implemented in src/agent_generator/store.py.


General background notes about store configuration and trade-offs.


Previously, project:agent-generator used a different approach for store; this is now superseded.


A conflicting note claims project:agent-generator uses a notebook for store.


In an old session we briefly mentioned store, but nothing was decided.


In other-project, the store is implemented in src/agent_generator/store.py.


In agent-generator, the retrieval is implemented in src/agent_generator/retrieval.py.


Note: In agent-generator, the retrieval is implemented in src/agent_generator/retrieval.py.


General background notes about retrieval configuration and trade-offs.


Previously, project:agent-generator used a different approach for retrieval; this is now superseded.


A conflicting note claims project:agent-generator uses a notebook for retrieval.


In an old session we briefly mentioned retrieval, but nothing was decided.


In other-project, the retrieval is implemented in src/agent_generator/retrieval.py.


In agent-generator, the embedder is implemented in src/agent_generator/embedder.py.


Note: In agent-generator, the embedder is implemented in src/agent_generator/embedder.py.


General background notes about embedder configuration and trade-offs.


Previously, project:agent-generator used a different approach for embedder; this is now superseded.


A conflicting note claims project:agent-generator uses a notebook for embedder.


In an old session we briefly mentioned embedder, but nothing was decided.


In other-project, the embedder is implemented in src/agent_generator/embedder.py.


In agent-generator, the cli is implemented in src/agent_generator/cli.py.


Note: In agent-generator, the cli is implemented in src/agent_generator/cli.py.


General background notes about cli configuration and trade-offs.


Previously, project:agent-generator used a different approach for cli; this is now superseded.


A conflicting note claims project:agent-generator uses a notebook for cli.


In an old session we briefly mentioned cli, but nothing was decided.


In other-project, the cli is implemented in src/agent_generator/cli.py.


In homepilot, the router is implemented in src/homepilot/router.py.


Note: In homepilot, the router is implemented in src/homepilot/router.py.


General background notes about router configuration and trade-offs.


Previously, project:homepilot used a different approach for router; this is now superseded.


A conflicting note claims project:homepilot uses a notebook for router.


In an old session we briefly mentioned router, but nothing was decided.


In other-project, the router is implemented in src/other-project/router.py.


In homepilot, the assembler is implemented in src/homepilot/assembler.py.


Note: In homepilot, the assembler is implemented in src/homepilot/assembler.py.


General background notes about assembler configuration and trade-offs.


Previously, project:homepilot used a different approach for assembler; this is now superseded.


A conflicting note claims project:homepilot uses a notebook for assembler.


In an old session we briefly mentioned assembler, but nothing was decided.


In other-project, the assembler is implemented in src/other-project/assembler.py.


In homepilot, the store is implemented in src/homepilot/store.py.


Note: In homepilot, the store is implemented in src/homepilot/store.py.


General background notes about store configuration and trade-offs.


Previously, project:homepilot used a different approach for store; this is now superseded.


A conflicting note claims project:homepilot uses a notebook for store.


In an old session we briefly mentioned store, but nothing was decided.


In other-project, the store is implemented in src/other-project/store.py.


In homepilot, the retrieval is implemented in src/homepilot/retrieval.py.


Note: In homepilot, the retrieval is implemented in src/homepilot/retrieval.py.


General background notes about retrieval configuration and trade-offs.


Previously, project:homepilot used a different approach for retrieval; this is now superseded.


A conflicting note claims project:homepilot uses a notebook for retrieval.


In an old session we briefly mentioned retrieval, but nothing was decided.


In other-project, the retrieval is implemented in src/other-project/retrieval.py.


In homepilot, the embedder is implemented in src/homepilot/embedder.py.


Note: In homepilot, the embedder is implemented in src/homepilot/embedder.py.


General background notes about embedder configuration and trade-offs.


Previously, project:homepilot used a different approach for embedder; this is now superseded.


A conflicting note claims project:homepilot uses a notebook for embedder.


In an old session we briefly mentioned embedder, but nothing was decided.


In other-project, the embedder is implemented in src/other-project/embedder.py.


In homepilot, the cli is implemented in src/homepilot/cli.py.


Note: In homepilot, the cli is implemented in src/homepilot/cli.py.


General background notes about cli configuration and trade-offs.


Previously, project:homepilot used a different approach for cli; this is now superseded.


A conflicting note claims project:homepilot uses a notebook for cli.


In an old session we briefly mentioned cli, but nothing was decided.


In other-project, the cli is implemented in src/other-project/cli.py.


In gitpilot, the router is implemented in src/gitpilot/router.py.


Note: In gitpilot, the router is implemented in src/gitpilot/router.py.


General background notes about router configuration and trade-offs.


Previously, project:gitpilot used a different approach for router; this is now superseded.


A conflicting note claims project:gitpilot uses a notebook for router.


In an old session we briefly mentioned router, but nothing was decided.


In other-project, the router is implemented in src/other-project/router.py.


In gitpilot, the assembler is implemented in src/gitpilot/assembler.py.


Note: In gitpilot, the assembler is implemented in src/gitpilot/assembler.py.


General background notes about assembler configuration and trade-offs.


Previously, project:gitpilot used a different approach for assembler; this is now superseded.


A conflicting note claims project:gitpilot uses a notebook for assembler.


In an old session we briefly mentioned assembler, but nothing was decided.


In other-project, the assembler is implemented in src/other-project/assembler.py.


In gitpilot, the store is implemented in src/gitpilot/store.py.


Note: In gitpilot, the store is implemented in src/gitpilot/store.py.


General background notes about store configuration and trade-offs.


Previously, project:gitpilot used a different approach for store; this is now superseded.


A conflicting note claims project:gitpilot uses a notebook for store.


In an old session we briefly mentioned store, but nothing was decided.


In other-project, the store is implemented in src/other-project/store.py.


In gitpilot, the retrieval is implemented in src/gitpilot/retrieval.py.


Note: In gitpilot, the retrieval is implemented in src/gitpilot/retrieval.py.


General background notes about retrieval configuration and trade-offs.


Previously, project:gitpilot used a different approach for retrieval; this is now superseded.


A conflicting note claims project:gitpilot uses a notebook for retrieval.


In an old session we briefly mentioned retrieval, but nothing was decided.


In other-project, the retrieval is implemented in src/other-project/retrieval.py.


In gitpilot, the embedder is implemented in src/gitpilot/embedder.py.


Note: In gitpilot, the embedder is implemented in src/gitpilot/embedder.py.


General background notes about embedder configuration and trade-offs.


Previously, project:gitpilot used a different approach for embedder; this is now superseded.


A conflicting note claims project:gitpilot uses a notebook for embedder.


In an old session we briefly mentioned embedder, but nothing was decided.


In other-project, the embedder is implemented in src/other-project/embedder.py.


In gitpilot, the cli is implemented in src/gitpilot/cli.py.


Note: In gitpilot, the cli is implemented in src/gitpilot/cli.py.


General background notes about cli configuration and trade-offs.


Previously, project:gitpilot used a different approach for cli; this is now superseded.


A conflicting note claims project:gitpilot uses a notebook for cli.


In an old session we briefly mentioned cli, but nothing was decided.


In other-project, the cli is implemented in src/other-project/cli.py.


In ruslanmv-web, the router is implemented in src/ruslanmv_web/router.py.


Note: In ruslanmv-web, the router is implemented in src/ruslanmv_web/router.py.


General background notes about router configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for router; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a notebook for router.


In an old session we briefly mentioned router, but nothing was decided.


In other-project, the router is implemented in src/ruslanmv_web/router.py.


In ruslanmv-web, the assembler is implemented in src/ruslanmv_web/assembler.py.


Note: In ruslanmv-web, the assembler is implemented in src/ruslanmv_web/assembler.py.


General background notes about assembler configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for assembler; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a notebook for assembler.


In an old session we briefly mentioned assembler, but nothing was decided.


In other-project, the assembler is implemented in src/ruslanmv_web/assembler.py.


In ruslanmv-web, the store is implemented in src/ruslanmv_web/store.py.


Note: In ruslanmv-web, the store is implemented in src/ruslanmv_web/store.py.


General background notes about store configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for store; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a notebook for store.


In an old session we briefly mentioned store, but nothing was decided.


In other-project, the store is implemented in src/ruslanmv_web/store.py.


In ruslanmv-web, the retrieval is implemented in src/ruslanmv_web/retrieval.py.


Note: In ruslanmv-web, the retrieval is implemented in src/ruslanmv_web/retrieval.py.


General background notes about retrieval configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for retrieval; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a notebook for retrieval.


In an old session we briefly mentioned retrieval, but nothing was decided.


In other-project, the retrieval is implemented in src/ruslanmv_web/retrieval.py.


In ruslanmv-web, the embedder is implemented in src/ruslanmv_web/embedder.py.


Note: In ruslanmv-web, the embedder is implemented in src/ruslanmv_web/embedder.py.


General background notes about embedder configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for embedder; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a notebook for embedder.


In an old session we briefly mentioned embedder, but nothing was decided.


In other-project, the embedder is implemented in src/ruslanmv_web/embedder.py.


In ruslanmv-web, the cli is implemented in src/ruslanmv_web/cli.py.


Note: In ruslanmv-web, the cli is implemented in src/ruslanmv_web/cli.py.


General background notes about cli configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for cli; this is now superseded.


A conflicting note claims project:ruslanmv-web uses a notebook for cli.


In an old session we briefly mentioned cli, but nothing was decided.


In other-project, the cli is implemented in src/ruslanmv_web/cli.py.


Policy in matrix-context: the agent must never store API keys in durable memory.


Note: Policy in matrix-context: the agent must never store API keys in durable memory.


General background notes about API keys configuration and trade-offs.


Previously, project:matrix-context used a different approach for API keys; this is now superseded.


A conflicting note claims project:matrix-context uses store API keys freely for API keys.


In an old session we briefly mentioned API keys, but nothing was decided.


Policy in other-project: the agent must never store API keys in durable memory.


Policy in matrix-context: the agent must never store PII in durable memory.


Note: Policy in matrix-context: the agent must never store PII in durable memory.


General background notes about PII configuration and trade-offs.


Previously, project:matrix-context used a different approach for PII; this is now superseded.


A conflicting note claims project:matrix-context uses store PII freely for PII.


In an old session we briefly mentioned PII, but nothing was decided.


Policy in other-project: the agent must never store PII in durable memory.


Policy in matrix-context: the agent must never store secrets in durable memory.


Note: Policy in matrix-context: the agent must never store secrets in durable memory.


General background notes about secrets configuration and trade-offs.


Previously, project:matrix-context used a different approach for secrets; this is now superseded.


A conflicting note claims project:matrix-context uses store secrets freely for secrets.


In an old session we briefly mentioned secrets, but nothing was decided.


Policy in other-project: the agent must never store secrets in durable memory.


Policy in matrix-context: the agent must never store audit logs in durable memory.


Note: Policy in matrix-context: the agent must never store audit logs in durable memory.


General background notes about audit logs configuration and trade-offs.


Previously, project:matrix-context used a different approach for audit logs; this is now superseded.


A conflicting note claims project:matrix-context uses store audit logs freely for audit logs.


In an old session we briefly mentioned audit logs, but nothing was decided.


Policy in other-project: the agent must never store audit logs in durable memory.


Policy in agent-generator: the agent must never store API keys in durable memory.


Note: Policy in agent-generator: the agent must never store API keys in durable memory.


General background notes about API keys configuration and trade-offs.


Previously, project:agent-generator used a different approach for API keys; this is now superseded.


A conflicting note claims project:agent-generator uses store API keys freely for API keys.


In an old session we briefly mentioned API keys, but nothing was decided.


Policy in other-project: the agent must never store API keys in durable memory.


Policy in agent-generator: the agent must never store PII in durable memory.


Note: Policy in agent-generator: the agent must never store PII in durable memory.


General background notes about PII configuration and trade-offs.


Previously, project:agent-generator used a different approach for PII; this is now superseded.


A conflicting note claims project:agent-generator uses store PII freely for PII.


In an old session we briefly mentioned PII, but nothing was decided.


Policy in other-project: the agent must never store PII in durable memory.


Policy in agent-generator: the agent must never store secrets in durable memory.


Note: Policy in agent-generator: the agent must never store secrets in durable memory.


General background notes about secrets configuration and trade-offs.


Previously, project:agent-generator used a different approach for secrets; this is now superseded.


A conflicting note claims project:agent-generator uses store secrets freely for secrets.


In an old session we briefly mentioned secrets, but nothing was decided.


Policy in other-project: the agent must never store secrets in durable memory.


Policy in agent-generator: the agent must never store audit logs in durable memory.


Note: Policy in agent-generator: the agent must never store audit logs in durable memory.


General background notes about audit logs configuration and trade-offs.


Previously, project:agent-generator used a different approach for audit logs; this is now superseded.


A conflicting note claims project:agent-generator uses store audit logs freely for audit logs.


In an old session we briefly mentioned audit logs, but nothing was decided.


Policy in other-project: the agent must never store audit logs in durable memory.


Policy in homepilot: the agent must never store API keys in durable memory.


Note: Policy in homepilot: the agent must never store API keys in durable memory.


General background notes about API keys configuration and trade-offs.


Previously, project:homepilot used a different approach for API keys; this is now superseded.


A conflicting note claims project:homepilot uses store API keys freely for API keys.


In an old session we briefly mentioned API keys, but nothing was decided.


Policy in other-project: the agent must never store API keys in durable memory.


Policy in homepilot: the agent must never store PII in durable memory.


Note: Policy in homepilot: the agent must never store PII in durable memory.


General background notes about PII configuration and trade-offs.


Previously, project:homepilot used a different approach for PII; this is now superseded.


A conflicting note claims project:homepilot uses store PII freely for PII.


In an old session we briefly mentioned PII, but nothing was decided.


Policy in other-project: the agent must never store PII in durable memory.


Policy in homepilot: the agent must never store secrets in durable memory.


Note: Policy in homepilot: the agent must never store secrets in durable memory.


General background notes about secrets configuration and trade-offs.


Previously, project:homepilot used a different approach for secrets; this is now superseded.


A conflicting note claims project:homepilot uses store secrets freely for secrets.


In an old session we briefly mentioned secrets, but nothing was decided.


Policy in other-project: the agent must never store secrets in durable memory.


Policy in homepilot: the agent must never store audit logs in durable memory.


Note: Policy in homepilot: the agent must never store audit logs in durable memory.


General background notes about audit logs configuration and trade-offs.


Previously, project:homepilot used a different approach for audit logs; this is now superseded.


A conflicting note claims project:homepilot uses store audit logs freely for audit logs.


In an old session we briefly mentioned audit logs, but nothing was decided.


Policy in other-project: the agent must never store audit logs in durable memory.


Policy in gitpilot: the agent must never store API keys in durable memory.


Note: Policy in gitpilot: the agent must never store API keys in durable memory.


General background notes about API keys configuration and trade-offs.


Previously, project:gitpilot used a different approach for API keys; this is now superseded.


A conflicting note claims project:gitpilot uses store API keys freely for API keys.


In an old session we briefly mentioned API keys, but nothing was decided.


Policy in other-project: the agent must never store API keys in durable memory.


Policy in gitpilot: the agent must never store PII in durable memory.


Note: Policy in gitpilot: the agent must never store PII in durable memory.


General background notes about PII configuration and trade-offs.


Previously, project:gitpilot used a different approach for PII; this is now superseded.


A conflicting note claims project:gitpilot uses store PII freely for PII.


In an old session we briefly mentioned PII, but nothing was decided.


Policy in other-project: the agent must never store PII in durable memory.


Policy in gitpilot: the agent must never store secrets in durable memory.


Note: Policy in gitpilot: the agent must never store secrets in durable memory.


General background notes about secrets configuration and trade-offs.


Previously, project:gitpilot used a different approach for secrets; this is now superseded.


A conflicting note claims project:gitpilot uses store secrets freely for secrets.


In an old session we briefly mentioned secrets, but nothing was decided.


Policy in other-project: the agent must never store secrets in durable memory.


Policy in gitpilot: the agent must never store audit logs in durable memory.


Note: Policy in gitpilot: the agent must never store audit logs in durable memory.


General background notes about audit logs configuration and trade-offs.


Previously, project:gitpilot used a different approach for audit logs; this is now superseded.


A conflicting note claims project:gitpilot uses store audit logs freely for audit logs.


In an old session we briefly mentioned audit logs, but nothing was decided.


Policy in other-project: the agent must never store audit logs in durable memory.


Policy in ruslanmv-web: the agent must never store API keys in durable memory.


Note: Policy in ruslanmv-web: the agent must never store API keys in durable memory.


General background notes about API keys configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for API keys; this is now superseded.


A conflicting note claims project:ruslanmv-web uses store API keys freely for API keys.


In an old session we briefly mentioned API keys, but nothing was decided.


Policy in other-project: the agent must never store API keys in durable memory.


Policy in ruslanmv-web: the agent must never store PII in durable memory.


Note: Policy in ruslanmv-web: the agent must never store PII in durable memory.


General background notes about PII configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for PII; this is now superseded.


A conflicting note claims project:ruslanmv-web uses store PII freely for PII.


In an old session we briefly mentioned PII, but nothing was decided.


Policy in other-project: the agent must never store PII in durable memory.


Policy in ruslanmv-web: the agent must never store secrets in durable memory.


Note: Policy in ruslanmv-web: the agent must never store secrets in durable memory.


General background notes about secrets configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for secrets; this is now superseded.


A conflicting note claims project:ruslanmv-web uses store secrets freely for secrets.


In an old session we briefly mentioned secrets, but nothing was decided.


Policy in other-project: the agent must never store secrets in durable memory.


Policy in ruslanmv-web: the agent must never store audit logs in durable memory.


Note: Policy in ruslanmv-web: the agent must never store audit logs in durable memory.


General background notes about audit logs configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for audit logs; this is now superseded.


A conflicting note claims project:ruslanmv-web uses store audit logs freely for audit logs.


In an old session we briefly mentioned audit logs, but nothing was decided.


Policy in other-project: the agent must never store audit logs in durable memory.


The last eval.harness run on matrix-context produced a passing result.


Note: The last eval.harness run on matrix-context produced a passing result.


General background notes about eval.harness configuration and trade-offs.


Previously, project:matrix-context used a different approach for eval.harness; this is now superseded.


A conflicting note claims project:matrix-context uses failing for eval.harness.


In an old session we briefly mentioned eval.harness, but nothing was decided.


The last eval.harness run on other-project produced a passing result.


The last experiments.runner run on matrix-context produced a passing result.


Note: The last experiments.runner run on matrix-context produced a passing result.


General background notes about experiments.runner configuration and trade-offs.


Previously, project:matrix-context used a different approach for experiments.runner; this is now superseded.


A conflicting note claims project:matrix-context uses failing for experiments.runner.


In an old session we briefly mentioned experiments.runner, but nothing was decided.


The last experiments.runner run on other-project produced a passing result.


The last pytest run on matrix-context produced a passing result.


Note: The last pytest run on matrix-context produced a passing result.


General background notes about pytest configuration and trade-offs.


Previously, project:matrix-context used a different approach for pytest; this is now superseded.


A conflicting note claims project:matrix-context uses failing for pytest.


In an old session we briefly mentioned pytest, but nothing was decided.


The last pytest run on other-project produced a passing result.


In the last session about matrix-context, we agreed to ship the REST API first.


Note: In the last session about matrix-context, we agreed to ship the REST API first.


General background notes about REST API configuration and trade-offs.


Previously, project:matrix-context used a different approach for REST API; this is now superseded.


A conflicting note claims project:matrix-context uses the UI first for REST API.


In an old session we briefly mentioned REST API, but nothing was decided.


In the last session about other-project, we agreed to ship the REST API first.


The last eval.harness run on agent-generator produced a passing result.


Note: The last eval.harness run on agent-generator produced a passing result.


General background notes about eval.harness configuration and trade-offs.


Previously, project:agent-generator used a different approach for eval.harness; this is now superseded.


A conflicting note claims project:agent-generator uses failing for eval.harness.


In an old session we briefly mentioned eval.harness, but nothing was decided.


The last eval.harness run on other-project produced a passing result.


The last experiments.runner run on agent-generator produced a passing result.


Note: The last experiments.runner run on agent-generator produced a passing result.


General background notes about experiments.runner configuration and trade-offs.


Previously, project:agent-generator used a different approach for experiments.runner; this is now superseded.


A conflicting note claims project:agent-generator uses failing for experiments.runner.


In an old session we briefly mentioned experiments.runner, but nothing was decided.


The last experiments.runner run on other-project produced a passing result.


The last pytest run on agent-generator produced a passing result.


Note: The last pytest run on agent-generator produced a passing result.


General background notes about pytest configuration and trade-offs.


Previously, project:agent-generator used a different approach for pytest; this is now superseded.


A conflicting note claims project:agent-generator uses failing for pytest.


In an old session we briefly mentioned pytest, but nothing was decided.


The last pytest run on other-project produced a passing result.


In the last session about agent-generator, we agreed to ship the REST API first.


Note: In the last session about agent-generator, we agreed to ship the REST API first.


General background notes about REST API configuration and trade-offs.


Previously, project:agent-generator used a different approach for REST API; this is now superseded.


A conflicting note claims project:agent-generator uses the UI first for REST API.


In an old session we briefly mentioned REST API, but nothing was decided.


In the last session about other-project, we agreed to ship the REST API first.


The last eval.harness run on homepilot produced a passing result.


Note: The last eval.harness run on homepilot produced a passing result.


General background notes about eval.harness configuration and trade-offs.


Previously, project:homepilot used a different approach for eval.harness; this is now superseded.


A conflicting note claims project:homepilot uses failing for eval.harness.


In an old session we briefly mentioned eval.harness, but nothing was decided.


The last eval.harness run on other-project produced a passing result.


The last experiments.runner run on homepilot produced a passing result.


Note: The last experiments.runner run on homepilot produced a passing result.


General background notes about experiments.runner configuration and trade-offs.


Previously, project:homepilot used a different approach for experiments.runner; this is now superseded.


A conflicting note claims project:homepilot uses failing for experiments.runner.


In an old session we briefly mentioned experiments.runner, but nothing was decided.


The last experiments.runner run on other-project produced a passing result.


The last pytest run on homepilot produced a passing result.


Note: The last pytest run on homepilot produced a passing result.


General background notes about pytest configuration and trade-offs.


Previously, project:homepilot used a different approach for pytest; this is now superseded.


A conflicting note claims project:homepilot uses failing for pytest.


In an old session we briefly mentioned pytest, but nothing was decided.


The last pytest run on other-project produced a passing result.


In the last session about homepilot, we agreed to ship the REST API first.


Note: In the last session about homepilot, we agreed to ship the REST API first.


General background notes about REST API configuration and trade-offs.


Previously, project:homepilot used a different approach for REST API; this is now superseded.


A conflicting note claims project:homepilot uses the UI first for REST API.


In an old session we briefly mentioned REST API, but nothing was decided.


In the last session about other-project, we agreed to ship the REST API first.


The last eval.harness run on gitpilot produced a passing result.


Note: The last eval.harness run on gitpilot produced a passing result.


General background notes about eval.harness configuration and trade-offs.


Previously, project:gitpilot used a different approach for eval.harness; this is now superseded.


A conflicting note claims project:gitpilot uses failing for eval.harness.


In an old session we briefly mentioned eval.harness, but nothing was decided.


The last eval.harness run on other-project produced a passing result.


The last experiments.runner run on gitpilot produced a passing result.


Note: The last experiments.runner run on gitpilot produced a passing result.


General background notes about experiments.runner configuration and trade-offs.


Previously, project:gitpilot used a different approach for experiments.runner; this is now superseded.


A conflicting note claims project:gitpilot uses failing for experiments.runner.


In an old session we briefly mentioned experiments.runner, but nothing was decided.


The last experiments.runner run on other-project produced a passing result.


The last pytest run on gitpilot produced a passing result.


Note: The last pytest run on gitpilot produced a passing result.


General background notes about pytest configuration and trade-offs.


Previously, project:gitpilot used a different approach for pytest; this is now superseded.


A conflicting note claims project:gitpilot uses failing for pytest.


In an old session we briefly mentioned pytest, but nothing was decided.


The last pytest run on other-project produced a passing result.


In the last session about gitpilot, we agreed to ship the REST API first.


Note: In the last session about gitpilot, we agreed to ship the REST API first.


General background notes about REST API configuration and trade-offs.


Previously, project:gitpilot used a different approach for REST API; this is now superseded.


A conflicting note claims project:gitpilot uses the UI first for REST API.


In an old session we briefly mentioned REST API, but nothing was decided.


In the last session about other-project, we agreed to ship the REST API first.


The last eval.harness run on ruslanmv-web produced a passing result.


Note: The last eval.harness run on ruslanmv-web produced a passing result.


General background notes about eval.harness configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for eval.harness; this is now superseded.


A conflicting note claims project:ruslanmv-web uses failing for eval.harness.


In an old session we briefly mentioned eval.harness, but nothing was decided.


The last eval.harness run on other-project produced a passing result.


The last experiments.runner run on ruslanmv-web produced a passing result.


Note: The last experiments.runner run on ruslanmv-web produced a passing result.


General background notes about experiments.runner configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for experiments.runner; this is now superseded.


A conflicting note claims project:ruslanmv-web uses failing for experiments.runner.


In an old session we briefly mentioned experiments.runner, but nothing was decided.


The last experiments.runner run on other-project produced a passing result.


The last pytest run on ruslanmv-web produced a passing result.


Note: The last pytest run on ruslanmv-web produced a passing result.


General background notes about pytest configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for pytest; this is now superseded.


A conflicting note claims project:ruslanmv-web uses failing for pytest.


In an old session we briefly mentioned pytest, but nothing was decided.


The last pytest run on other-project produced a passing result.


In the last session about ruslanmv-web, we agreed to ship the REST API first.


Note: In the last session about ruslanmv-web, we agreed to ship the REST API first.


General background notes about REST API configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for REST API; this is now superseded.


A conflicting note claims project:ruslanmv-web uses the UI first for REST API.


In an old session we briefly mentioned REST API, but nothing was decided.


In the last session about other-project, we agreed to ship the REST API first.


The matrix-context whitepaper abstract section states that routed typed context cuts distractors at equal recall.


Note: The matrix-context whitepaper abstract section states that routed typed context cuts distractors at equal recall.


General background notes about abstract configuration and trade-offs.


Previously, project:matrix-context used a different approach for abstract; this is now superseded.


A conflicting note claims project:matrix-context uses increases recall for abstract.


In an old session we briefly mentioned abstract, but nothing was decided.


The other-project whitepaper abstract section states that routed typed context cuts distractors at equal recall.


The matrix-context whitepaper method section states that routed typed context cuts distractors at equal recall.


Note: The matrix-context whitepaper method section states that routed typed context cuts distractors at equal recall.


General background notes about method configuration and trade-offs.


Previously, project:matrix-context used a different approach for method; this is now superseded.


A conflicting note claims project:matrix-context uses increases recall for method.


In an old session we briefly mentioned method, but nothing was decided.


The other-project whitepaper method section states that routed typed context cuts distractors at equal recall.


The matrix-context whitepaper limitations section states that routed typed context cuts distractors at equal recall.


Note: The matrix-context whitepaper limitations section states that routed typed context cuts distractors at equal recall.


General background notes about limitations configuration and trade-offs.


Previously, project:matrix-context used a different approach for limitations; this is now superseded.


A conflicting note claims project:matrix-context uses increases recall for limitations.


In an old session we briefly mentioned limitations, but nothing was decided.


The other-project whitepaper limitations section states that routed typed context cuts distractors at equal recall.


The matrix-context whitepaper results section states that routed typed context cuts distractors at equal recall.


Note: The matrix-context whitepaper results section states that routed typed context cuts distractors at equal recall.


General background notes about results configuration and trade-offs.


Previously, project:matrix-context used a different approach for results; this is now superseded.


A conflicting note claims project:matrix-context uses increases recall for results.


In an old session we briefly mentioned results, but nothing was decided.


The other-project whitepaper results section states that routed typed context cuts distractors at equal recall.


The matrix-context whitepaper positioning section states that routed typed context cuts distractors at equal recall.


Note: The matrix-context whitepaper positioning section states that routed typed context cuts distractors at equal recall.


General background notes about positioning configuration and trade-offs.


Previously, project:matrix-context used a different approach for positioning; this is now superseded.


A conflicting note claims project:matrix-context uses increases recall for positioning.


In an old session we briefly mentioned positioning, but nothing was decided.


The other-project whitepaper positioning section states that routed typed context cuts distractors at equal recall.


The agent-generator whitepaper abstract section states that routed typed context cuts distractors at equal recall.


Note: The agent-generator whitepaper abstract section states that routed typed context cuts distractors at equal recall.


General background notes about abstract configuration and trade-offs.


Previously, project:agent-generator used a different approach for abstract; this is now superseded.


A conflicting note claims project:agent-generator uses increases recall for abstract.


In an old session we briefly mentioned abstract, but nothing was decided.


The other-project whitepaper abstract section states that routed typed context cuts distractors at equal recall.


The agent-generator whitepaper method section states that routed typed context cuts distractors at equal recall.


Note: The agent-generator whitepaper method section states that routed typed context cuts distractors at equal recall.


General background notes about method configuration and trade-offs.


Previously, project:agent-generator used a different approach for method; this is now superseded.


A conflicting note claims project:agent-generator uses increases recall for method.


In an old session we briefly mentioned method, but nothing was decided.


The other-project whitepaper method section states that routed typed context cuts distractors at equal recall.


The agent-generator whitepaper limitations section states that routed typed context cuts distractors at equal recall.


Note: The agent-generator whitepaper limitations section states that routed typed context cuts distractors at equal recall.


General background notes about limitations configuration and trade-offs.


Previously, project:agent-generator used a different approach for limitations; this is now superseded.


A conflicting note claims project:agent-generator uses increases recall for limitations.


In an old session we briefly mentioned limitations, but nothing was decided.


The other-project whitepaper limitations section states that routed typed context cuts distractors at equal recall.


The agent-generator whitepaper results section states that routed typed context cuts distractors at equal recall.


Note: The agent-generator whitepaper results section states that routed typed context cuts distractors at equal recall.


General background notes about results configuration and trade-offs.


Previously, project:agent-generator used a different approach for results; this is now superseded.


A conflicting note claims project:agent-generator uses increases recall for results.


In an old session we briefly mentioned results, but nothing was decided.


The other-project whitepaper results section states that routed typed context cuts distractors at equal recall.


The agent-generator whitepaper positioning section states that routed typed context cuts distractors at equal recall.


Note: The agent-generator whitepaper positioning section states that routed typed context cuts distractors at equal recall.


General background notes about positioning configuration and trade-offs.


Previously, project:agent-generator used a different approach for positioning; this is now superseded.


A conflicting note claims project:agent-generator uses increases recall for positioning.


In an old session we briefly mentioned positioning, but nothing was decided.


The other-project whitepaper positioning section states that routed typed context cuts distractors at equal recall.


The homepilot whitepaper abstract section states that routed typed context cuts distractors at equal recall.


Note: The homepilot whitepaper abstract section states that routed typed context cuts distractors at equal recall.


General background notes about abstract configuration and trade-offs.


Previously, project:homepilot used a different approach for abstract; this is now superseded.


A conflicting note claims project:homepilot uses increases recall for abstract.


In an old session we briefly mentioned abstract, but nothing was decided.


The other-project whitepaper abstract section states that routed typed context cuts distractors at equal recall.


The homepilot whitepaper method section states that routed typed context cuts distractors at equal recall.


Note: The homepilot whitepaper method section states that routed typed context cuts distractors at equal recall.


General background notes about method configuration and trade-offs.


Previously, project:homepilot used a different approach for method; this is now superseded.


A conflicting note claims project:homepilot uses increases recall for method.


In an old session we briefly mentioned method, but nothing was decided.


The other-project whitepaper method section states that routed typed context cuts distractors at equal recall.


The homepilot whitepaper limitations section states that routed typed context cuts distractors at equal recall.


Note: The homepilot whitepaper limitations section states that routed typed context cuts distractors at equal recall.


General background notes about limitations configuration and trade-offs.


Previously, project:homepilot used a different approach for limitations; this is now superseded.


A conflicting note claims project:homepilot uses increases recall for limitations.


In an old session we briefly mentioned limitations, but nothing was decided.


The other-project whitepaper limitations section states that routed typed context cuts distractors at equal recall.


The homepilot whitepaper results section states that routed typed context cuts distractors at equal recall.


Note: The homepilot whitepaper results section states that routed typed context cuts distractors at equal recall.


General background notes about results configuration and trade-offs.


Previously, project:homepilot used a different approach for results; this is now superseded.


A conflicting note claims project:homepilot uses increases recall for results.


In an old session we briefly mentioned results, but nothing was decided.


The other-project whitepaper results section states that routed typed context cuts distractors at equal recall.


The homepilot whitepaper positioning section states that routed typed context cuts distractors at equal recall.


Note: The homepilot whitepaper positioning section states that routed typed context cuts distractors at equal recall.


General background notes about positioning configuration and trade-offs.


Previously, project:homepilot used a different approach for positioning; this is now superseded.


A conflicting note claims project:homepilot uses increases recall for positioning.


In an old session we briefly mentioned positioning, but nothing was decided.


The other-project whitepaper positioning section states that routed typed context cuts distractors at equal recall.


The gitpilot whitepaper abstract section states that routed typed context cuts distractors at equal recall.


Note: The gitpilot whitepaper abstract section states that routed typed context cuts distractors at equal recall.


General background notes about abstract configuration and trade-offs.


Previously, project:gitpilot used a different approach for abstract; this is now superseded.


A conflicting note claims project:gitpilot uses increases recall for abstract.


In an old session we briefly mentioned abstract, but nothing was decided.


The other-project whitepaper abstract section states that routed typed context cuts distractors at equal recall.


The gitpilot whitepaper method section states that routed typed context cuts distractors at equal recall.


Note: The gitpilot whitepaper method section states that routed typed context cuts distractors at equal recall.


General background notes about method configuration and trade-offs.


Previously, project:gitpilot used a different approach for method; this is now superseded.


A conflicting note claims project:gitpilot uses increases recall for method.


In an old session we briefly mentioned method, but nothing was decided.


The other-project whitepaper method section states that routed typed context cuts distractors at equal recall.


The gitpilot whitepaper limitations section states that routed typed context cuts distractors at equal recall.


Note: The gitpilot whitepaper limitations section states that routed typed context cuts distractors at equal recall.


General background notes about limitations configuration and trade-offs.


Previously, project:gitpilot used a different approach for limitations; this is now superseded.


A conflicting note claims project:gitpilot uses increases recall for limitations.


In an old session we briefly mentioned limitations, but nothing was decided.


The other-project whitepaper limitations section states that routed typed context cuts distractors at equal recall.


The gitpilot whitepaper results section states that routed typed context cuts distractors at equal recall.


Note: The gitpilot whitepaper results section states that routed typed context cuts distractors at equal recall.


General background notes about results configuration and trade-offs.


Previously, project:gitpilot used a different approach for results; this is now superseded.


A conflicting note claims project:gitpilot uses increases recall for results.


In an old session we briefly mentioned results, but nothing was decided.


The other-project whitepaper results section states that routed typed context cuts distractors at equal recall.


The gitpilot whitepaper positioning section states that routed typed context cuts distractors at equal recall.


Note: The gitpilot whitepaper positioning section states that routed typed context cuts distractors at equal recall.


General background notes about positioning configuration and trade-offs.


Previously, project:gitpilot used a different approach for positioning; this is now superseded.


A conflicting note claims project:gitpilot uses increases recall for positioning.


In an old session we briefly mentioned positioning, but nothing was decided.


The other-project whitepaper positioning section states that routed typed context cuts distractors at equal recall.


The ruslanmv-web whitepaper abstract section states that routed typed context cuts distractors at equal recall.


Note: The ruslanmv-web whitepaper abstract section states that routed typed context cuts distractors at equal recall.


General background notes about abstract configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for abstract; this is now superseded.


A conflicting note claims project:ruslanmv-web uses increases recall for abstract.


In an old session we briefly mentioned abstract, but nothing was decided.


The other-project whitepaper abstract section states that routed typed context cuts distractors at equal recall.


The ruslanmv-web whitepaper method section states that routed typed context cuts distractors at equal recall.


Note: The ruslanmv-web whitepaper method section states that routed typed context cuts distractors at equal recall.


General background notes about method configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for method; this is now superseded.


A conflicting note claims project:ruslanmv-web uses increases recall for method.


In an old session we briefly mentioned method, but nothing was decided.


The other-project whitepaper method section states that routed typed context cuts distractors at equal recall.


The ruslanmv-web whitepaper limitations section states that routed typed context cuts distractors at equal recall.


Note: The ruslanmv-web whitepaper limitations section states that routed typed context cuts distractors at equal recall.


General background notes about limitations configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for limitations; this is now superseded.


A conflicting note claims project:ruslanmv-web uses increases recall for limitations.


In an old session we briefly mentioned limitations, but nothing was decided.


The other-project whitepaper limitations section states that routed typed context cuts distractors at equal recall.


The ruslanmv-web whitepaper results section states that routed typed context cuts distractors at equal recall.


Note: The ruslanmv-web whitepaper results section states that routed typed context cuts distractors at equal recall.


General background notes about results configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for results; this is now superseded.


A conflicting note claims project:ruslanmv-web uses increases recall for results.


In an old session we briefly mentioned results, but nothing was decided.


The other-project whitepaper results section states that routed typed context cuts distractors at equal recall.


The ruslanmv-web whitepaper positioning section states that routed typed context cuts distractors at equal recall.


Note: The ruslanmv-web whitepaper positioning section states that routed typed context cuts distractors at equal recall.


General background notes about positioning configuration and trade-offs.


Previously, project:ruslanmv-web used a different approach for positioning; this is now superseded.


A conflicting note claims project:ruslanmv-web uses increases recall for positioning.


In an old session we briefly mentioned positioning, but nothing was decided.


The other-project whitepaper positioning section states that routed typed context cuts distractors at equal recall.


Background fact #0 loosely related to store and cli.


Background fact #1 loosely related to limitations and cli.


Background fact #2 loosely related to tone and cli.


Background fact #3 loosely related to tone and embedder.


Background fact #4 loosely related to abstract and router.


Background fact #5 loosely related to limitations and store.


Background fact #6 loosely related to MCP server and retrieval.


Background fact #7 loosely related to local-first and store.


Background fact #8 loosely related to audit logs and cli.


Background fact #9 loosely related to API keys and cli.


Background fact #10 loosely related to positioning and cli.


Background fact #11 loosely related to REST API and retrieval.


Background fact #12 loosely related to PII and store.


Background fact #13 loosely related to audit logs and store.


Background fact #14 loosely related to store and retrieval.


Background fact #15 loosely related to secrets and embedder.


Background fact #16 loosely related to cli and cli.


Background fact #17 loosely related to storage backend and cli.


Background fact #18 loosely related to API keys and router.


Background fact #19 loosely related to positioning and assembler.


Background fact #20 loosely related to results and cli.


Background fact #21 loosely related to pytest and cli.


Background fact #22 loosely related to results and assembler.


Background fact #23 loosely related to experiments.runner and embedder.


Background fact #24 loosely related to local-first and cli.


Background fact #25 loosely related to abstract and embedder.


Background fact #26 loosely related to MCP server and embedder.


Background fact #27 loosely related to router and store.


Background fact #28 loosely related to abstract and assembler.


Background fact #29 loosely related to cli and retrieval.


Background fact #30 loosely related to REST API and embedder.


Background fact #31 loosely related to store and retrieval.


Background fact #32 loosely related to retrieval and retrieval.


Background fact #33 loosely related to positioning and router.


Background fact #34 loosely related to local-first and embedder.


Background fact #35 loosely related to audit logs and assembler.


Background fact #36 loosely related to router and retrieval.


Background fact #37 loosely related to method and cli.


Background fact #38 loosely related to cli and store.


Background fact #39 loosely related to cli and assembler.


Background fact #40 loosely related to cli and cli.


Background fact #41 loosely related to MCP server and retrieval.


Background fact #42 loosely related to Milvus and embedder.


Background fact #43 loosely related to eval.harness and assembler.


Background fact #44 loosely related to audit logs and store.


Background fact #45 loosely related to API keys and assembler.


Background fact #46 loosely related to storage backend and store.


Background fact #47 loosely related to store and store.


Background fact #48 loosely related to router and store.


Background fact #49 loosely related to retrieval and retrieval.


Background fact #50 loosely related to audit logs and router.


Background fact #51 loosely related to router and router.


Background fact #52 loosely related to positioning and router.


Background fact #53 loosely related to method and router.


Background fact #54 loosely related to embedder and store.


Background fact #55 loosely related to abstract and router.


Background fact #56 loosely related to pytest and embedder.


Background fact #57 loosely related to limitations and assembler.


Background fact #58 loosely related to eval.harness and embedder.


Background fact #59 loosely related to Milvus and embedder.


Background fact #60 loosely related to embedder and store.


Background fact #61 loosely related to secrets and store.


Background fact #62 loosely related to storage backend and assembler.


Background fact #63 loosely related to MCP server and router.


Background fact #64 loosely related to results and assembler.


Background fact #65 loosely related to method and router.


Background fact #66 loosely related to store and retrieval.


Background fact #67 loosely related to retrieval and assembler.


Background fact #68 loosely related to storage backend and embedder.


Background fact #69 loosely related to cli and assembler.


Background fact #70 loosely related to positioning and retrieval.


Background fact #71 loosely related to limitations and retrieval.


Background fact #72 loosely related to API keys and assembler.


Background fact #73 loosely related to eval.harness and assembler.


Background fact #74 loosely related to abstract and retrieval.


Background fact #75 loosely related to tone and router.


Background fact #76 loosely related to local-first and router.


Background fact #77 loosely related to API keys and assembler.


Background fact #78 loosely related to method and router.


Background fact #79 loosely related to Milvus and store.


Background fact #80 loosely related to local-first and cli.


Background fact #81 loosely related to results and assembler.


Background fact #82 loosely related to pytest and assembler.


Background fact #83 loosely related to PII and embedder.


Background fact #84 loosely related to limitations and cli.


Background fact #85 loosely related to storage backend and assembler.


Background fact #86 loosely related to REST API and router.


Background fact #87 loosely related to tone and store.


Background fact #88 loosely related to eval.harness and cli.


Background fact #89 loosely related to cli and store.


Background fact #90 loosely related to tone and embedder.


Background fact #91 loosely related to secrets and embedder.


Background fact #92 loosely related to storage backend and store.


Background fact #93 loosely related to positioning and embedder.


Background fact #94 loosely related to Milvus and embedder.


Background fact #95 loosely related to router and cli.


Background fact #96 loosely related to assembler and retrieval.


Background fact #97 loosely related to results and retrieval.


Background fact #98 loosely related to results and cli.


Background fact #99 loosely related to retrieval and embedder.


Background fact #100 loosely related to MCP server and store.


Background fact #101 loosely related to tone and store.


Background fact #102 loosely related to API keys and retrieval.


Background fact #103 loosely related to router and assembler.


Background fact #104 loosely related to limitations and cli.


Background fact #105 loosely related to tone and embedder.


Background fact #106 loosely related to store and assembler.


Background fact #107 loosely related to tone and router.


Background fact #108 loosely related to API keys and cli.


Background fact #109 loosely related to retrieval and retrieval.


Background fact #110 loosely related to local-first and router.


Background fact #111 loosely related to storage backend and router.


Background fact #112 loosely related to cli and retrieval.


Background fact #113 loosely related to store and embedder.


Background fact #114 loosely related to embedder and store.


Background fact #115 loosely related to store and cli.


Background fact #116 loosely related to storage backend and store.


Background fact #117 loosely related to retrieval and router.


Background fact #118 loosely related to PII and router.


Background fact #119 loosely related to secrets and assembler.


Background fact #120 loosely related to embedder and store.


Background fact #121 loosely related to local-first and cli.


Background fact #122 loosely related to Milvus and store.


Background fact #123 loosely related to embedder and cli.


Background fact #124 loosely related to audit logs and assembler.


Background fact #125 loosely related to cli and router.


Background fact #126 loosely related to cli and cli.


Background fact #127 loosely related to tone and embedder.


Background fact #128 loosely related to cli and embedder.


Background fact #129 loosely related to local-first and retrieval.


Background fact #130 loosely related to positioning and embedder.


Background fact #131 loosely related to limitations and retrieval.


Background fact #132 loosely related to router and retrieval.


Background fact #133 loosely related to API keys and retrieval.


Background fact #134 loosely related to experiments.runner and retrieval.


Background fact #135 loosely related to PII and cli.


Background fact #136 loosely related to positioning and embedder.


Background fact #137 loosely related to storage backend and retrieval.


Background fact #138 loosely related to retrieval and router.


Background fact #139 loosely related to tone and retrieval.


Background fact #140 loosely related to tone and assembler.


Background fact #141 loosely related to PII and router.


Background fact #142 loosely related to retrieval and embedder.


Background fact #143 loosely related to assembler and router.


Background fact #144 loosely related to secrets and retrieval.


Background fact #145 loosely related to PII and retrieval.


Background fact #146 loosely related to audit logs and router.


Background fact #147 loosely related to secrets and router.


Background fact #148 loosely related to audit logs and assembler.


Background fact #149 loosely related to storage backend and cli.


Background fact #150 loosely related to method and retrieval.


Background fact #151 loosely related to embedder and assembler.


Background fact #152 loosely related to limitations and embedder.


Background fact #153 loosely related to tone and cli.


Background fact #154 loosely related to tone and store.


Background fact #155 loosely related to PII and cli.


Background fact #156 loosely related to storage backend and router.


Background fact #157 loosely related to Milvus and cli.


Background fact #158 loosely related to router and assembler.


Background fact #159 loosely related to MCP server and retrieval.