FAQ

FAQ

How is this different from an agent-orchestration framework?

Most frameworks let an LLM decide the next step. TRON doesn't: the flow is a fixed event table run by deterministic code, lint-checked before it runs. The model is called only to build and for two narrow, typed judgments — never to choose a transition. You get predictable, inspectable orchestration with a human in the loop, not an autonomous agent improvising a graph.

What do I need to run it?

python3, git, jq, crontab, and a background-capable agent runtime on PATH that runs the worker agents. See Getting Started.

Is there a hosted/SaaS version?

No. TRON is yours and runs on your machine. It's a supervisor for your own dev work, not a service.

What happens if it crashes mid-session?

Each tick is crash-safe: state is persisted atomically, dispatch intent is committed before any spawn (no double-spawn on retry), and inbound messages are processed at-least-once (no lost work). The next heartbeat resumes; tron recover reattaches live workers explicitly. See Architecture.

Can I run more than one reviewer type?

Yes. cadence is a map of lens → threshold (code, security, data, …). Add an entry to schedule that lens; drop it to stop. See Configuration.

Why is the architect separate from the workers?

It's the throughput gate: only cleared blocks are dispatchable, and the architect is what clears them — forward-only. Keeping it out of the worker pool means clearing never competes with building. If engineers starve waiting for cleared work, raise architect_count.

Can I change how TRON behaves?

You tune knobs (workflow.yaml) and pointers (project.yaml) — counts, cadence, peer-consults, git, pipeline mode. The behaviour (the event table + trigger grammar) is canon and intentionally not per-project; that's what keeps every instance lint-checkable. See Configuration.

How do I extend the worker roles?

Add the agent definition in your agents directory and reference the role (as a cadence reviewer type, a peer-consult pair, or a pipeline block owner). The seeder validates that every referenced role has a file.

How do I contribute?

The canon repo is the single source of truth; per-project customization lives in seeded instances, never in canon. PRs that add project- or machine-specific assumptions are rejected. Open an issue first for non-trivial changes.

License?

Dual-licensed: AGPL-3.0 for open-source use, or a commercial license to use TRON without the AGPL-3.0's obligations (closed-source / SaaS) — contact ahoy@42labs.io.