Repository navigation
FAQ
Wiki home · more: Troubleshooting · Glossary
No. Syncing, linting, repairing, links, maps, trust, tracing, export — all deterministic scripts. A gateway is needed for
agent:* (parsing into cards with theses, asking, producing artifacts), semantic search (kb:embed) and scan recognition.
→ The agent
Only to the gateways you configure, and only for the model-driven commands. Mirrors and cards stay on your machine and in
your git. If your perimeter forbids sending materials out, leave semantics and scans off and use a local gateway. The panel
listens on 127.0.0.1 only.
Nobody. Trust is computed from the statuses of the Jira issues behind a card's source (or from a signed document in
Raw/). An issue goes back to work — the card becomes draft at the next kb:trust. → Trust
Issues still in progress, or no links to them were found. The second is cured by tracing (ops:trace-table), not by
changing statuses. Also check trust_statuses in the config.
Yes for knowledge cards where you add what the sources lack — but prefer a correction (kb:correct): it lives in
Raw/corrections/ and is applied at every rebuild, so it survives. Dictionary and document bodies are never rewritten,
and the history footer is never overwritten. → The card
A second model that checks every claim of an agent answer against the source: either a supporting quote, or "no support". Claims without support are not carried into documents. → The agent
So skills, prompts, templates and update work in every project. Anything non-standard goes to Workspaces/<task>/; a folder
needed only by one project is declared in paths.extra_structure_dirs.
Yes, at any moment. The run is cut into complete laps and every lap is committed: what was parsed stays valid.
In .env.aurora.local, which is git-ignored. The panel shows only "filled / empty" and never gives a value back.
kit:mcp prints a ready connection block; the server only reads. → Assistants, MCP and skills
It cannot touch Raw/ (immutable), Sources/ (written only by sync) or Deliverables/released/ (frozen). It writes only
through whitelisted engine commands, always after a checkpoint commit.
It is deterministic: the same source gives the same file byte for byte, so a repeated sync makes no noise in git and
sync:audit can verify it. → Sources and mirrors
It rots by itself in the right direction: when a linked issue is reopened the card drops to draft. A replaced card is
moved to _archive/ with kb:supersede and incoming links are rewritten; Decision Records are append-only and keep the
rejected options.
Yes — the test suite runs on windows-latest in CI. → Windows and macOS
The engine's output and the cards are as you write them (Russian is the project's own language); the panel and the documentation are available in Russian and English. A new interface language is a new file: Contributing.
CHANGELOG.md (in Russian) and the GitHub Releases page; every release is created from it.
This wiki is generated from the wiki/ folder of the repository — edit the pages there, changes made here are overwritten. · RU-Home
Concepts The cycle · The card · Trust · Sources and mirrors · The agent
Using it Getting started · Daily work · Asking the base · Assistants, MCP and skills · Artifacts and deliverables · The control panel
Practicalities Troubleshooting · Windows and macOS · FAQ · Glossary · Contributing
Понятия Цикл · Карточка · Доверие · Источники и зеркала · Агент
Как пользоваться Быстрый старт · Повседневная работа · Спросить базу · Ассистенты, MCP и скиллы · Артефакты и поставка · Панель управления
На практике Если что-то не так · Windows и macOS · Частые вопросы · Словарь · Участие в разработке