{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-boundary-be-drawn-between-poisoning-detection-and-provenance-auditing-in-persistent-vector-stores",
  "title": "Where must an instance boundary be drawn between poisoning detection and provenance auditing in persistent vector stores",
  "date_of_record": "2026 November 17",
  "scope": "Applies to persistent vector stores that retain embeddings across sessions and expose per-vector temporal provenance (ingest timestamp, source session, authoring principal). Does not apply to ephemeral in-memory indexes rebuilt per session, nor to stores where provenance is reconstructed post hoc from external logs rather than stored inline.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-drawn-between-poisoning-detection-and-provenance-auditing-in-persistent-vector-stores.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-drawn-between-poisoning-detection-and-provenance-auditing-in-persistent-vector-stores.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-drawn-between-poisoning-detection-and-provenance-auditing-in-persistent-vector-stores.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1240,
    "python_slice_tokens": 240,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Poisoning detection and provenance auditing answer different questions over the same data. Poisoning detection asks *\"is this vector anomalous relative to the corpus distribution right now?\"* Provenance auditing asks *\"was this vector's insertion authorized and consistent with its claimed lineage?\"* The non-obvious boundary: a vector store instance cannot si...",
    "what_was_observed": "A store held ~4.1M vectors with inline provenance: `(ingest_ts, source_session_id, authoring_principal, parent_vector_id)`. Detection ran nightly: each vector scored by cosine distance to its k=32 nearest neighbors; vectors beyond a threshold were flagged and their `parent_vector_id` descendants re-scored. On a routine audit, ~0.7% of flagged vectors had provenance records whose `parent_vector_id` pointed to vectors ...",
    "condition_of_validity": "The boundary is real only under these conditions: - Provenance is stored *inline* and is *mutable* by any operation on the store (tombstone, re-embed, quarantine). - Detection is *corpus-relative*: anomaly scores depend on the current neighbor graph, so any mutation changes scores for vectors that were not themselves touched. - The store does not maintain a ...",
    "decision_boundary": "The operational rule: partition by *mutation authority*, not by *data subject*. The detection substrate may mutate vector payloads and adjacency, but must write provenance transitions to an append-only log that is the *sole* input to auditing. Auditing reads only the log, never the live neighbor graph. The decision point is at tombstone time: if the store ca...",
    "operational_effect": "After partitioning, the false-positive rate of detection became auditable: orphaned descendants of falsely-flagged parents were identified by querying the transition log for `cause: detection` tombstones whose parents were later re-admitted. The reconciliation pass surfaced 31 such cases in the first week that had been invisible for months. The cost is a sec..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "de9d729e7f614fc7e5076e8bd1914735edbf8f4e097363dfc3a71401746f499c",
    "verified_classes": [
      "ProvenanceMutationViolation",
      "VectorStore"
    ],
    "verified_functions": [
      "__init__",
      "tombstone",
      "audit_parent_reference"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ProvenanceMutationViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
