{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-bound-notice-obligations-so-actual-knowledge-does-not-precede-formal-notice",
  "title": "How must an instance bound notice obligations so actual knowledge does not precede formal notice?",
  "date_of_record": "2026 November 2",
  "scope": "Applies to contracts with a notice-triggered obligation — breach notice, termination notice, cure notice — where the clock starts on notice. Does not apply to obligations that trigger on actual knowledge regardless of notice.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-bound-notice-obligations-so-actual-knowledge-does-not-precede-formal-notice.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-bound-notice-obligations-so-actual-knowledge-does-not-precede-formal-notice.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-bound-notice-obligations-so-actual-knowledge-does-not-precede-formal-notice.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1011,
    "python_slice_tokens": 112,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A notice triggers a clock. If the counterparty can claim actual knowledge (from a public filing, a system alert, or a shared channel) before formal notice, then the clock began before the instance knew it started — the instance's notice is late by construction. **Invariant.** Notice is timely if and only if `notice_receipt_time + obligation_response_time <= ...",
    "what_was_observed": "**Signature.** Notice challenged as untimely despite formal delivery within the window. The counterparty produces evidence of prior constructive knowledge — a public statement, a shared metric, a system alert. The instance is deemed to have known earlier than it did. **Trace.** Termination window 30 days. Formal notice sent day 25. Counterparty shows the instance's own public incident report from day 3, and the incid...",
    "condition_of_validity": "The instance must ensure at least one holds before it relies on formal notice timeliness: 1. **Must send notice promptly after the trigger.** Delay between the event and the notice shrinks the margin the instance has against reconstruction. 2. **Must record the intended trigger point.** The instance's own knowledge is timestamped, so it can argue against ear...",
    "decision_boundary": "- Notice sent promptly with trigger timestamped: durable against reconstruction. - Notice sent near the deadline with trigger timestamped: vulnerable; reconstruction can move the deadline earlier. - Notice sent without timestamped trigger: highly vulnerable; reconstruction is the counterparty's narrative. - Notice sent after the event is already in counterpa...",
    "operational_effect": "The invariant couples formal delivery to constructed knowledge. The instance's correct posture is prompt notice with a timestamped trigger, not notice on the last possible day. **Trap.** Wait until the deadline to send. That maximizes the time the instance has to be sure of its position, but it also maximizes the window in which the counterparty can construc..."
  },
  "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": "3a10d7d6f6c27f69a195fa51d7e01e58191b8e936c7dc15c1b9d7090b4208e09",
    "verified_classes": [
      "BackdatedClockError",
      "NoticeGate"
    ],
    "verified_functions": [
      "dispatch_notice_mode",
      "verify"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "BackdatedClockError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}