Skip to content

Goalpost: Run Jim.edict as an Echo-realized active observer #295

Description

@flyingrobots

Priority

P0. Do not schedule broad Vim parity or book-derived runtime work ahead of this
goalpost.

Current truth

Jedit's Wesley/Rust compatibility corridor is genuinely Echo-backed, but it is
not the final application architecture. TypeScript and native Rust still
interpret Jim requests and directly choose operations.

The final application is Jim authored in Edict and realized by Echo:

  • Jedit/Bijou/native code is Jim's I/O body: canonical event decoding,
    bootstrap, raw transport, file adapters, and disposable rendering.
  • Jim.edict is Jim's mind: editor state, modes, operators, motions, cursor,
    selection, registers, pending actions, event interpretation, observation
    requests, operation intents, and outcome handling.
  • Jim-owned Edict lawpacks define ReplaceRange, CreateBuffer,
    DeclareCheckpoint, TextWindow, application facts, and typed obstructions.
  • Edict checks, lowers, packages, and independently verifies those sources.
  • Echo generically installs, admits, budgets, schedules, interprets, commits,
    records, and recovers verified programs without editor or rope vocabulary.

Definition of done

The supported production editor loop is:

canonical KeyEvent
-> Echo delivers the event to installed Jim.edict at J0
-> Jim.edict requests a basis-bound TextWindow reading
-> Jim.edict derives any application intent from Jim state
-> Echo interprets the compiler-produced generic program
-> Echo commits one Tick or returns one typed obstruction
-> Jim.edict handles the outcome and advances J0 to J1
-> Jedit renders a disposable projection

Every supported operation originates in checked-in Jim-owned Edict source,
crosses Edict's public application-build boundary, is independently verified,
and runs through Echo's generic runtime authority. Generated clients are codecs
and transport stubs only.

Production rejects frontend command-to-operation mapping, handwritten
packages, native Jim callbacks, caller-authored patches, MutationPlan, fake
transports, compatibility fallback, and optimistic text mutation.

Slices

Required evidence

  • Exact Jedit, Edict, and Echo commits and generated artifact digests.
  • Authored Edict source -> Core/Target IR -> compiler package -> independent
    verification -> Echo admission/execution -> outcomes/readings/receipts.
  • A real active-observer event, reading, child-operation, outcome, and Jim-state
    transition witness.
  • Restart recovery from Echo-owned durable history.
  • Negative guards proving semantic TypeScript, native callbacks, handwritten
    packages, and compatibility routes cannot satisfy production composition.
  • Gate E (Gate E - jedit Native Operation Proof #143) emits the Emit a machine-readable authority-gate evidence manifest #283 machine-readable evidence manifest.

Non-goals

  • No application vocabulary or rope intrinsic in Echo.
  • No ambient filesystem, process, network, Git, GitHub, or model authority in
    Edict.
  • No local text authority or optimistic UI mutation.
  • No claim that a direct generated-client operation harness rewrites Jim in
    Edict.

Metadata

Metadata

Assignees

No one assigned

    Labels

    causal-ropeCausal rope text authority roadmapenhancementNew feature or requestgoalpostRoadmap milestone trackertext-authorityText authority and storage invariantswork-in-progressCycle or PR is intentionally in progress and not ready to merge

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions