Research · Questions and evidence

Research into a developing architecture.

LARI research asks whether an AI model can acquire, construct, compose, and retain executable representations as part of a locally controlled architecture. This is a scientific effort to make a different model—not a claim that current systems already deliver general intelligence on inexpensive hardware. The questions below describe active investigations and evidence boundaries.

01 · Executable learning

Can experience change behavior in a checkable way?

Problem. A system can appear to improve because a developer added a shortcut or a test reused known code. Research must separate those explanations from behavior acquired from examples or failures.

Approach. LARI stores typed rules and programs, then tests candidates against baselines, unseen cases, ablations, reloads, and rollback where applicable.

Demonstrated. The report describes bounded candidates with causal and transfer checks, alongside failures and unpromoted work.

Unresolved. Independent generalization, durable benefit across ordinary use, and broad capability remain open questions.

Browse reviewed experiment records →

02 · Representation growth

What structures should a growing model acquire?

Problem. Memorizing outputs does not explain how knowledge can be composed or reused across tasks.

Approach. LARI investigates typed operators, semantic relations, recursive generators, and executable structures that can be selected by a shared kernel.

Demonstrated. Some bounded structures have passed family-specific qualification in historical and current evidence.

Unresolved. Growth must remain useful outside the training contrasts, avoid regressions, and preserve meaning under composition.

Read about structured model state →

03 · Program induction

Can a system construct a procedure from examples?

Problem. Procedures can be authored or retrieved; neither alone proves induction.

Approach. Bounded candidate synthesis uses explicit task contracts, constrained search, execution, and immutable checks.

Demonstrated. Certain coding lanes and program families have bounded passing evidence, while object-program and broader repository tasks also show failures.

Unresolved. Search cost, unseen structures, ambiguous requirements, and arbitrary repository work need stronger qualification.

See the observatory status →

04 · Language generation

How far can structured generators support language?

Problem. Bounded conversational families are not unrestricted language understanding or generation.

Approach. LARI represents selected discourse and semantic operations as composable records and tests hidden variants and ablations.

Demonstrated. The report documents qualified bounded RECAP families and recursive composition in production, with family-specific gates.

Unresolved. Broad generation, long-horizon dialogue, multilingual coverage, and robust open-domain semantics remain limited.

View capability qualification →

05 · Persistent model state

What survives process boundaries and rollback?

Problem. User memory, a candidate learned record, and an active model are different state layers.

Approach. Tests distinguish scoped persistence from model promotion and measure reload, isolation, and rollback separately.

Demonstrated. The internal record includes fixture-backed persistence checks and separate registry operations.

Unresolved. A narrow fixture result cannot establish general durability, multi-user safety, or all entry points.

Read the state model →

06 · Verified learning

What does “verified” mean for a learned behavior?

Problem. Passing examples may reflect leakage, a pre-existing intrinsic, or a test-specific patch.

Approach. Use sealed transfer cases, causal ablation, cold reload, parity across surfaces, regression checks, and explicit model binding.

Demonstrated. The report records both qualified bounded results and candidates that remain unpromoted or fail a gate.

Unresolved. Qualification is only as broad as the tested families and environment; it is not a global certification.

Read the claim-scope guide →

07 · Generalization

Can a rule travel to genuinely new tasks?

Problem. Paraphrases and near-duplicates can overstate transfer.

Approach. Separate discovery from sealed validation and test distinct domains, schemas, and execution paths.

Demonstrated. Several bounded transfer studies report held-out successes; other studies fail when the task family or interface changes.

Unresolved. The evidence does not establish general-purpose reasoning or robust transfer to arbitrary settings.

Follow reviewed milestones →

08 · Efficiency

What are the costs of search and qualification?

Problem. A method that works only with excessive search or expensive repeated verification may not be practical.

Approach. Record bounded search steps, runtime conditions, test counts, and comparable baselines rather than collapsing unlike tasks into one score.

Demonstrated. Current report evidence includes measured bounded search and performance observations, including unproductive searches.

Unresolved. Cross-task efficiency comparisons and end-to-end user value need consistent conditions and fresh evaluation.

Read the evaluation method →

Reviewed research

Selected stories from Lari Live

LARI built a small JavaScript app twice, starting from zero each time ↗

An isolated candidate began with zero implementation modules, induced a four-program typed bundle from local immutable tests and a project contract, created three JavaScript source files, and passed all 12 acceptance checks. The construction run passed twice. A serialized candidate then rebuilt a second blank workspace in a fresh process with induction disabled; removing the generated command-line entry point restored failure. The candidate remains separate from the active model and unpromoted.

demonstrated · verified · 2026-10-23T10:10:12.710Z

Seven sources and a real test contract—but no Go dependency planner ↗

An October 23 attempt acquired seven public sources and recovered positive examples and rejection conditions from the immutable Go tests, but the shared typed inducer produced no planner. Later diagnostics still produced no candidate: one direct typed search reached its 100,000-step limit, and a separate relational route rejected the task shape before generating candidates. These are distinct runs and budgets. The compiler’s generic nested-loop sketch is not a Go planner.

negative-result · verified · 2026-10-31T01:11:19.307Z

A bounded relational procedure passed held-out tests and failed after exact removal ↗

The shared typed proposer induced one repeated keyed-state update program without receiving the target AST. After an ambiguous first hypothesis, the review retained that failure and added a separately frozen refinement split; three acceptance holdouts stayed out of search. The selected candidate passed all six induction/refinement examples and all three holdouts. A fresh process reloaded the exact record with research and induction disabled and passed the holdouts; removing that record returned performance to zero of three. The candidate was not promoted.

demonstrated · verified · 2026-10-31T00:00:00Z

Five bounded coding lanes have report-derived production qualification ↗

The 2026-10-31 source report describes five named coding lanes in active production: traceback-based issue localization, isolated test creation when a native harness is blocked, coordinated multi-file repair, behavior-preserving refactoring, and bounded long-horizon multi-defect repair. It reports 5/5 reuse-only lane checks, three causal ablations, reload, rollback, and same-hash selection across five public surfaces. The active model identity matched the report at review time; the underlying per-lane qualification suite was not freshly rerun for this release.

production-qualified · verified · 2026-10-31T00:00:00Z

RECAP generates bounded language and composes existing families ↗

The 2026-10-31 source report describes 38 atomic RECAP records across seven bounded language families as present in active production. It reports inherited ancestor qualification: 6/6 training families, 12/12 unseen semantic variants, 32/32 new-record ablations, 12/12 reload checks, 17/17 hidden transfer cases, five-surface parity, and no family regressions. A bounded recursive-composition record is also reported active with inherited qualification. The active-model identity matched the report at review time; the family qualification suite was not rerun for this release.

production-qualified · verified · 2026-10-31T00:00:00Z

Qualification keeps a verified candidate distinct from production ↗

LARI’s documented governance separates evidence, isolated candidates, qualification, active-model state, and explicit promotion. A current qualification receipt verifies one isolated candidate on two workspace languages: fail-before/pass-after, persisted-candidate reload, and exact-operator removal restoring failure. The active model, registry, and runtime remained read-only, the candidate was not promoted, and external-model calls were zero. The report separately describes rollback controls for bounded production lanes; those rollback checks are inherited report evidence, not a fresh rollback test in this receipt.

demonstrated · verified · 2026-10-31T10:00:58.566Z

Evidence boundary

Selected research stories and evidence are drawn from the individually approved snapshot; unapproved candidates and raw evidence remain private.

Open Lari Live → · Join the Community Lab →

Discuss this page

Read and join this page’s discussion here. Sign in to GitHub when you want to reply or react.

Loading discussion from GitHub…