-
Notifications
You must be signed in to change notification settings - Fork 2
Commands
Ânderson Q. edited this page Jul 21, 2026
·
6 revisions
You mostly run one thing — tron start. TRON then runs autonomously; you're not in a REPL.
Wake TRON. A short bootup asks two things — where to start (scope: all, a phase, or a range of blocks) and how many workers — with an optional AIDE advisor (a real LLM, counsel only, fail-open) recommending a next block. Then TRON dispatches the fleet and drives the pipeline to done, printing milestone notes as blocks land. Pass a project path to skip the picker.
TRON pages you (terminal OPERATOR> prompt, or Telegram if configured) only when it needs a
decision. You reach TRON by dropping a file in the project root:
| Drop a file | Does |
|---|---|
parley.md |
a question or instruction — the architect answers, recorded under parley/
|
report-request.md |
the architect writes a status report, recorded under reports/
|
STOP |
under --watch, ends the run |
| Command | What it does |
|---|---|
./tron --watch |
long-running: idles, wakes on register work (WAKE), exits on a STOP file |
./tron --selftest |
the engine selftests — no agents, no tokens |
python3 engine/tron.py |
the engine directly (Enter at the prompt = built-in demo project) |
| Command | What it does |
|---|---|
python3 engine/<module>.py |
that module's selftests (gate, glossary, events, workflow, bpmn, tg) |
python3 engine/glossary.py --write |
regenerate docs/GLOSSARY.md (same for events/workflow; bpmn.py --write regenerates workflow/) |
python3 evaluation/harness.py <template> N |
run N SIMs of a template; --parallel N, --ablate ARM
|
See also: Configuration · Operations.