BASEtrading knowledge base
RU

One base for people and for agents

How the base works

BASE collects the terms of all our projects in one place, so that people and AI agents in every project read the same definitions.

One source, three outputs

The wiki/ source is built into the site, terms.json and GLOSSARY.md wiki/ glossary.json + pages 🌐 Site base.adventu.pro people: Simple / Pro, RU / EN 🔌 /api/terms.json sites: term tooltips 🤖 wiki/GLOSSARY.md Claude / Codex agents in every project
Edits are made in one place, /var/www/projects/BASE/wiki/; the node build.mjs command rebuilds everything else.

Rules

  1. One term, one entry. If projects interpret a term differently, it is not duplicated; the difference goes into the “discrepancies” field (⚖) and the term gets the “being refined” status.
  2. Every claim has a source. In the Pro version, pages and terms carry a “Sources in projects” list: the path to the file where it is written down.
  3. New beats old. The latest version is described; earlier ones go into the history, marked as such.
  4. Two audiences. “Simple” has no formulas and uses analogies; “Pro” has formulas, code and test numbers.

How projects use it

Statuses

✓ settled — the same in all projects and in the code. ⟳ being refined — still being aligned: interpretations differ or the rule is under test.

How the base is updated

  1. Proposal. An agent in any project (or a person) spots a new term or a different reading in code. It does not edit the glossary; it queues a proposal with bin/wiki-propose, always with a path to the file that proves it.
  2. Agent review. Once an hour the reviewer agent (bin/wiki-review) opens the source and decides: apply, reject or leave for a human. An empty queue does not start a model.
  3. A human for what matters. Changes to the four core concepts, moving a term to “stable” and rewriting a stable definition always wait for the owner (wiki-review --list / --approve).
  4. Publishing is automatic. After a change the site, terms.json and GLOSSARY.md are rebuilt and deployed, and the change log below gets a row. A copy of the glossary before each change is kept in wiki/.history/.

The rules live in wiki/policy.json: agent mode (the agent applies safe changes itself) or human mode (everything goes through the owner).

Glossary change log

DateTermChangeFromApproved byWhy
2026-11-07RTS Index (RTSI)newmambaагент (claude sonnet)load-rtsi.py подтверждает FINAM, M5/H1, asset_class='index', исключение из цепочек и дашбордов; обновление каждые 5 минут подтверждается CLAUDE.md (s0-rtsi-refresh.timer, #420).