Skip to content

Getting Started

Jump to bottom
Ânderson Q edited this page Jun 5, 2026 · 7 revisions

Getting Started

Requirements

  • python3 and git.
  • jq — the shell connectors parse JSON.
  • crontab — the autonomous heartbeat.
  • A background-capable agent runtime on PATH — the runtime that runs the worker agents TRON dispatches. TRON drives it; you never address it directly.

Your target project should already have agent definitions for the roles TRON dispatches (architect, engineer, reviewer) under its agents directory.

1. Seed TRON into a project

From a clone of the canon repo, run the seeder from your project root:

cd ~/code/my-project
~/code/tron/tron seeder

The seeder is an interview. It:

  1. Settles the knobs (architect count, reviewer cadence, whether the workflow commits, peer-consult pairs).
  2. Locates your agents directory and your specs directory.
  3. Lays down TRON's folder (<agents>/tron/) — canon copied verbatim, knobs written per your answers.
  4. Validates your agents + specs, builds the pipeline (or adopts your existing status doc).
  5. Runs blueprint-lint and writes a seed trace.

It touches only <agents>/tron.md and <agents>/tron/. Nothing else in your project is modified.

worker_count is not asked here — TRON asks it every time you start a session.

2. Wake TRON

From the seeded instance:

<agents>/tron/tron start

Bootup asks two things — where to start (default: the whole pipeline) and how many workers (worker_count; the architect is extra) — then spawns the architect and dispatches the first work. You drop into the live console.

3. Inside the console

  • Type to talk to TRON — your line is classified and routed; out-of-grammar input is refused.
  • status — the fleet. pipeline — block statuses. log — recent events.
  • stop — release the fleet and end the session.

After this, TRON runs on its own: a cron heartbeat ticks the engine, fills slots, clears ahead, and surfaces to you only what matters. You can close the console and reattach later with tron start.

Removing TRON

Delete <agents>/tron.md and <agents>/tron/. No other traces.

See also: Commands · Configuration · Operations.

TRON

Clone this wiki locally