Daily Work - VVG-web/aurora-studio GitHub Wiki

Daily work

Wiki home · related: The cycle · Troubleshooting · the full table: Practice: situation → command · every command: command reference

One command can be run three ways, and the name is the same everywhere (kb:repair, ctx:context, agent:make):

  1. a panel button — the default path;
  2. the terminal — python3 aurora.py <verb> <project> [flags], or a script from .aurora/scripts/;
  3. the assistant — /aurora-vault <command>, for procedure commands that need meaning.

The rhythm

When What How
every day, ten minutes take the new, see what drifted Update the base → sync:audit → sync:diff → ops:stats
after every sync trust ops:trace-table → kb:trust (the route does it itself)
weekly hygiene Fix the base → ops:todo → kb:garden
monthly navigation and quality kb:moc --suggest, ops:search-quality, ops:gaps
development is going on tracing sync:jira-status → ops:trace → make:spec-pack
an artifact is ready outward make:review → ship:export → ship:publish → ship:release

The three kinds of command

Kind Examples Rule
Observation ops:stats, kb:lint, ops:impact, ops:trace, sync:audit, sync:diff, kb:schema, kb:scrub, kit:doctor run freely: they change nothing
Writing everything with --apply: kb:repair, kb:supersede, kb:index, ship:release, kit:update, agent tasks without the flag you get a preview — always read it: a mass edit is what you sort out in git diff for hours
Outward sync:*, ship:publish, ship:export need the network and a token; change external systems

Which command, when

flowchart TD
  Q{"What do you need?"}
  Q -->|"take the new from the sources"| A["Update the base"]
  Q -->|"put the base in order"| B["Fix the base"]
  Q -->|"find something out"| C["Ask · ctx:context"]
  Q -->|"write a document"| D["Production · agent:make"]
  Q -->|"hand it outward"| E["ship:*"]
  Q -->|"record knowledge by hand"| F["kb:decide · kb:question · kb:correct"]
  Q -->|"something broke"| G["kit:doctor · kb:lint · ops:todo"]
Loading

What a human actually does

Almost nothing of what used to be manual: you do not approve cards, set trust or fix links by hand. What remains:

  • write what the sources lack — Decision Records (kb:decide), questions to the customer (kb:question, closed by kb:answer), your own reference lists, corrections (kb:correct) when a card is wrong;
  • resolve the disputed — duplicates the machine did not dare merge, cards without links to issues, claims Momus marked "no support" (ops:todo lists them with the reason it is not a button);
  • press two buttons — Update and Fix.

Handy one-liners

Situation Command
A card is wrong kb:correct --new "Request" --text "…" — a correction in Raw/corrections/, applied at every build
Two files say one thing kb:dedupe, kb:twins, agent:twins
A card grew bloated kb:split
A card is obsolete, a replacement exists kb:supersede <card>
Who relies on this card ops:impact <card>
The card schema changed with a kit version kb:schema
File names fail on Windows or macOS kb:names
Update a project's engine kit:update (preview), then --apply
I do not remember which commands exist kit:list

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

⚠️ **GitHub.com Fallback** ⚠️