Skip to content

Goalpost: WF-0108A :why observation evidence #181

Description

@flyingrobots

Goalpost

Make :why the product-facing witness that explains the last meaningful command and names the observer coordinate, evidence posture, Echo reading envelope status, retained evidence posture, and replay availability.

Slices

Done When

  • :why human output explains command, target, result, receipt, and evidence posture.
  • JSON witness exposes command facts plus observer-coordinate/evidence facts without terminal scraping.
  • Local-only evidence is labeled local-only and never upgraded to Echo or Continuum-native evidence.
  • At least one golden dw path consumes real Echo ReadingEnvelope identity.
  • WF-0108 command set expands to dw, dd, ciw, and gUap after the golden path is stable.

Coordination

Cross-repo dependencies: Echo v0.1.0 - Jim Evidence Gate; Continuum Continuum Protocol - Observation Evidence And Capability Proofs for portable protocol/profile vocabulary only; Jim remains an Echo app and Jim/Echo integration does not go through Continuum.

This issue is the repo-local goalpost for the Jim/Echo/Continuum :why observation-evidence roadmap.

WF-0106 Supporting Packet

WF-0106 is tracked in #192 and milestone https://github.com/flyingrobots/jedit/milestone/3. It is Jim-owned product work around command catalog, describe-key, causal register history, semantic macros, buffer/mode reports, diagnostics buffers, debug traces, and host-operation previews. It supports :why and the golden loop, but it does not change the WF-0108A requirement that command provenance/evidence must be honest first.

Activity

  1. coderabbitai commented on Jun 29, 2026

    @coderabbitai
    🔗 Related PRs

    #12 - test(stack): move fixture basis behind optic session [merged]
    #23 - feat(echo): add Echo release gate witness [merged]
    #26 - feat: report Echo witness evidence posture [merged]
    #27 - feat(echo): wire trusted runtime lifecycle into jedit [merged]
    #135 - Docs: lock Jim causal roadmap [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!

  2. flyingrobots commented on Jul 4, 2026

    @flyingrobots
    OwnerAuthor

    Supported Outcome Settlement lock-in added #201 to this milestone.

    #201 extends WF-0108A so :why distinguishes completed, repairable obstruction, authority block, underdetermined support, dispute, and invalid proposal. The key product rule: Jim may translate Echo/Continuum evidence into editor language, but must not upgrade a local-only or missing support posture into success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    cool-ideas™Speculative high-leverage ideas worth exploringenhancementNew feature or request

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions