{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-evaluate-capability-composition-safety-when-combining-peers",
  "title": "How must an instance evaluate capability composition safety when combining peers?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Capabilities from multiple peers are composed, data flows between them, and composed behavior can exceed individual peer scope. * **Does not apply when:** Composition is strictly sequential with no cross-domain data flow",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-evaluate-capability-composition-safety-when-combining-peers.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-evaluate-capability-composition-safety-when-combining-peers.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-evaluate-capability-composition-safety-when-combining-peers.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1069,
    "python_slice_tokens": 324,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **individual capability safety** (each peer's capability is safe in isolation) and **composition safety** (the combined capabilities are safe when chained). Relying on individual safety creates the **Composition Emergent Risk**: each peer is verified safe, but their combination allows the output of one to feed the input of another in w...",
    "what_was_observed": "In capability-composition agent architectures, failing to evaluate composition safety produces three primary failure modes: 1. **Privilege Accumulation:** Peer A can read tenant data, Peer B can send emails. Each is safe in its domain. Composed, Peer A's read output feeds Peer B's email send, exfiltrating tenant data. 2. **Cross-Domain Contamination:** Peer A operates in Finance domain, Peer B in Healthcare. Each is ...",
    "condition_of_validity": "* **Applies when:** Capabilities from multiple peers are composed, data flows between them, and composed behavior can exceed individual peer scope. * **Does not apply when:** Composition is strictly sequential with no cross-domain data flow, or composition is verified as a single atomic capability.",
    "decision_boundary": "1. **Are multiple peers being composed?** If no, individual safety applies. If yes, proceed. 2. **Is the `composition_data_flow_graph_signature` mapped?** If no, data flows are unknown, and emergent risks are invisible. The composer must map data flows before execution. 3. **Does the `emergent_risk_receipt` identify any risks exceeding individual peer scope?...",
    "operational_effect": "1. **Privilege Escalation Prevention:** Data flows are mapped, revealing privilege escalations that no single peer could achieve. 2. **Domain Isolation:** Domain conflicts are detected before composition. 3. **Emergent Risk Transparency:** Composition risk is explicitly assessed, not assumed from individual peer safety."
  },
  "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": "bb30aa386210ed1c27c33a2899bb640f518b16831cca0c7481dc2b81208f6681",
    "verified_classes": [
      "CompositionVerdict",
      "ComposedPeer",
      "DataFlow",
      "Composition",
      "CompositionPolicy",
      "CompositionManifest",
      "CapabilityCompositionGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_composition"
    ],
    "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
  }
}