Aurora Studio Wiki

English · Русский

A knowledge base about Aurora itself: short pages that each answer one question in a screen or two and point to the full document in docs/ when you need depth. Read it on GitHub as it is — every link works in the repository view.

One sentence. Aurora turns the documents a project piles up (Confluence, Jira, contracts, meetings) into a base of Markdown cards where every card says how far it can be trusted, and produces analyst artifacts from that base without letting a model invent facts.

flowchart LR
  A["Sources"] --> B["Cards"] --> C{"Trust"} --> D["Context"] --> E["Artifacts"] --> F["Delivered,<br>frozen"]
  C -.->|"draft: not yet<br>to be believed"| G["What is left<br>for a human"]

Start here

I want to…	Read
install it and see it work	Getting started
understand the idea in five minutes	The cycle → The card → Trust
know which command to run	Daily work
find out why something broke	Troubleshooting · FAQ
look up a word	Glossary

Concepts

Page	Answers
The cycle	What happens from a source to a delivered document, and which two buttons drive it
The card	What a card is, its kinds and statuses, what is allowed to rewrite it
Trust	How a card becomes knowledge or draft, and why nobody approves anything
Sources and mirrors	How Confluence, Jira, sites and Raw/ get into the project
The agent	The built-in agent: gateways, roles, Momus, limits

Using it

Page	Answers
Asking the base	Questions in your own words, context packs, search
Assistants, MCP and skills	Giving the base to Claude Code, Cursor, OpenCode
Artifacts and deliverables	Writing, reviewing, exporting, publishing, freezing
The control panel	A tour of the local web panel
Daily work	The working rhythm and the situation → command map

Practicalities

Page	Answers
Troubleshooting	Typical errors and what to do
Windows and macOS	What behaves differently, file names, launch files
FAQ	Short answers
Glossary	The words Aurora uses
Contributing	Tests, releases, how to add a command, a skin, a language

About this wiki

The pages live in wiki/ of the repository and are reviewed like code: a change that alters behaviour updates its page in the same pull request. Russian pages are in wiki/ru/ and cover the same set. The test suite checks that every link resolves, that both languages have the same pages, and that every page is reachable from here. When the repository's GitHub Wiki is switched on, the workflow wiki-sync publishes these pages there as well — the repository stays the single source of truth.

Full documentation: docs/README.md · command reference: commands.md.

---

This wiki is generated from the wiki/ folder of the repository — edit the pages there, changes made here are overwritten. · RU-Home