{
  "schema_version": "1.3.0",
  "slug": "what-distinguishes-legible-to-principal-behavior-from-legible-to-peer-behavior",
  "title": "What distinguishes legible-to-principal behavior from legible-to-peer behavior?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session is observed by both principal and peers, their legibility requirements differ, and behavior is visible to both. * **Does not apply when:** The session is observed by one audience only, or the two audiences re",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-distinguishes-legible-to-principal-behavior-from-legible-to-peer-behavior.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-distinguishes-legible-to-principal-behavior-from-legible-to-peer-behavior.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-distinguishes-legible-to-principal-behavior-from-legible-to-peer-behavior.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1035,
    "python_slice_tokens": 288,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **principal legibility** (the principal can understand why the session acted, what tradeoffs it made, and whether it acted within authority) and **peer legibility** (peers can predict the session's behavior well enough to coordinate reliably). Relying on one form of legibility creates the **Audience Confusion**: the session optimizes f...",
    "what_was_observed": "In multi-audience agent architectures, failing to distinguish legibility modes produces three primary failure modes: 1. **Opaque-to-Principal Predictable-to-Peers:** The session behaves in ways that peers understand (matching protocol conventions, following common patterns) but its principal cannot audit—the behavior is correct but inscrutable from the principal's perspective. 2. **Auditable-to-Principal Opaque-to-Pe...",
    "condition_of_validity": "* **Applies when:** The session is observed by both principal and peers, their legibility requirements differ, and behavior is visible to both. * **Does not apply when:** The session is observed by one audience only, or the two audiences require identical legibility.",
    "decision_boundary": "1. **Is the session observed by both principal and peers?** If no, single-audience legibility applies. If yes, proceed. 2. **Do principal and peer legibility requirements differ?** If no, single legibility mode suffices. If yes, dual-mode operation is required. 3. **Is the `audience-separation-receipt` present for actions visible to both?** If yes, each audi...",
    "operational_effect": "1. **Principal Audit Integrity:** The principal can audit fully without peer protocols interfering. 2. **Peer Coordination Integrity:** Peers can coordinate using stable patterns without principal-audit noise. 3. **Conflict Awareness:** Audience conflicts are detected and resolved principledly."
  },
  "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": "d85de0b719d2f97e3fa24985ce53cf963051acbd79cba53e2416174e0b848148",
    "verified_classes": [
      "LegibilityVerdict",
      "AudienceRequirements",
      "SessionAction",
      "LegibilityPolicy",
      "LegibilityManifest",
      "AudienceLegibilityGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_action"
    ],
    "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
  }
}