data/v0.2/cases.jsonl

{"id":"env-001","query":"What database does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses db-staging.internal for its database.","tags":["staging","database","infra"],"depth":1},{"id":"e2","text":"The production environment uses db-prod.internal for its database.","tags":["production","database","infra"],"depth":1},{"id":"e3","text":"The development environment uses db-dev.internal for its database.","tags":["development","database","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the database.","tags":["staging","database","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-002","query":"What database does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses db-prod.internal for its database.","tags":["production","database","infra"],"depth":1},{"id":"e2","text":"The staging environment uses db-staging.internal for its database.","tags":["staging","database","infra"],"depth":1},{"id":"e3","text":"The development environment uses db-dev.internal for its database.","tags":["development","database","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the database.","tags":["production","database","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-003","query":"What database does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses db-dev.internal for its database.","tags":["development","database","infra"],"depth":1},{"id":"e2","text":"The production environment uses db-staging.internal for its database.","tags":["production","database","infra"],"depth":1},{"id":"e3","text":"The staging environment uses db-prod.internal for its database.","tags":["staging","database","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the database.","tags":["development","database","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-004","query":"What redis cache does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses redis-staging.internal for its redis cache.","tags":["staging","redis-cache","infra"],"depth":1},{"id":"e2","text":"The production environment uses redis-prod.internal for its redis cache.","tags":["production","redis-cache","infra"],"depth":1},{"id":"e3","text":"The development environment uses redis-dev.internal for its redis cache.","tags":["development","redis-cache","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the redis cache.","tags":["staging","redis-cache","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-005","query":"What redis cache does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses redis-prod.internal for its redis cache.","tags":["production","redis-cache","infra"],"depth":1},{"id":"e2","text":"The staging environment uses redis-staging.internal for its redis cache.","tags":["staging","redis-cache","infra"],"depth":1},{"id":"e3","text":"The development environment uses redis-dev.internal for its redis cache.","tags":["development","redis-cache","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the redis cache.","tags":["production","redis-cache","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-006","query":"What redis cache does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses redis-dev.internal for its redis cache.","tags":["development","redis-cache","infra"],"depth":1},{"id":"e2","text":"The production environment uses redis-staging.internal for its redis cache.","tags":["production","redis-cache","infra"],"depth":1},{"id":"e3","text":"The staging environment uses redis-prod.internal for its redis cache.","tags":["staging","redis-cache","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the redis cache.","tags":["development","redis-cache","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-007","query":"What object storage bucket does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses assets-staging for its object storage bucket.","tags":["staging","object-storage-bucket","infra"],"depth":1},{"id":"e2","text":"The production environment uses assets-prod for its object storage bucket.","tags":["production","object-storage-bucket","infra"],"depth":1},{"id":"e3","text":"The development environment uses assets-dev for its object storage bucket.","tags":["development","object-storage-bucket","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the object storage bucket.","tags":["staging","object-storage-bucket","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-008","query":"What object storage bucket does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses assets-prod for its object storage bucket.","tags":["production","object-storage-bucket","infra"],"depth":1},{"id":"e2","text":"The staging environment uses assets-staging for its object storage bucket.","tags":["staging","object-storage-bucket","infra"],"depth":1},{"id":"e3","text":"The development environment uses assets-dev for its object storage bucket.","tags":["development","object-storage-bucket","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the object storage bucket.","tags":["production","object-storage-bucket","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-009","query":"What object storage bucket does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses assets-dev for its object storage bucket.","tags":["development","object-storage-bucket","infra"],"depth":1},{"id":"e2","text":"The production environment uses assets-staging for its object storage bucket.","tags":["production","object-storage-bucket","infra"],"depth":1},{"id":"e3","text":"The staging environment uses assets-prod for its object storage bucket.","tags":["staging","object-storage-bucket","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the object storage bucket.","tags":["development","object-storage-bucket","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-010","query":"What email sender does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses ses-staging for its email sender.","tags":["staging","email-sender","infra"],"depth":1},{"id":"e2","text":"The production environment uses ses-prod for its email sender.","tags":["production","email-sender","infra"],"depth":1},{"id":"e3","text":"The development environment uses ses-dev for its email sender.","tags":["development","email-sender","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the email sender.","tags":["staging","email-sender","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-011","query":"What email sender does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses ses-prod for its email sender.","tags":["production","email-sender","infra"],"depth":1},{"id":"e2","text":"The staging environment uses ses-staging for its email sender.","tags":["staging","email-sender","infra"],"depth":1},{"id":"e3","text":"The development environment uses ses-dev for its email sender.","tags":["development","email-sender","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the email sender.","tags":["production","email-sender","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-012","query":"What email sender does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses ses-dev for its email sender.","tags":["development","email-sender","infra"],"depth":1},{"id":"e2","text":"The production environment uses ses-staging for its email sender.","tags":["production","email-sender","infra"],"depth":1},{"id":"e3","text":"The staging environment uses ses-prod for its email sender.","tags":["staging","email-sender","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the email sender.","tags":["development","email-sender","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-013","query":"What nats cluster does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses nats-staging.internal for its nats cluster.","tags":["staging","nats-cluster","infra"],"depth":1},{"id":"e2","text":"The production environment uses nats-prod.internal for its nats cluster.","tags":["production","nats-cluster","infra"],"depth":1},{"id":"e3","text":"The development environment uses nats-dev.internal for its nats cluster.","tags":["development","nats-cluster","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the nats cluster.","tags":["staging","nats-cluster","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-014","query":"What nats cluster does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses nats-prod.internal for its nats cluster.","tags":["production","nats-cluster","infra"],"depth":1},{"id":"e2","text":"The staging environment uses nats-staging.internal for its nats cluster.","tags":["staging","nats-cluster","infra"],"depth":1},{"id":"e3","text":"The development environment uses nats-dev.internal for its nats cluster.","tags":["development","nats-cluster","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the nats cluster.","tags":["production","nats-cluster","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-015","query":"What nats cluster does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses nats-dev.internal for its nats cluster.","tags":["development","nats-cluster","infra"],"depth":1},{"id":"e2","text":"The production environment uses nats-staging.internal for its nats cluster.","tags":["production","nats-cluster","infra"],"depth":1},{"id":"e3","text":"The staging environment uses nats-prod.internal for its nats cluster.","tags":["staging","nats-cluster","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the nats cluster.","tags":["development","nats-cluster","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-016","query":"What API base URL does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses https://api-staging.ecue.ai for its API base URL.","tags":["staging","api-base-url","infra"],"depth":1},{"id":"e2","text":"The production environment uses https://api.ecue.ai for its API base URL.","tags":["production","api-base-url","infra"],"depth":1},{"id":"e3","text":"The development environment uses https://api-dev.ecue.ai for its API base URL.","tags":["development","api-base-url","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the API base URL.","tags":["staging","api-base-url","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-017","query":"What API base URL does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses https://api.ecue.ai for its API base URL.","tags":["production","api-base-url","infra"],"depth":1},{"id":"e2","text":"The staging environment uses https://api-staging.ecue.ai for its API base URL.","tags":["staging","api-base-url","infra"],"depth":1},{"id":"e3","text":"The development environment uses https://api-dev.ecue.ai for its API base URL.","tags":["development","api-base-url","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the API base URL.","tags":["production","api-base-url","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-018","query":"What API base URL does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses https://api-dev.ecue.ai for its API base URL.","tags":["development","api-base-url","infra"],"depth":1},{"id":"e2","text":"The production environment uses https://api-staging.ecue.ai for its API base URL.","tags":["production","api-base-url","infra"],"depth":1},{"id":"e3","text":"The staging environment uses https://api.ecue.ai for its API base URL.","tags":["staging","api-base-url","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the API base URL.","tags":["development","api-base-url","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-019","query":"What metrics backend does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses vm-staging.internal for its metrics backend.","tags":["staging","metrics-backend","infra"],"depth":1},{"id":"e2","text":"The production environment uses vm-prod.internal for its metrics backend.","tags":["production","metrics-backend","infra"],"depth":1},{"id":"e3","text":"The development environment uses vm-dev.internal for its metrics backend.","tags":["development","metrics-backend","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the metrics backend.","tags":["staging","metrics-backend","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-020","query":"What metrics backend does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses vm-prod.internal for its metrics backend.","tags":["production","metrics-backend","infra"],"depth":1},{"id":"e2","text":"The staging environment uses vm-staging.internal for its metrics backend.","tags":["staging","metrics-backend","infra"],"depth":1},{"id":"e3","text":"The development environment uses vm-dev.internal for its metrics backend.","tags":["development","metrics-backend","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the metrics backend.","tags":["production","metrics-backend","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-021","query":"What metrics backend does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses vm-dev.internal for its metrics backend.","tags":["development","metrics-backend","infra"],"depth":1},{"id":"e2","text":"The production environment uses vm-staging.internal for its metrics backend.","tags":["production","metrics-backend","infra"],"depth":1},{"id":"e3","text":"The staging environment uses vm-prod.internal for its metrics backend.","tags":["staging","metrics-backend","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the metrics backend.","tags":["development","metrics-backend","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-022","query":"What auth issuer does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses https://auth-staging.ecue.ai for its auth issuer.","tags":["staging","auth-issuer","infra"],"depth":1},{"id":"e2","text":"The production environment uses https://auth.ecue.ai for its auth issuer.","tags":["production","auth-issuer","infra"],"depth":1},{"id":"e3","text":"The development environment uses https://auth-dev.ecue.ai for its auth issuer.","tags":["development","auth-issuer","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the auth issuer.","tags":["staging","auth-issuer","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-023","query":"What auth issuer does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses https://auth.ecue.ai for its auth issuer.","tags":["production","auth-issuer","infra"],"depth":1},{"id":"e2","text":"The staging environment uses https://auth-staging.ecue.ai for its auth issuer.","tags":["staging","auth-issuer","infra"],"depth":1},{"id":"e3","text":"The development environment uses https://auth-dev.ecue.ai for its auth issuer.","tags":["development","auth-issuer","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the auth issuer.","tags":["production","auth-issuer","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-024","query":"What auth issuer does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses https://auth-dev.ecue.ai for its auth issuer.","tags":["development","auth-issuer","infra"],"depth":1},{"id":"e2","text":"The production environment uses https://auth-staging.ecue.ai for its auth issuer.","tags":["production","auth-issuer","infra"],"depth":1},{"id":"e3","text":"The staging environment uses https://auth.ecue.ai for its auth issuer.","tags":["staging","auth-issuer","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the auth issuer.","tags":["development","auth-issuer","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-025","query":"What artifact bucket does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses artifacts-staging for its artifact bucket.","tags":["staging","artifact-bucket","infra"],"depth":1},{"id":"e2","text":"The production environment uses artifacts-prod for its artifact bucket.","tags":["production","artifact-bucket","infra"],"depth":1},{"id":"e3","text":"The development environment uses artifacts-dev for its artifact bucket.","tags":["development","artifact-bucket","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the artifact bucket.","tags":["staging","artifact-bucket","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-026","query":"What artifact bucket does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses artifacts-prod for its artifact bucket.","tags":["production","artifact-bucket","infra"],"depth":1},{"id":"e2","text":"The staging environment uses artifacts-staging for its artifact bucket.","tags":["staging","artifact-bucket","infra"],"depth":1},{"id":"e3","text":"The development environment uses artifacts-dev for its artifact bucket.","tags":["development","artifact-bucket","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the artifact bucket.","tags":["production","artifact-bucket","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-027","query":"What artifact bucket does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses artifacts-dev for its artifact bucket.","tags":["development","artifact-bucket","infra"],"depth":1},{"id":"e2","text":"The production environment uses artifacts-staging for its artifact bucket.","tags":["production","artifact-bucket","infra"],"depth":1},{"id":"e3","text":"The staging environment uses artifacts-prod for its artifact bucket.","tags":["staging","artifact-bucket","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the artifact bucket.","tags":["development","artifact-bucket","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-028","query":"What search index does staging use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The staging environment uses meili-staging.internal for its search index.","tags":["staging","search-index","infra"],"depth":1},{"id":"e2","text":"The production environment uses meili-prod.internal for its search index.","tags":["production","search-index","infra"],"depth":1},{"id":"e3","text":"The development environment uses meili-dev.internal for its search index.","tags":["development","search-index","infra"],"depth":2},{"id":"e4","text":"The staging environment rotates credentials weekly for the search index.","tags":["staging","search-index","ops"],"depth":2},{"id":"e5","text":"The staging email sender is ses-staging for notification traffic.","tags":["staging","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-029","query":"What search index does production use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The production environment uses meili-prod.internal for its search index.","tags":["production","search-index","infra"],"depth":1},{"id":"e2","text":"The staging environment uses meili-staging.internal for its search index.","tags":["staging","search-index","infra"],"depth":1},{"id":"e3","text":"The development environment uses meili-dev.internal for its search index.","tags":["development","search-index","infra"],"depth":2},{"id":"e4","text":"The production environment rotates credentials weekly for the search index.","tags":["production","search-index","ops"],"depth":2},{"id":"e5","text":"The production email sender is ses-production for notification traffic.","tags":["production","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"env-030","query":"What search index does development use?","adversary_type":"environment_swap","entries":[{"id":"e1","text":"The development environment uses meili-dev.internal for its search index.","tags":["development","search-index","infra"],"depth":1},{"id":"e2","text":"The production environment uses meili-staging.internal for its search index.","tags":["production","search-index","infra"],"depth":1},{"id":"e3","text":"The staging environment uses meili-prod.internal for its search index.","tags":["staging","search-index","infra"],"depth":2},{"id":"e4","text":"The development environment rotates credentials weekly for the search index.","tags":["development","search-index","ops"],"depth":2},{"id":"e5","text":"The development email sender is ses-development for notification traffic.","tags":["development","email","infra"],"depth":3}],"relevant_ids":["e1"],"notes":"Environment swap distractors with same service family."}
{"id":"entity-001","query":"What does Caroline prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Caroline prefers oat milk for daily work.","tags":["caroline","preference"],"depth":1},{"id":"e2","text":"Catherine prefers oat milk for daily work.","tags":["catherine","preference"],"depth":1},{"id":"e3","text":"Caroline also likes black tea in some situations.","tags":["caroline","preference"],"depth":2},{"id":"e4","text":"The team discussed oat milk and black tea during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Caroline wrote a migration note about deployment safety.","tags":["caroline","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-002","query":"What does Jordan prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Jordan prefers standing desk for daily work.","tags":["jordan","preference"],"depth":1},{"id":"e2","text":"Jordyn prefers standing desk for daily work.","tags":["jordyn","preference"],"depth":1},{"id":"e3","text":"Jordan also likes ergonomic chair in some situations.","tags":["jordan","preference"],"depth":2},{"id":"e4","text":"The team discussed standing desk and ergonomic chair during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Jordan wrote a migration note about deployment safety.","tags":["jordan","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-003","query":"What does Alicia prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Alicia prefers Postgres for daily work.","tags":["alicia","preference"],"depth":1},{"id":"e2","text":"Alice prefers Postgres for daily work.","tags":["alice","preference"],"depth":1},{"id":"e3","text":"Alicia also likes MySQL in some situations.","tags":["alicia","preference"],"depth":2},{"id":"e4","text":"The team discussed Postgres and MySQL during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Alicia wrote a migration note about deployment safety.","tags":["alicia","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-004","query":"What does Mika prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Mika prefers vim for daily work.","tags":["mika","preference"],"depth":1},{"id":"e2","text":"Mila prefers vim for daily work.","tags":["mila","preference"],"depth":1},{"id":"e3","text":"Mika also likes emacs in some situations.","tags":["mika","preference"],"depth":2},{"id":"e4","text":"The team discussed vim and emacs during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Mika wrote a migration note about deployment safety.","tags":["mika","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-005","query":"What does Darren prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Darren prefers dark mode for daily work.","tags":["darren","preference"],"depth":1},{"id":"e2","text":"Dorian prefers dark mode for daily work.","tags":["dorian","preference"],"depth":1},{"id":"e3","text":"Darren also likes light mode in some situations.","tags":["darren","preference"],"depth":2},{"id":"e4","text":"The team discussed dark mode and light mode during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Darren wrote a migration note about deployment safety.","tags":["darren","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-006","query":"What does Riley prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Riley prefers GraphQL for daily work.","tags":["riley","preference"],"depth":1},{"id":"e2","text":"Ryan prefers GraphQL for daily work.","tags":["ryan","preference"],"depth":1},{"id":"e3","text":"Riley also likes REST in some situations.","tags":["riley","preference"],"depth":2},{"id":"e4","text":"The team discussed GraphQL and REST during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Riley wrote a migration note about deployment safety.","tags":["riley","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-007","query":"What does Marina prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Marina prefers daily standups for daily work.","tags":["marina","preference"],"depth":1},{"id":"e2","text":"Maria prefers daily standups for daily work.","tags":["maria","preference"],"depth":1},{"id":"e3","text":"Marina also likes weekly status docs in some situations.","tags":["marina","preference"],"depth":2},{"id":"e4","text":"The team discussed daily standups and weekly status docs during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Marina wrote a migration note about deployment safety.","tags":["marina","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-008","query":"What does Talia prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Talia prefers Go modules for daily work.","tags":["talia","preference"],"depth":1},{"id":"e2","text":"Tanya prefers Go modules for daily work.","tags":["tanya","preference"],"depth":1},{"id":"e3","text":"Talia also likes Bazel workspaces in some situations.","tags":["talia","preference"],"depth":2},{"id":"e4","text":"The team discussed Go modules and Bazel workspaces during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Talia wrote a migration note about deployment safety.","tags":["talia","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-009","query":"What does Nolan prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Nolan prefers CUDA containers for daily work.","tags":["nolan","preference"],"depth":1},{"id":"e2","text":"Noah prefers CUDA containers for daily work.","tags":["noah","preference"],"depth":1},{"id":"e3","text":"Nolan also likes CPU-only builds in some situations.","tags":["nolan","preference"],"depth":2},{"id":"e4","text":"The team discussed CUDA containers and CPU-only builds during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Nolan wrote a migration note about deployment safety.","tags":["nolan","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-010","query":"What does Elena prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Elena prefers Linear for daily work.","tags":["elena","preference"],"depth":1},{"id":"e2","text":"Alina prefers Linear for daily work.","tags":["alina","preference"],"depth":1},{"id":"e3","text":"Elena also likes Jira in some situations.","tags":["elena","preference"],"depth":2},{"id":"e4","text":"The team discussed Linear and Jira during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Elena wrote a migration note about deployment safety.","tags":["elena","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-011","query":"What does Sonia prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Sonia prefers dark roast for daily work.","tags":["sonia","preference"],"depth":1},{"id":"e2","text":"Sonya prefers dark roast for daily work.","tags":["sonya","preference"],"depth":1},{"id":"e3","text":"Sonia also likes green tea in some situations.","tags":["sonia","preference"],"depth":2},{"id":"e4","text":"The team discussed dark roast and green tea during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Sonia wrote a migration note about deployment safety.","tags":["sonia","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"entity-012","query":"What does Maren prefer?","adversary_type":"entity_swap","entries":[{"id":"e1","text":"Maren prefers Nix for daily work.","tags":["maren","preference"],"depth":1},{"id":"e2","text":"Karen prefers Nix for daily work.","tags":["karen","preference"],"depth":1},{"id":"e3","text":"Maren also likes Docker Compose in some situations.","tags":["maren","preference"],"depth":2},{"id":"e4","text":"The team discussed Nix and Docker Compose during planning.","tags":["team","planning"],"depth":3},{"id":"e5","text":"Maren wrote a migration note about deployment safety.","tags":["maren","deployment"],"depth":3}],"relevant_ids":["e1"],"notes":"Entity swap with near-name collision and shared preference value."}
{"id":"time-001","query":"When did we migrate auth to bearer tokens?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We migrate auth to bearer tokens in March.","tags":["timeline","migrate-auth-to-bearer-tokens"],"depth":1,"timestamp":"2026-03-03"},{"id":"e2","text":"We migrate auth to bearer tokens in May.","tags":["timeline","migrate-auth-to-bearer-tokens"],"depth":1,"timestamp":"2026-05-04"},{"id":"e3","text":"We discussed how to migrate auth to bearer tokens throughout March planning.","tags":["planning","migrate-auth-to-bearer-tokens"],"depth":2},{"id":"e4","text":"We completed documentation for that change in May.","tags":["docs","migrate-auth-to-bearer-tokens"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-002","query":"When did we split staging and production domains?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We split staging and production domains in April.","tags":["timeline","split-staging-and-production-domains"],"depth":1,"timestamp":"2026-04-03"},{"id":"e2","text":"We split staging and production domains in June.","tags":["timeline","split-staging-and-production-domains"],"depth":1,"timestamp":"2026-06-04"},{"id":"e3","text":"We discussed how to split staging and production domains throughout April planning.","tags":["planning","split-staging-and-production-domains"],"depth":2},{"id":"e4","text":"We completed documentation for that change in June.","tags":["docs","split-staging-and-production-domains"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-003","query":"When did we move Redis into a private subnet?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We move Redis into a private subnet in January.","tags":["timeline","move-redis-into-a-private-subnet"],"depth":1,"timestamp":"2026-01-03"},{"id":"e2","text":"We move Redis into a private subnet in February.","tags":["timeline","move-redis-into-a-private-subnet"],"depth":1,"timestamp":"2026-02-04"},{"id":"e3","text":"We discussed how to move Redis into a private subnet throughout January planning.","tags":["planning","move-redis-into-a-private-subnet"],"depth":2},{"id":"e4","text":"We completed documentation for that change in February.","tags":["docs","move-redis-into-a-private-subnet"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-004","query":"When did we ship the reporting dashboard?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We ship the reporting dashboard in July.","tags":["timeline","ship-the-reporting-dashboard"],"depth":1,"timestamp":"2026-07-03"},{"id":"e2","text":"We ship the reporting dashboard in August.","tags":["timeline","ship-the-reporting-dashboard"],"depth":1,"timestamp":"2026-08-04"},{"id":"e3","text":"We discussed how to ship the reporting dashboard throughout July planning.","tags":["planning","ship-the-reporting-dashboard"],"depth":2},{"id":"e4","text":"We completed documentation for that change in August.","tags":["docs","ship-the-reporting-dashboard"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-005","query":"When did we enable GPU inference in Docker?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We enable GPU inference in Docker in September.","tags":["timeline","enable-gpu-inference-in-docker"],"depth":1,"timestamp":"2026-09-03"},{"id":"e2","text":"We enable GPU inference in Docker in October.","tags":["timeline","enable-gpu-inference-in-docker"],"depth":1,"timestamp":"2026-10-04"},{"id":"e3","text":"We discussed how to enable GPU inference in Docker throughout September planning.","tags":["planning","enable-gpu-inference-in-docker"],"depth":2},{"id":"e4","text":"We completed documentation for that change in October.","tags":["docs","enable-gpu-inference-in-docker"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-006","query":"When did we rotate the SES credentials?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We rotate the SES credentials in November.","tags":["timeline","rotate-the-ses-credentials"],"depth":1,"timestamp":"2026-11-03"},{"id":"e2","text":"We rotate the SES credentials in December.","tags":["timeline","rotate-the-ses-credentials"],"depth":1,"timestamp":"2026-12-04"},{"id":"e3","text":"We discussed how to rotate the SES credentials throughout November planning.","tags":["planning","rotate-the-ses-credentials"],"depth":2},{"id":"e4","text":"We completed documentation for that change in December.","tags":["docs","rotate-the-ses-credentials"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-007","query":"When did we switch the default embedded model to bge-small?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We switch the default embedded model to bge-small in February.","tags":["timeline","switch-the-default-embedded-model-to-bge-small"],"depth":1,"timestamp":"2026-02-03"},{"id":"e2","text":"We switch the default embedded model to bge-small in April.","tags":["timeline","switch-the-default-embedded-model-to-bge-small"],"depth":1,"timestamp":"2026-04-04"},{"id":"e3","text":"We discussed how to switch the default embedded model to bge-small throughout February planning.","tags":["planning","switch-the-default-embedded-model-to-bge-small"],"depth":2},{"id":"e4","text":"We completed documentation for that change in April.","tags":["docs","switch-the-default-embedded-model-to-bge-small"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-008","query":"When did we publish the public GHCR image?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We publish the public GHCR image in May.","tags":["timeline","publish-the-public-ghcr-image"],"depth":1,"timestamp":"2026-05-03"},{"id":"e2","text":"We publish the public GHCR image in July.","tags":["timeline","publish-the-public-ghcr-image"],"depth":1,"timestamp":"2026-07-04"},{"id":"e3","text":"We discussed how to publish the public GHCR image throughout May planning.","tags":["planning","publish-the-public-ghcr-image"],"depth":2},{"id":"e4","text":"We completed documentation for that change in July.","tags":["docs","publish-the-public-ghcr-image"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-009","query":"When did we replace the handwritten MCP server?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We replace the handwritten MCP server in June.","tags":["timeline","replace-the-handwritten-mcp-server"],"depth":1,"timestamp":"2026-06-03"},{"id":"e2","text":"We replace the handwritten MCP server in August.","tags":["timeline","replace-the-handwritten-mcp-server"],"depth":1,"timestamp":"2026-08-04"},{"id":"e3","text":"We discussed how to replace the handwritten MCP server throughout June planning.","tags":["planning","replace-the-handwritten-mcp-server"],"depth":2},{"id":"e4","text":"We completed documentation for that change in August.","tags":["docs","replace-the-handwritten-mcp-server"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-010","query":"When did we introduce depth-aware ranking?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We introduce depth-aware ranking in October.","tags":["timeline","introduce-depth-aware-ranking"],"depth":1,"timestamp":"2026-10-03"},{"id":"e2","text":"We introduce depth-aware ranking in December.","tags":["timeline","introduce-depth-aware-ranking"],"depth":1,"timestamp":"2026-12-04"},{"id":"e3","text":"We discussed how to introduce depth-aware ranking throughout October planning.","tags":["planning","introduce-depth-aware-ranking"],"depth":2},{"id":"e4","text":"We completed documentation for that change in December.","tags":["docs","introduce-depth-aware-ranking"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-011","query":"When did we remove the TUI surface?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We remove the TUI surface in January.","tags":["timeline","remove-the-tui-surface"],"depth":1,"timestamp":"2026-01-03"},{"id":"e2","text":"We remove the TUI surface in March.","tags":["timeline","remove-the-tui-surface"],"depth":1,"timestamp":"2026-03-04"},{"id":"e3","text":"We discussed how to remove the TUI surface throughout January planning.","tags":["planning","remove-the-tui-surface"],"depth":2},{"id":"e4","text":"We completed documentation for that change in March.","tags":["docs","remove-the-tui-surface"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"time-012","query":"When did we generalize the tagger pipeline?","adversary_type":"time_swap","entries":[{"id":"e1","text":"We generalize the tagger pipeline in April.","tags":["timeline","generalize-the-tagger-pipeline"],"depth":1,"timestamp":"2026-04-03"},{"id":"e2","text":"We generalize the tagger pipeline in September.","tags":["timeline","generalize-the-tagger-pipeline"],"depth":1,"timestamp":"2026-09-04"},{"id":"e3","text":"We discussed how to generalize the tagger pipeline throughout April planning.","tags":["planning","generalize-the-tagger-pipeline"],"depth":2},{"id":"e4","text":"We completed documentation for that change in September.","tags":["docs","generalize-the-tagger-pipeline"],"depth":2}],"relevant_ids":["e1"],"notes":"Same event with swapped month distractor."}
{"id":"state-001","query":"What is the current production domain?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current production domain is ecue.ai.","tags":["current-production-domain","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current production domain used to be hifidelityai.com.","tags":["current-production-domain","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is preview.ecue.ai.","tags":["current-production-domain","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current production domain.","tags":["current-production-domain","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-002","query":"What is the default embed model?","adversary_type":"state_update","entries":[{"id":"e1","text":"The default embed model is bge-small-en-v1.5.","tags":["default-embed-model","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The default embed model used to be all-MiniLM-L6-v2.","tags":["default-embed-model","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is bge-base-en-v1.5.","tags":["default-embed-model","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the default embed model.","tags":["default-embed-model","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-003","query":"What is the current staging database?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current staging database is db-staging.internal.","tags":["current-staging-database","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current staging database used to be db-old-staging.internal.","tags":["current-staging-database","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is db-preview.internal.","tags":["current-staging-database","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current staging database.","tags":["current-staging-database","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-004","query":"What is the current metrics backend?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current metrics backend is VictoriaMetrics.","tags":["current-metrics-backend","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current metrics backend used to be Prometheus.","tags":["current-metrics-backend","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is InfluxDB.","tags":["current-metrics-backend","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current metrics backend.","tags":["current-metrics-backend","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-005","query":"What is the current mail sender?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current mail sender is ses-prod.","tags":["current-mail-sender","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current mail sender used to be ses-old.","tags":["current-mail-sender","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is ses-preview.","tags":["current-mail-sender","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current mail sender.","tags":["current-mail-sender","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-006","query":"What is the current OpenCode MCP name?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current OpenCode MCP name is tagmem.","tags":["current-opencode-mcp-name","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current OpenCode MCP name used to be tagmem_active.","tags":["current-opencode-mcp-name","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is mempalace_active.","tags":["current-opencode-mcp-name","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current OpenCode MCP name.","tags":["current-opencode-mcp-name","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-007","query":"What is the current published image?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current published image is ghcr.io/codysnider/tagmem.","tags":["current-published-image","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current published image used to be ghcr.io/codysnider/tagmem-opencode.","tags":["current-published-image","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is ghcr.io/codysnider/tagmem-preview.","tags":["current-published-image","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current published image.","tags":["current-published-image","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-008","query":"What is the current local data root?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current local data root is $HOME/.local/share/tagmem.","tags":["current-local-data-root","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current local data root used to be /data/tagmem.","tags":["current-local-data-root","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is /srv/tagmem.","tags":["current-local-data-root","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current local data root.","tags":["current-local-data-root","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-009","query":"What is the current vector backend?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current vector backend is chromem-go.","tags":["current-vector-backend","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current vector backend used to be ChromaDB.","tags":["current-vector-backend","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is SQLite FTS.","tags":["current-vector-backend","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current vector backend.","tags":["current-vector-backend","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"state-010","query":"What is the current graph package name?","adversary_type":"state_update","entries":[{"id":"e1","text":"The current graph package name is taggraph.","tags":["current-graph-package-name","current"],"depth":0,"timestamp":"2026-04-01"},{"id":"e2","text":"The current graph package name used to be topicgraph.","tags":["current-graph-package-name","historical"],"depth":2,"timestamp":"2025-10-01"},{"id":"e3","text":"The staging or preview equivalent is memorygraph.","tags":["current-graph-package-name","preview"],"depth":2,"timestamp":"2026-04-01"},{"id":"e4","text":"We updated the runbook after changing the current graph package name.","tags":["current-graph-package-name","runbook"],"depth":3}],"relevant_ids":["e1"],"notes":"Current fact vs stale fact and sibling environment distractor."}
{"id":"speaker-001","query":"What did you suggest for Terraform environments?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested separate Terraform states for shared, production, and staging.","tags":["terraform-environments","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested one Terraform state with workspaces.","tags":["terraform-environments","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed Terraform environments implementation details later.","tags":["terraform-environments","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about Terraform environments.","tags":["terraform-environments","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-002","query":"What did you suggest for tagging pipeline?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested use deterministic extraction first and embedding ranking second.","tags":["tagging-pipeline","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested let the model invent tags directly.","tags":["tagging-pipeline","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed tagging pipeline implementation details later.","tags":["tagging-pipeline","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about tagging pipeline.","tags":["tagging-pipeline","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-003","query":"What did you suggest for OpenCode integration?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested run the image directly with the mcp subcommand.","tags":["opencode-integration","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested wrap everything in a shell pipeline.","tags":["opencode-integration","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed OpenCode integration implementation details later.","tags":["opencode-integration","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about OpenCode integration.","tags":["opencode-integration","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-004","query":"What did you suggest for release packaging?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested publish ghcr.io/codysnider/tagmem as the generic image.","tags":["release-packaging","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested ship only a local Docker build.","tags":["release-packaging","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed release packaging implementation details later.","tags":["release-packaging","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about release packaging.","tags":["release-packaging","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-005","query":"What did you suggest for depth model?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested treat depth as a secondary ranking bias.","tags":["depth-model","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested replace tags with rigid hierarchical folders.","tags":["depth-model","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed depth model implementation details later.","tags":["depth-model","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about depth model.","tags":["depth-model","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-006","query":"What did you suggest for README benchmarks?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested keep a compact benchmark table in the main README.","tags":["readme-benchmarks","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested put the full benchmark suite in the top section.","tags":["readme-benchmarks","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed README benchmarks implementation details later.","tags":["readme-benchmarks","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about README benchmarks.","tags":["readme-benchmarks","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-007","query":"What did you suggest for Docker data root?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested use HOME-local defaults with an env override.","tags":["docker-data-root","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested hardcode everything to /data/tagmem.","tags":["docker-data-root","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed Docker data root implementation details later.","tags":["docker-data-root","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about Docker data root.","tags":["docker-data-root","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-008","query":"What did you suggest for MCP compatibility?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested use the official Go SDK.","tags":["mcp-compatibility","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested hand-roll every transport detail.","tags":["mcp-compatibility","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed MCP compatibility implementation details later.","tags":["mcp-compatibility","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about MCP compatibility.","tags":["mcp-compatibility","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-009","query":"What did you suggest for adversarial benchmark repo?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested split it into a standalone project.","tags":["adversarial-benchmark-repo","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested bury it inside the main app repo.","tags":["adversarial-benchmark-repo","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed adversarial benchmark repo implementation details later.","tags":["adversarial-benchmark-repo","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about adversarial benchmark repo.","tags":["adversarial-benchmark-repo","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"speaker-010","query":"What did you suggest for OpenCode command naming?","adversary_type":"speaker_swap","entries":[{"id":"e1","text":"You suggested use remember instead of mine.","tags":["opencode-command-naming","assistant","suggestion"],"depth":1,"speaker":"assistant"},{"id":"e2","text":"I suggested keep mine because users will figure it out.","tags":["opencode-command-naming","user","suggestion"],"depth":1,"speaker":"user"},{"id":"e3","text":"We discussed OpenCode command naming implementation details later.","tags":["opencode-command-naming","discussion"],"depth":2},{"id":"e4","text":"The team wrote follow-up notes about OpenCode command naming.","tags":["opencode-command-naming","notes"],"depth":3}],"relevant_ids":["e1"],"notes":"Assistant/user suggestion swap with same subject area."}
{"id":"paraphrase-001","query":"What timeout do API calls use?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"API calls time out after 30 seconds.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The API timeout is 60 seconds.","tags":["config","limits"],"depth":1},{"id":"e3","text":"Background jobs retry for up to 30 seconds.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: API calls time out after 30 seconds.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-002","query":"How long do production cookies last?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"Production cookies expire after 12 hours.","tags":["config","limits"],"depth":1},{"id":"e2","text":"Production cookies expire after 24 hours.","tags":["config","limits"],"depth":1},{"id":"e3","text":"Staging cookies expire after 12 hours.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: Production cookies expire after 12 hours.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-003","query":"What is the upload limit?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The upload limit is 25 megabytes.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The upload limit is 50 megabytes.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The attachment limit is 25 megabytes.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The upload limit is 25 megabytes.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-004","query":"How often does auth refresh run?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"Auth refresh runs every 10 minutes.","tags":["config","limits"],"depth":1},{"id":"e2","text":"Auth refresh runs every 15 minutes.","tags":["config","limits"],"depth":1},{"id":"e3","text":"Metrics scraping runs every 10 minutes.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: Auth refresh runs every 10 minutes.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-005","query":"When does the reporting batch run?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The reporting batch runs at 02:00 UTC.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The reporting batch runs at 03:00 UTC.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The cleanup batch runs at 02:00 UTC.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The reporting batch runs at 02:00 UTC.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-006","query":"What port does the public API use?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The public API port is 8443.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The public API port is 9443.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The internal admin port is 8443.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The public API port is 8443.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-007","query":"What is the Docker data root default?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The Docker data root defaults to HOME-local storage.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The Docker data root defaults to /data/tagmem.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The benchmark root defaults to HOME-local storage.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The Docker data root defaults to HOME-local storage.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-008","query":"What prefix do the MCP tools use?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The MCP tools use the tagmem_ prefix.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The MCP tools use the tiered_memory_ prefix.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The CLI binary is named tagmem.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The MCP tools use the tagmem_ prefix.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-009","query":"What is the default GPU model?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The default GPU model is bge-small-en-v1.5.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The default GPU model is bge-base-en-v1.5.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The CPU fallback model is all-MiniLM-L6-v2.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The default GPU model is bge-small-en-v1.5.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-010","query":"What is the runtime image name?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The runtime image is ghcr.io/codysnider/tagmem.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The runtime image is ghcr.io/codysnider/tagmem-opencode.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The repo path is github.com/codysnider/tagmem.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The runtime image is ghcr.io/codysnider/tagmem.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-011","query":"How is the MCP server implemented?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The MCP server is implemented with the official Go SDK.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The MCP server is still handwritten.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The transport runs over stdio.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The MCP server is implemented with the official Go SDK.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}
{"id":"paraphrase-012","query":"What is the graph package name?","adversary_type":"near_duplicate_paraphrase","entries":[{"id":"e1","text":"The local graph package is named taggraph.","tags":["config","limits"],"depth":1},{"id":"e2","text":"The local graph package is named topicgraph.","tags":["config","limits"],"depth":1},{"id":"e3","text":"The benchmark package is named tagbench.","tags":["jobs","limits"],"depth":2},{"id":"e4","text":"We reviewed the policy related to: The local graph package is named taggraph.","tags":["policy"],"depth":3}],"relevant_ids":["e1"],"notes":"Near-duplicate paraphrase with one wrong value distractor."}