54378c7355f20cdad76ea1b50f646bbfe2b85f6c
El SDK CI - dev / build-and-test (pull_request) Successful in 6m57s
Drop the bilingual-string-table framing and the external-encoder plan (both wrong). Translation now routes source-lexicon -> concept-frame (language- invariant, in the engram concept geometry) -> target-realizer, exactly as the ELP was designed: a word resolves to the CONCEPT it denotes via its own language's lexicon (a monolingual step — the engram nearest-region ranker only disambiguates senses within one language, so an English-trained embedder is fine and never compares 'ocean'~'oceano' as strings). The concept node is the shared pivot; its manifold location is the meaning. - Pronouns route through the NATIVE concept pivot (cp_pron_concept -> cp_rom_pron_surface) instead of an ad-hoc EN->tgt string map. - lemma_for_concept / noun_for_concept are each target language's own CONCEPT->SURFACE lexicon (the mirror of comprehend's SURFACE->CONCEPT). - Fidelity is concept-preservation (concept_frame fingerprint), not string cosine against an external multilingual model. - Plural article agreement fixed (las/los, as/os). Verified: 'You never fought the ocean.' -> ES 'Usted nunca luchó el océano.' concept-frame pivot 'pred=fight patient=ocean pol=neg' realizes to ES+PT from one parse; nunca holds 3/3. Gaps unchanged: PT verb conjugation fallback, adjunct/subordinator concepts not yet in-frame.
Description
The Engram programming language — types as knowledge nodes, quantum-sealed prod target
199 MiB
Releases
5
El SDK (latest)
Latest
Languages
Emacs Lisp
95.1%
C
3.9%
HTML
0.3%
Python
0.2%
Shell
0.2%
Other
0.1%