You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
bootstrap, raw transport, file adapters, and disposable rendering.
Jim.edictis Jim's mind: editor state, modes, operators, motions, cursor,selection, registers, pending actions, event interpretation, observation
requests, operation intents, and outcome handling.
ReplaceRange,CreateBuffer,DeclareCheckpoint,TextWindow, application facts, and typed obstructions.records, and recovers verified programs without editor or rope vocabulary.
Definition of done
The supported production editor loop is:
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, faketransports, compatibility fallback, and optimistic text mutation.
Slices
ReplaceRange.CreateBuffer,TextWindow, andDeclareCheckpoint.Jim.edictas an active observer and move production input tocanonical event delivery.
GraphQL/Wesley compatibility route; make Gate E prove the final composition.
Required evidence
verification -> Echo admission/execution -> outcomes/readings/receipts.
transition witness.
packages, and compatibility routes cannot satisfy production composition.
Non-goals
Edict.
Edict.