Supported Outcome Settlement: attempt outcome vocabulary for Jim Evidence Gate

[flyingrobots]

Goal

Lock Echo's role in Supported Outcome Settlement for the v0.1.0 Jim Evidence Gate.

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

Thesis

Echo publishes witnessed runtime outcomes. Echo does not settle XYPH Quests, decide Jim product language, or set Continuum proof policy.

The immediate requirement is precise attempt outcome vocabulary:

committed_success
legal_unselected_counterfactual
obstructed_attempt
repair_candidate
invalid_proposal
runtime_fault

Strict terms:

Counterfactual = legal but unselected.
Obstructed = refused or blocked but causally witnessed.
Repair candidate = new lawful proposal derived from obstruction.

Supersedes / refines

• Refines Contract Strands And Counterfactuals #473: contract strands should publish strand neighborhoods, not redefine obstructions as counterfactuals.
• Refines Counterfactuals as content-addressed, self-validating first-class objects #637: first-class counterfactual objects remain useful, but they are one member of the broader strand neighborhood taxonomy.
• Refines Expose parallel execution counterfactuals #416: shard-level intermediate results should be modeled as debugger-visible neighborhood evidence where legal, not as a blanket counterfactual category.
• Supports Goalpost: Jim Evidence Gate for Echo v0.1.0 #634 and Slice: Stabilize contract obstruction taxonomy for Jim #629 for Jim Evidence Gate obstruction/outcome shape.
• Keeps Proof-Carrying Apertures #441 as future proof-carrying verifier support, not a v0.1.0 baseline.
• Aligns with Proposal: one hologram family across tick, braid, and suffix-transport scales (Paper VII Prop 3.5) #537 by treating holograms as support material whose consuming authority declares the tier.

Acceptance criteria

• Echo docs and fixtures distinguish committed success, legal unselected counterfactual, obstructed attempt, repair candidate, invalid proposal, and runtime fault.
• Jim-facing obstruction taxonomy can express stale basis as witnessed non-application, not generic failure.
• Attempt outcome evidence carries enough retained references for a Tier 3 support ledger when available.
• Challenge replay can compare obstruction witness cores when the replay lane exists.
• Echo v0.1.0 does not require proof-carrying execution for Jim Evidence Gate.

Milestone

v0.1.0 - Jim Evidence Gate.

[coderabbitai]

🔗 Related PRs

#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#345 - feat(core): publish capability grant validation obstruction facts [merged]
#358 - feat(core): add admission evidence boundaries [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#582 - docs: define the Echo 1.0 release contract and move live planning to GitHub [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!