Slice: Stabilize contract obstruction taxonomy for Jim #629

Activity

1. flyingrobots

   added this to the v0.1.0 - Jim Evidence Gate milestone on Jun 29, 2026
2. coderabbitai commented on Jun 29, 2026

   

   coderabbitaibot

   on Jun 29, 2026 – with coderabbitai

   Contributor

   More actions

   🔗 Related PRs

   #335 - feat(core): add authority policy obstruction vocabulary [merged]
   #358 - feat(core): add admission evidence boundaries [merged]
   #365 - feat(wesley): emit query observer host helpers [merged]
   #371 - feat(core): advance v0.1 contract evidence and retention [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!
3. coderabbitai

   added

   lane:releaseMethod lane release.Method lane release.

   legend:platformMethod legend platform.Method legend platform.

   legend:releaseMethod legend release.Method legend release.

   legend:testMethod legend test.Method legend test.

   release:echo-1.0Echo 1.0 release convergence scopeEcho 1.0 release convergence scope

   type:maintenanceMethod work type maintenance.Method work type maintenance.

   runtimeRuntime coreRuntime core

   specSpec/Design documentSpec/Design document

   on Jun 29, 2026
4. flyingrobots commented on Jul 4, 2026

   

   flyingrobots

   on Jul 4, 2026 – with ChatGPT Codex Connector

   OwnerAuthor

   More actions

   Refined by #640.

   The Jim obstruction taxonomy should support Supported Outcome Settlement outcomes. In particular, stale basis should be representable as witnessed non-application and, when repair metadata exists, repairable obstruction. Broad runtime errors, terminal obstructions, scheduler rejections, and faults should remain distinct.