Skip to content

Gate E - jedit Native Operation Proof #143

Description

@flyingrobots

Contract

jedit proves designated product operations through the Continuum/Echo/Edict path rather than a direct bespoke execution path.

Owner

Canonical repository: flyingrobots/jedit.

Executable check

TBD: run the jedit native operation proof against pinned Echo and Edict commits.

Required evidence

  • Designated jedit operation set.
  • Edict compilation of each designated operation.
  • Echo admission and invocation evidence.
  • End-to-end trace: authored operation -> bundle -> admission -> invocation -> Echo mutation.
  • Negative proof that the old direct bypass cannot execute.

Negative cases

  • Direct jedit execution path cannot satisfy this gate.
  • Missing Edict admission must block invocation.
  • Old bypass route must be removed or unreachable.

Compatibility set

Pinned jedit commit, Echo commit, Edict commit, operation set, bundle digests, admission receipts, invocation receipts, and trace digest.

Pass rule

The jedit proof returns pass/fail and links the end-to-end trace plus old-bypass negative test evidence.

Activity

  1. flyingrobots commented on Aug 15, 2026

    @flyingrobots
    OwnerAuthor

    Reconciliation update, 2026-08-15:

    Jim's current production text corridor is real Echo authority but still uses the transitional GraphQL/Wesley contract-host route. Hello Echo's current main passes its pure runtime, bounded observation, and validated patch suites against current Edict and Echo heads in a disposable local probe, so the generic substrate is available; Jim consumer adoption remains unproven.

    #295 now owns the P0 migration goalpost. Its slices are #296, #297, and #298. This Gate E remains the closure authority: it must pass only when the designated Jim operation set runs from authored Edict through verified Echo execution and the compatibility/bypass routes fail negative tests. #283 owns the machine-readable evidence artifact.

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

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions