Supported Outcome Settlement support ledger and observation profile

[flyingrobots]

Goal

Lock Supported Outcome Settlement into Continuum as the cross-runtime support/admissibility doctrine.

Canonical doc: docs/explanation/supported-outcome-settlement.md.

Thesis

Continuum checks support for a claim, purpose, and context. It derives admissible observations. It does not create native consequence.

The model is:

outcome kind x support tier

Scope

Extend the protocol/profile planning so Continuum can carry and check support for:

• completed outcomes;
• repairable obstructions;
• authority blocks;
• underdetermined support;
• disputed support;
• invalid proposals;
• repair candidates derived from obstruction.

The support tier ladder is:

tier0_agent_assertion
tier1_signed_receipt_shell
tier2_history_inclusion
tier3_holographic_support_ledger
tier4_native_hologram_verification
tier4_5_challenge_replay
tier5_proof_carrying_hologram_verification

Tier 3 is the buildable default. Tier 5 is future/high-assurance only.

Supersedes / refines

• Extends Goalpost: Continuum protocol observation evidence and capability proofs #59 with explicit outcome-kind/support-tier posture.
• Refines Continuum Contract Artifact Interchange #72: contract artifact interchange must carry supported outcomes, not just artifact identity.
• Refines protocol profile wording around counterfactuals: the broad debugger surface is a strand neighborhood; counterfactual remains legal but unselected.

Acceptance criteria

• continuum.observation.v1 planning can represent completed, obstructed, repairable, authority-blocked, underdetermined, disputed, and invalid observations.
• Support ledger atoms can disclose tier used, verification mode, guarantees, and non-guarantees.
• The docs distinguish receipt shell, support ledger, admissible observation, and native settlement.
• WARP TTD/neighborhood vocabulary distinguishes actuals, legal unselected counterfactuals, obstructed attempts, repair candidates, and invalid proposals.
• No v1 profile requires proof-carrying execution as the baseline.

Milestone

Continuum Protocol - Observation Evidence And Capability Proofs.

[coderabbitai]

🔗 Related PRs

#18 - Align Continuum sibling runtime doctrine [closed]
#20 - Rewrite README around witnessed causal history [closed]
#71 - Add Observer API contract and core package [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!