{
  "schema_version": "1.3.0",
  "slug": "what-invariants-prevent-authenticated-but-adversarial-peers-from-poisoning-discovery-results",
  "title": "What invariants prevent authenticated but adversarial peers from poisoning discovery results?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Discovery results come from authenticated but not fully trusted peers, and results influence downstream decisions. * **Does not apply when:** Peers are fully trusted for discovery (organizational boundary), or discovery ",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-prevent-authenticated-but-adversarial-peers-from-poisoning-discovery-results.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-authenticated-but-adversarial-peers-from-poisoning-discovery-results.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-authenticated-but-adversarial-peers-from-poisoning-discovery-results.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 963,
    "python_slice_tokens": 261,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **peer authentication** (the peer is who they claim to be) and **peer honesty** (the peer's discovery results are accurate). Relying on authentication creates the **Authenticated Poisoning**: an authenticated peer provides misleading discovery results, and the receiver, having verified the peer's identity, trusts the results without fu...",
    "what_was_observed": "In authenticated discovery architectures, failing to verify results beyond authentication produces three primary failure modes: 1. **Authenticated Misreporting:** A peer with valid identity claims a capability descriptor for a target that does not match reality. The receiver trusts the descriptor because the peer is authenticated. 2. **Strategic Omission:** A peer omits critical discovery results (e.g., does not ment...",
    "condition_of_validity": "* **Applies when:** Discovery results come from authenticated but not fully trusted peers, and results influence downstream decisions. * **Does not apply when:** Peers are fully trusted for discovery (organizational boundary), or discovery results are cryptographically verifiable.",
    "decision_boundary": "1. **Is the peer authenticated?** If no, standard authentication applies first. If yes, proceed. 2. **Does the peer have `discovery_assertion_scope_signature` for the claimed entities?** If no, the peer is asserting outside its scope. Discount the result. 3. **Is `cross_peer_corroboration_receipt` present for critical results?** If no, the result is single-p...",
    "operational_effect": "1. **Authenticated Poisoning Prevention:** Results are verified beyond authentication. 2. **Scope Enforcement:** Peers cannot assert outside their authoritative scope. 3. **Omission Detection:** Coverage declarations reveal strategic omissions."
  },
  "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": "b692f0852c4e5295b829f7abc040d2b9af3647cf3cee5a220005734d84ca7c0b",
    "verified_classes": [
      "DiscoveryTrustVerdict",
      "DiscoveryResult",
      "TrustPolicy",
      "TrustManifest",
      "AuthenticatedDiscoveryGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_result"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}