Initialize
The first run needs a configuration file and a ledger. The Hermes slash command starts the agentic setup:
/auwai-init
The command returns the initialization brief.
The agent reads the facts, asks the user the questions below, and writes the
configuration with auwai init --write.
What the brief checks
- the repository root and whether it is writable;
- the Python version (3.10 or newer);
- the SQLite version and an in-memory FTS5 probe;
- the index and ledger that already exist;
- the
config.tomlin effect; - the optional codebase-memory binary.
Questions
- Context window: 65,536 for a small local model, 262,144 for a larger local model, or 1,000,000 for a native 1M cloud model.
- Config scope: user-wide (
~/.config/auwai/config.toml) or this repository (.auwai/config.toml). - Ledger location: the default
.auwai/auwai.sqlite, or another path. - Raw-read guard: keep it on, or allow raw reads.
- codebase-memory: auto-export on or off.
The agent should not hand-edit the file. It calls one command with the answers:
./auwai init --write --scope repo --context-window 262144
Optional flags:
--database-path PATH
--journal-mode WAL|DELETE|TRUNCATE|PERSIST|MEMORY|OFF
--busy-timeout-ms N
--allow-raw-read
--cbm-auto on|off
--cbm-bin PATH
--hint on|off
--prime on|off
The command merges the values into the existing file, creates the ledger and
schema, and reports the paths and FTS5 status.
It refuses a database whose meta.root names another repository.
After writing
./auwai index --repo .
./auwai doctor
The index builds the JSONL map and the coverage ledger. The doctor confirms the interpreter, FTS5, and the language providers.
One database per repository
Auwai stores one ledger per repository at .auwai/auwai.sqlite.
A workspace is a manifest over several per-repository ledgers, not one shared
database.
Do not point two repositories at the same database file.