Research

Quasar AI

Our own core. Our own knowledge. A verifiable conclusion.

The project’s own intelligent system: the core, the knowledge, the language analysis and the inference all live inside Quasar. An answer is built by algorithms over knowledge from books, dictionaries and manuals. In supported scenarios, the grounds of an answer are preserved and checked.

A deterministic coreC++Knowledge cubesOur own servers

Now: contextual understanding and verifiable inference · updated 25 September 2026

The parts

What the system is made of

Quasar CoreThe computing core: parsing the request, finding knowledge, inference and verification.
Quasar AI AgentPlanning and tool use are under development. Independently understanding and modifying an unfamiliar project are upcoming milestones.
Memory and knowledgeReferences, dictionaries, grammars, an encyclopaedia and textbooks. Knowledge lives as data, not wired into the code.
Analysis toolsChecking grounds and dependencies in supported tasks; general document understanding is still being developed.

What Quasar AI is

Quasar AI is the project's own intelligent system. Its C++ core, knowledge, language analysis and inference are developed within the project and run on our own infrastructure.

In supported scenarios, answers are built by algorithms over knowledge from books, dictionaries and manuals. Each case preserves its grounds, assumptions and revision history. When evidence is missing, the system should name the gap. This is a development principle; universal understanding of arbitrary requests has not yet been achieved.

What has been verified

In the mathematical scenario, Quasar calculates a 2×2 matrix determinant exactly, compares two input editions and independently checks the difference between their results. In the control example, changing one cell from 4 to 5 changes the result from −2 to −1.

Withdrawing an assumption removes the applicability of dependent conclusions while retaining the earlier result in the history. Cases survive a restart; a person can select a particular answer and continue that case.

The same mathematical meaning can already be expressed in several orders of presentation. A first Russian construction is built from roles — “Детерминант равен −2”: the designation has supporting evidence, the word form comes from morphology, and an independent check verifies agreement and meaning.

The QLEX dictionary package is connected to the standard engine. For tested dictionary queries, answers are built from typed articles with an internal trace and source coordinates; unsupported meanings are not replaced by guesses.

For ordinary ice in fresh liquid water near 0 °C, Quasar has checked an inference from density values and Archimedes’ principle. The original question and five paraphrases produce the same ten-step trace; that trace is not reused for a different temperature or medium without supporting evidence.

These results apply to the specified scenarios. They do not yet amount to a general conversational assistant, translator or autonomous programmer.

What we are working on now

Updated 25 September 2026.

The project already contains large Wiki and Habr knowledge cubes, dictionaries, physics knowledge and programming manuals. The current question is not whether to add more gigabytes, but whether Quasar can complete the whole path: understand a request, select a relevant source, retrieve a specific record, connect it to a rule and preserve the grounds for its answer. A large cube does not by itself prove that Quasar can use its knowledge.

When a request is ambiguous, Quasar should first check available articles and other relevant sources, then compare them with the history of that conversation. If the sources and context identify one meaning, it should select it and preserve its grounds. A clarifying question is asked only if distinct, source-supported possibilities remain after that search or a specific fact needed for retrieval is missing; it should resolve that distinction rather than replace knowledge retrieval with a refusal.

First, we are testing whether Quasar can use the contents of the cubes already present; new data will be added only after a specific knowledge gap is demonstrated. Then we will extend reusable inference from facts and rules with explicit applicability conditions. The next major goal is constructing code from language manuals: derive program constructs and lines from documented rules, rather than calling a code generator or inserting ready-made solutions or task templates. A capability not confirmed by the language specification or manual must not be presented as supported. New language features are a separate development effort or a proposal to the language maintainers.

The presence of 19 languages and 45 directions in the dictionary corpus does not mean full-text translation is ready for all of them; open-ended conversation and autonomous programming have not yet been achieved.

The laws it works by

Freedom to research anything, with a ban on presenting the unproven as proven. An honest “not proven” that names the missing observation is preferable to a confident assumption.

Provenance is never fabricated: an unknown source remains unknown in the journal. A feature is evidence only where it distinguishes the cases under consideration.

Accepted milestones are protected by targeted tests and negative checks. The full integration gate remains a separate upcoming milestone.

What this has to do with the trading terminal

The ecosystem's released products work independently. Applying the research core to trade reviews and explanations of risk remains a development goal.

Quasar AI has not yet been released as a user-facing product. Research continues through verifiable milestones, without a promised completion date.

Roadmap

Seven stages of the research

Each status applies to the stated scope of verification. Having a source does not yet mean having a working capability.

Stage 0 — the foundation

  • Verified. A C++ core with a replayable case journal and verifiable state transitions
  • Verified. Established findings, hypotheses and unknowns kept distinct in supported tasks
  • Verified. Knowledge storage and a reproducible build of the previous dictionary cube
  • Verified. Targeted tests, negative checks and mutation tests for accepted milestones
  • In progress. The full integration gate: the final run is still ahead

Stage 1 — language

  • Verified. A first Russian sentence construction built from roles, with independent agreement checks
  • Verified. Gender and number of short adjective forms from a morphological dictionary; ambiguous forms are not guessed
  • In progress. Extending Russian grammar to further constructions and kinds of answer
  • In progress. Using English grammar sources within the wider language system
  • Planned. Full language-system acceptance beyond the tested constructions

Stage 2 — knowledge

  • Verified. Previous dictionary cube reproduced: 8,097,450 records with no discrepancies
  • Verified. Entire corpus examined: 225 dictionary files, 19 languages and 45 directions
  • Verified. A complete verifiable dictionary package: definitions, translations, references and explicit reasons for unsupported content
  • In progress. End-to-end use of existing Wiki/Habr, dictionary and manual cubes: a retrieved record must become grounds for inference, not merely exist in storage
  • In progress. Selecting dictionary meanings from sources and conversation history; ask only when supported candidates remain indistinguishable
  • Planned. Automatically filling knowledge gaps recorded in the journal

Stage 3 — reasoning

  • Verified. A multi-step cycle of goals, observations, hypotheses and conclusions in tested scenarios
  • Verified. Exact calculation of a 2×2 matrix determinant using a verified law
  • Verified. Comparing two matrix editions with exact input and result differences
  • Verified. Withdrawing an assumption and revising dependent conclusions without declaring them false
  • Verified. Causal answers to a supported form of “why” question
  • Verified. Inferring why ordinary ice floats in fresh water near 0 °C for the original question and five tested paraphrases; changed conditions do not reuse that proof
  • In progress. Extending inference to new cases only when facts and rules with verified applicability conditions are available
  • Planned. Units and dimensions, and comparing two calculated sets of alternative assumptions

Stage 4 — speech

  • Verified. Cases survive a restart; a user can continue an explicitly selected answer
  • Verified. Several orders of presentation for the same mathematical meaning
  • Verified. Independent verification of speech in supported mathematical and causal scenarios
  • In progress. Lexical choice that accounts for meaning, grammatical government and register
  • In progress. Use the current conversation topic to select a meaning; explicit topic changes and insufficient context need separate tests
  • Planned. Open-ended conversation and varied speech beyond tested scenarios

Stage 5 — the agent

  • Verified. Subgoals and planning in tested multi-step scenarios
  • In progress. Developing tools for working with projects and code
  • Planned. Verifiable understanding of unfamiliar code: dependencies, execution paths and predicted results
  • Planned. Constructing code from language manuals: derive each construct from documented rules, with grounds and checks; no code generator, ready-made solutions or task templates
  • Planned. Independently modifying a project and checking predictions by execution
  • Planned. A self-development loop: a gap → a contract → a check → a justified change

Stage 6 — application

  • Planned. Review of a trade in the terminal
  • Planned. Explaining a decision with a verifiable argument
  • Planned. An assistant for analysing ideas
  • Planned. Integrating the research core with ecosystem products

The update date indicates how recent this information is. No research completion date has been set.