Reference
Commands
Every make target, script subcommand, and CLI flag in the IRIN repo, tagged by who it is for. Snap your fingers wisely.
The root Makefile
Run these from the IRIN repository root. Operator tags are for the human running the gauntlet; Engineering tags are for the humans building it.
Setup and proof
make help
OperatorPrints the target list. The gauntlet's own table of contents.
make setup
OperatormacOS only. Prepares private config and signing material, builds and starts Council, War Room Web, and Gateway, enables login recovery, then prints your service URLs. Preserves operator-owned values you already set.
make setup-prepare
OperatorPrepares config and signing material only. No services are built or started.
make app-install
OperatormacOS only. Builds, atomically installs, and launches the native desktop shell. It reuses the runtime make setup already started; it never starts a competing backend.
make verify make verify-down
OperatorThe proof lane. Runs the Sentinel-to-signed-directive path end to end in an isolated stack: no provider keys, no hardware arming, own ports, own volumes. Knobs: DEMO_ALLOW_BUILD=1, DEMO_PULL=1, DEMO_GW_PORT=28080, DEMO_COUNCIL_PORT=28765, DEMO_POLL_TIMEOUT=90. Details on the Ceremony page.
Managed runtime
make runtime-up
OperatorStarts the managed runtime: Council, War Room Web, and Gateway under the supervisor.
make runtime-down
OperatorStops the managed runtime.
make runtime-restart
OperatorRestarts the managed runtime.
make runtime-status
OperatorPrints per-service status for the managed runtime.
make docker-cache-prune
OperatorOps hygiene. Prunes build cache while keeping images, containers, and volumes intact.
War Room and engineering
make warroom
OperatormacOS and Ubuntu. Builds and starts Council plus War Room Web in the foreground on loopback; stop with Ctrl+C. Knobs: COUNCIL_PORT, WARROOM_WEB_PORT, WARROOM_ADOPT=1.
make warroom-tauri make warroom-tauri-build
EngineeringDev lane for the native desktop shell: run it live, or build the bundle.
make release-check
EngineeringThe release gate. Runs the checks a release must pass.
make worktree BRANCH=feat/example [DEST=path]
EngineeringCreates an isolated worktree runtime. BRANCH= is required, DEST= is optional.
make build make test
EngineeringBuilds the workspace and runs the test suites.
The runtime supervisor: scripts/irin-runtime.sh
One script rules the managed runtime. The make runtime-* targets are thin wrappers around these subcommands.
irinityhq/irin; the canonical profile must be on a clean main.uninstall-login
com.irinity.irin-runtime.login.Supervisor knobs
Component targets
Each component keeps its own Makefile. One line each; the stones do not ramble.
council-rs
gateway
LEDGER_KEY_PATH (default ~/.irin/ledger_key.pem). Never overwrites an existing key. Dev and CI only.BUDGET= is required; TIER= defaults to default; RPM= defaults to 600.LEDGER_DB_PATH (default ledger.db).triad-test, triad-smoke.Council CLI flags
The Council binary takes its own flags for seats, modes, rounds, and chairs. They are documented flag by flag on the Council stone page.
Where things listen
Everything binds to loopback. The only way out is the private Tailscale endpoint, and that is yours alone.
127.0.0.1:3010127.0.0.1:8765: REST at /api/health, stream at /ws.127.0.0.1:18080: /health, /watch, /admin/keys, /ledger/verify, /metrics, /v1/models.:9090, Codex proxy :9091.:443: maps / to Web, /api and /ws to Council, /watch and /health to Gateway.28080, Council stub 28765. Compose project irin-demo.20000+slot, Web 22000+slot, Gateway 24000+slot, where slot is cksum mod 1000.Platform split
Not every stone fits every gauntlet. Check the platform before you snap.
macOS only
make setup, setup-prepare, app-install, and warroom-sign. The whole irin-runtime.sh supervisor is macOS-shaped: launchctl, lockf, ~/Library/LaunchAgents.
macOS and Ubuntu
make warroom, make verify and verify-down, the Gateway docker stack, and cargo build / cargo test.
Fine print, read before you snap
- The managed runtime enforces the canonical origin (
irinityhq/irin) as a source-provenance boundary. - Fork contributors can build, test, and verify, but cannot launch the managed runtime from a fork.
- Neither
make verifynormake runtime-statusproves a paid provider call or an armed action path.