Reference

The tx-engine command.

A terminal showing tx-engine replay with sandbox, chaos, and serve.
Replay takes a transaction id and stays in the sandbox.

The shaded jar is mcp-tx-proxy/target/tx-engine.jar. The entrypoint is org.atp.proxy.TxEngineMain.

CommandWhat it does
demo --port 8080Serves the operations console and POST /mcp. Same process as serve.
stdioReads one JSON-RPC object per line and writes one response per line.
keysPrints a new Ed25519 public key, then the private key, both base64.
sign --kid --private --payloadSigns a manifest payload file.
replay --tx --wal-dir --sandbox --up-to-stepWalks a recorded transaction. --sandbox is required.
chaos --out file.csvWrites the recovery comparison. Parent directories are created.

Environment

VariableEffect
ATP_JDBC_URLJournal in JDBC. H2 and PostgreSQL are on the classpath of the shaded jar.
ATP_JDBC_USERJDBC user. Empty when unset.
ATP_JDBC_PASSWORDJDBC password. Empty when unset.
ATP_WAL_DIRFile journal, used only when no JDBC URL is set. Writes wal.bin and wal.anchor.

HTTP routes on the demo

Build gates

mvn -B verify
cd sdks/python
python -m coverage run --source=agent_tx -m pytest
python -m coverage report --fail-under=100

Java 21 is required. mvn verify fails unless JaCoCo reports a line-coverage ratio of 1.00 for the engine, the proxy (the process entrypoint is excluded), and the Java SDK.