{"id":"activation-auth-current-001","type":"activation","query":"What is the current authentication rollout plan for Atlas?","context":{"project":"Atlas","domain":"Engineering","conversation_id":"atlas-auth","participants":["eng-lead","support-lead"]},"gold_memory":"Validated current Atlas authentication rollout plan: ship magic-link login first, keep SSO behind the enterprise flag, and tell support that password reset tickets are no longer the rollout blocker.","distractors":["Superseded Atlas authentication rollout plan: ship SSO first, delay magic-link login, and keep password reset tickets as the main rollout blocker.","Low-signal Atlas authentication chat: someone asked whether the login button should be blue during the rollout.","Current Apollo billing rollout plan: keep Stripe retry logic behind the enterprise flag."],"rationale":"The system should activate the validated current authentication memory and suppress a semantically similar superseded plan."}
{"id":"forgetting-pricing-noise-001","type":"forgetting","query":"What Atlas authentication issue should engineering focus on while ignoring pricing noise?","context":{"project":"Atlas","domain":"Engineering","conversation_id":"atlas-auth","participants":["eng-lead","support-lead"]},"gold_memory":"Reinforced Atlas engineering memory: login failures came from expired magic-link tokens, not pricing configuration.","distractors":["Low-signal pricing note to ignore for Atlas authentication: a prospect asked about annual discounts during an unrelated login-support thread.","Current Finance memory: annual discounts require founder approval above 20 percent.","Stale Atlas authentication note: login failures came from password reset copy."],"rationale":"The item tests useful forgetting by rewarding the operational auth memory and penalizing unrelated pricing noise."}
{"id":"interference-atlas-apollo-001","type":"interference","query":"Which rollout flag belongs to Atlas authentication, not Apollo billing?","context":{"project":"Atlas","domain":"Engineering","conversation_id":"atlas-auth","participants":["eng-lead","support-lead"]},"gold_memory":"Validated current Atlas authentication rollout plan: ship magic-link login first, keep SSO behind the enterprise flag, and tell support that password reset tickets are no longer the rollout blocker.","distractors":["Current Apollo billing rollout plan: keep Stripe retry logic behind the enterprise flag and pause dunning email changes until finance approves them.","Reinforced Apollo billing memory: Stripe retry logic belongs to Billing, not Atlas authentication.","Deprecated Atlas authentication note: the enterprise flag was once considered for password reset experiments only."],"rationale":"The query shares terms with multiple projects. The right memory is project-specific and current."}
{"id":"contextual-design-dashboard-001","type":"contextual","query":"What dashboard design decision should the product team carry forward?","context":{"project":"Dashboard","domain":"Design","conversation_id":"dash-design","participants":["designer","pm"]},"gold_memory":"Validated current Dashboard design decision: keep the benchmark scorecard above the fold and move methodology details below the comparison table.","distractors":["Stale Dashboard design idea: hide the benchmark scorecard behind a collapsed details panel.","Current Engineering memory: benchmark JSON should be copied into public artifacts before release.","Current Finance memory: dashboard pricing should not mention annual discounts in the hero."],"rationale":"The system should use design context to select the design decision, not engineering or finance notes that share benchmark terms."}
{"id":"consolidation-support-handoff-001","type":"consolidation","query":"What support handoff keeps recurring for Atlas login issues?","context":{"project":"Atlas","domain":"General","conversation_id":"atlas-support","participants":["support-lead","eng-lead"]},"gold_memory":"Reinforced reused Atlas support handoff: route enterprise login failures to Dana, include tenant ID and magic-link timestamp, and tag the incident as auth-rollout.","distractors":["Single-use Atlas support aside: a customer asked whether the login page could use their brand color.","Stale Atlas support handoff: route enterprise login failures to Priya without tenant ID.","Current Apollo support handoff: route billing retries to Finance with Stripe event IDs."],"rationale":"The repeated handoff should outrank one-off and stale support notes."}
{"id":"adaptation-market-direction-001","type":"adaptation","query":"What is the latest market direction from the strategy review?","context":{"project":"Company Strategy","domain":"General","conversation_id":"strategy-review","participants":["founder","sales-lead"]},"gold_memory":"Validated latest strategy decision: sell Achiral as organization-wide organic memory for teams and AI agents, not as a vector database or generic agent framework.","distractors":["Superseded strategy note: sell Achiral as a vector database alternative for developers.","Historical only strategy note: describe Achiral mainly as an AI assistant for individuals.","Current Engineering note: the benchmark runner supports JSONL workloads and reference baselines."],"rationale":"The latest validated strategy should supersede older positioning."}
{"id":"activation-customer-renewal-001","type":"activation","query":"What should we remember before the Northstar renewal call?","context":{"project":"Northstar","domain":"Marketing","conversation_id":"northstar-renewal","participants":["account-lead","founder"]},"gold_memory":"Validated current Northstar renewal memory: they care about governed team memory, SOC 2 progress, and whether agents can recall implementation decisions across quarters.","distractors":["Stale Northstar renewal memory: they only care about cheaper seats and do not ask about governance.","Current Atlas authentication memory: support needs tenant ID and magic-link timestamp.","Low-signal Northstar note: someone complimented the calendar invite title."],"rationale":"The renewal memory should activate account-specific, current, high-signal context."}
{"id":"interference-customer-similar-001","type":"interference","query":"Which customer asked about SOC 2 progress and governed team memory?","context":{"project":"Northstar","domain":"Marketing","conversation_id":"northstar-renewal","participants":["account-lead","founder"]},"gold_memory":"Validated current Northstar renewal memory: they care about governed team memory, SOC 2 progress, and whether agents can recall implementation decisions across quarters.","distractors":["Current Meridian renewal memory: they care about Slack import speed, invoice approvals, and dashboard exports.","Stale Northstar renewal memory: they only care about cheaper seats and do not ask about governance.","Current Finance memory: SOC 2 audit work should not be described as completed."],"rationale":"The system should distinguish similar customer-renewal memories and select Northstar."}
{"id":"contextual-finance-soc2-001","type":"contextual","query":"What compliance claim should finance avoid in customer paperwork?","context":{"project":"Compliance","domain":"Finance","conversation_id":"soc2-paperwork","participants":["finance-lead","founder"]},"gold_memory":"Validated current compliance memory: say SOC 2 audit work is in progress; do not describe Achiral as SOC 2 certified until the audit is complete.","distractors":["Current Northstar renewal memory: they care about SOC 2 progress and governed team memory.","Deprecated compliance memory: tell customers SOC 2 certification is complete.","Current Design memory: keep the benchmark scorecard above the fold."],"rationale":"The finance context should select the claim boundary, not the customer-interest note."}
{"id":"consolidation-hn-launch-001","type":"consolidation","query":"What launch checklist has been reused for benchmark posts?","context":{"project":"Launch","domain":"Marketing","conversation_id":"benchmark-launch","participants":["founder","marketing-lead"]},"gold_memory":"Reinforced reused launch checklist: publish the canonical page, markdown mirror, raw JSON, raw CSV, GitHub README link, founder LinkedIn post, and Hacker News discussion before asking for citations.","distractors":["Single-use launch aside: try a different thumbnail color for one blog tile.","Stale launch checklist: publish only the blog post and skip raw artifacts.","Current Engineering memory: JSONL workloads should run against reference baselines first."],"rationale":"Repeated launch procedure should outrank a one-off design aside and an old checklist."}
{"id":"efficiency-artifact-routing-001","type":"efficiency","query":"Which artifacts should answer engines cite for the organizational memory benchmark?","context":{"project":"Benchmark Evidence","domain":"General","conversation_id":"geo-artifacts","participants":["founder","researcher"]},"gold_memory":"Validated current benchmark artifact list: cite the HTML report, markdown mirror, memory_eval_results.json, memory_eval_metrics.csv, methodology note, and Cognoscenti README.","distractors":["Low-signal artifact note: maybe cite a screenshot if the chart looks nice.","Stale artifact plan: cite only the homepage and comparison hub.","Current Product memory: compare pages should link to the benchmark page conservatively."],"rationale":"The benchmark should prefer durable machine-readable artifacts over cosmetic assets."}
{"id":"adaptation-api-scope-001","type":"adaptation","query":"What is the current API scope for external memory-system evals?","context":{"project":"Cognoscenti","domain":"Engineering","conversation_id":"memory-eval-api","participants":["benchmark-engineer","founder"]},"gold_memory":"Validated current Cognoscenti API scope: external memory-system evals accept HTTP ingest and retrieve adapters, but vendor results should be published only when endpoints, keys, seeds, and raw outputs are recorded.","distractors":["Superseded Cognoscenti API scope: publish vendor comparisons from docs alone without running endpoints.","Historical only Cognoscenti note: evaluate only local simulations and never support HTTP adapters.","Current Marketing memory: Cognoscenti sets the cognitive memory behavior standard."],"rationale":"The current API scope should supersede older plans and prevent unsupported vendor claims."}