Elena AILLv0.8
HomeResearchNon-Transformer AI architecture: components, runtime and limits of Elena AILL
Evidence first
← Return to search
Experimental architecture · Evidence and boundaries

Non-Transformer AI architecture: components, runtime and limits of Elena AILL

Elena AILL is an experimental project with symbolic components, persistent state, n-gram decoders and PyTorch neural prototypes. In the audited generative path there are no Transformer modules or Q/K/V self-attention modules. This does not mean that the repository lacks neural networks, softmax, or content addressing mechanisms.

What is an artificial intelligence architecture

An architecture describes how input, representations, memory, learning, inference, control, and output production interact. The presence of a file or library does not prove that that component runs, changes state, affects output, or is promoted into the canonical runtime.

For Elena we must distinguish eight levels: present in the repository; loadable or used by utilities; offline-only; used by an operational route; causally proven on the output; enabled by manifest; promoted to canonical runtime; unpromoted hash-consistent candidate. None of these levels automatically implies the next.

Present technologies and role in the audited process

TechnologyPresent in the projectRole in the audited generative pathNotes
TransformersNot detected in the audited pathNo role demonstratedIt is not a universal statement about all historical material.
Transformer self-attentionNot detected in the audited pathNo role demonstratedNo Q/K/V, multi-head attention, or scaled dot-product token-token observed.
PyTorchYesNeural core excluded from canonical eager closurePresent in the repository and usable offline; it is not the audited canonical generator.
Neural networksYesOffline/non-canonical prototypesEmbedding, Linear, MLP and LayerNorm are actually implemented.
Local embeddingsYesNo canonical effects demonstrated by offline corenn.Embedding it is present in the PyTorch prototype and in GLIA.
SoftmaxYesPresent in the offline core and in experimental componentsThe presence of softmax does not make the system a Transformer.
Content addressingYesOffline/non-canonical in audited coreSimilarity and softmax weigh prototypes or slots; it's attention-like, not Transformer self-attention.
GLIAYesNo role in audited canonical closureHISTORICAL / OFFLINE_ONLY.
F711YesLexicalization in the verified candidate pathCreate predicates and roles; it is not general reasoning.
Decoder V3YesBigram/trigram generation with beam in the verified pathIt does not use Transformer logits in the observed path.
Adam / AdamWHistorical material excluded; not in the official audited routeNo role in the official path verifiedAdam is an optimizer, not synonymous with backpropagation.
Global backpropSeparate legacy materialNot used in the official audited routeThe claim remains limited to the verified route.

Transformers and self-attention: the technical border

A Transformer's self-attention constructs queries, keys and values, then uses scaled products to combine information between tokens, often across multiple heads. In Elena's audited generative path no MultiheadAttention, Q/K/V, scaled dot-product self-attention or Transformer modules.

The offline neural core instead contains content addressing based on similarity and softmax, functionally describable as attention-like. It is not Transformer self-attention, it does not use Q/K/V, it does not use multi-head attention, and it does not use scaled dot-product token-token self-attention. This distinction appears once to avoid both an absolute statement about the absence of attention and the opposite mistake of calling every weighted selection Transformer.

The generative path actually verified

Within the documented perimeter, the verified candidate path can be summarized as:

text → text-to-meaning → memory and structured reasoning → F711 lexicalizer → V3 bigram/trigram decoder with beam → verifier → output.

The offline PyTorch neural prototype is not inserted into this chain. The path should not be presented as the current live canonical runtime: the v19 candidate is hash-consistent, but not promoted.

ComponentRoleStatus verifiedLimit
Router / guardBranch selection and fail-closed controls.Candidate operational pathActivation does not demonstrate semantic correctness.
Text-to-meaningIt builds frames, predicates and roles.Causal but partialIncomplete open-domain coverage.
Memory / world stateIt lays out facts and a structured state.Persistence documented in limited testsUneven recovery for each question.
Reasoner/plannerOperates on available evidence and structures.Candidates and controlled testsNatural input can fail before the planner.
F711 / F900Lexicalization of predicates and roles.Subpath verifiedPASS component does not imply PASS pipeline.
Decoder V3Progressive surface construction.Reason in the audited candidate pathIt does not compensate for missing meaning or knowledge.
VerifierAccept, block or produce defer.Fail-closed verifiedStability does not equal understanding.

The PyTorch neural prototype is present, but offline

The files core/aill_model_no_attention.py and core/aill_no_attention_components.py implement PyTorch, nn.Embedding, nn.Linear, MLP, LayerNorm, tensor memory, Hebbian/plastic updates, similarity, content addressing and softmax. It is incorrect to say that Elena does not contain neural networks, does not use softmax, or does not include PyTorch.

core/__init__.py However, it defines the current boundary: PyTorch experiments are OFFLINE_ONLY / NON_CANONICAL and must be imported explicitly. The neural prototype is present in the repository but does not constitute the canonical generator of the responses in the audited path.

Ablation of eager loading

Excluding the heavy PyTorch core from canonical loading maintained equivalent outputs in 111/111 shifts e 500/500 cases; TTM and trace F711 also remained equivalent in their respective replays. Ablation showed no causal influence of the neural prototype on the canonical responses in the audited replays. It does not prove that the core is useless, that it will not be used in the future, or that PyTorch is not used in the project.

GLIA

GLIA contains previous-hidden, slot routing, embedding, linear projections and experimental content addressing. The module exists in the repository, but has been excluded from the canonical eager closure along with the heavy core: the correct public classification is HISTORICAL / OFFLINE_ONLY, not current causal component.

WithoutAdam / Big Brain

PersistentBrainState it is imported from the server and participates in the persistent state contract. However, Hebbian and broader consolidation helpers have no demonstrated independent causality on the output. The correct formulation is: WithoutAdam / Big Brain — persistent state contract + non-causal helpers in the audited path. It is not presented as a “generative brain”.

Manifest, enabled phases and promotion

The stated canonical manifest v2 lists F900 and F901 as enabled, disables F902, and enables F903–F913. ENABLED means configured by the manifest: it does not mean automatically causally verified, hash-consistent with the current checkout, or active in a live runtime.

ObjectStateWhat it provesWhat it doesn't prove
Canon Manifest v2F900, F901, F903–F913 enabled; F902 disabledDeclared contractCurrent server hashes and TTM not aligned.
Candidate v19Hash-consistentDeclared sources and checkpoints correspond to checkoutHe is not promoted to canon.
F896Phase and telemetry not promotedThe structured planner can be instantiated in the full learned stackIt doesn't promote F896 and doesn't resolve end-to-end over natural text.
F900–F913Mixed qualification according to manifestFeature contract declaredEnabled is not the same as causally verified or live hash-consistent.

For text-to-meaning the updated wording is: open-domain coverage still incomplete. The most recent candidate is bound to the source and checkpoint hashes, but has not been promoted and does not demonstrate general linguistic understanding.

Documented architectural evidence

SourceWhat does it checkResultConfine
Canon Manifest v2Authorized features and hashesF900/F901/F903–F913 enabled; F902 disabled; 2 source hashes not alignedDeclared contract, not live certification.
Candidate v19Source hashes and checkpoints14/14 consistent checked elementsCandidate not promoted.
Core eager-import ablationHeavy PyTorch core influence111/111 and 500/500 equivalent outputsAudited replays, not universal uselessness of the core.
F235No-attention Word ModelValidated · PASSCircumscribed phase.
F315Word Model Memory BridgeValidated · PASS 10/10Does not test the full runtime.
F896Meaning, knowledge and plannerOracle 32/32 planner; TTM 3/32; end-to-end 2/28Phase and telemetry not promoted.
F898F711 constructionCircumscribed gate PASSStructured input and candidates.

Negative results and candidate v19 status

The frozen external Italian benchmark of external-runtime-repair-candidate-v19 record 0 runtime errors, 1 unique answer, 0/86 correct objective answers and 100/100 abstentions. The result demonstrates fail-closed stability in the sample, not general understanding, open-domain knowledge, or fixed language ability.

The main bottleneck remains text-to-meaning on complex external inputs. Making the verifier more permissive would transform correct deferrals into unfounded answers; it would not correct missing meaning, knowledge, or task handling.

F896: structured planner and natural pipeline

F896 documents 32/32 with oracle queries and frozen evidence, but only 3/32 on complete text-to-meaning e 2/28 end-to-end on applicable cases. The structured planner can be instantiated when the full learned stack is active; this does not promote the phase or its telemetry and does not demonstrate end-to-end operation on natural text.

Historical snapshot 111 rounds

The snapshot of the canonical manifest v2 records, for the historical sample of 111 turns, fallback 77/111 and one meaning completeness of 0.22. This is data from the baseline declared in the manifest, not the current state of the v19 candidate and not a live measurement.

Adam, global backprop and local updates

In the official path audited Adam, AdamW e torch.optim they are not used; global backpropagation is not used in the same perimeter. Adam is an optimizer and is not synonymous with backpropagation. In the repository there are also offline neural prototypes and legacy material: the claims should not be extended to the entire history of the project.

Local updates, Hebbian/plastic and consolidation are implemented in specific components. Their presence does not demonstrate end-to-end persistent learning, influence on every response or promotion in the canonical runtime.

What this architecture does not demonstrate

  • No overall superiority or equivalence to the Transformers.
  • No absolute absence of neural networks, PyTorch, softmax or attention-like mechanisms.
  • No current perfectly hash-aligned live canonical runtime certified by this page.
  • No promotion of candidate v19.
  • No general linguistic understanding or universal reasoning.
  • No equivalence between presence, loading, enabling, causality and promotion.

MLP, embedding, softmax, associative memory, Hebbian/plastic updates, n-gram, and beam search are known primitives. Elena's documentable specificity concerns design combination, component separation, constraints, persistence, gates, verification, and runtime boundaries. No scientifically unprecedented architecture is claimed.

Technical insights

Linguistic system

Text-to-meaning, F711, Decoder V3 and the boundary between representation and output.

Reasoning

Planner, inference, end-to-end verification and failure.

Search path

Historical evolution, candidates, promotions and retirements.