ticket_id: "tkt_pmem_scope_policy_and_ingest_rules" title: "Memory scope policy and project-ingest operating rules are codified" agent: "codex" done: false goal: "The integration has an explicit system rule and operating guidance for project-scoped memory, scope separation, and when to refresh project knowledge."

Tasks

Add the hard system rule from the source so that when the active project is set, durable repo facts, architecture decisions, workflow rules, team conventions, and recurring issues are stored with the Remember tool using project scope for that project.
Document the intended scope split from the source: global for user-wide preferences or instructions, project for repo-specific knowledge, and session for temporary task state.
Document the project ingest triggers from the source: first repo connection, material architecture changes, major tickets landing, and convention changes.
Document the source limitation that setting activeProject and enabling AI extraction is not sufficient by itself without the write-path patch.

A system rule exists that directs durable project facts into project scope for the active project.
Operational guidance defines the intended use of global, project, and session scopes.
Operational guidance defines when to run project ingest and states the limitation around activeProject plus AI extraction.

Review the system rule and verify it matches the source behavior for project-scoped durable facts.
Review the operational guidance and verify it includes the scope split, ingest triggers, and the stated limitation.