Enterprise Deployment Guide

rescile-ee Service Binary

CLI reference for the service-oriented edition binary, including schema validation and module management.

Edit this page on GitHub

rescile-ee Service Binary

rescile-ee is the service-oriented edition of the rescile controller. It is intended to run under systemd or another service manager, produces syslog-style logs, and exposes the same GraphQL, MCP, Vault, and portal endpoints as rescile-ce.

Most global options (--data-dir, --module, --offline, --git-client, etc.) are identical to rescile-ce. The main differences are the output style (no colors, timestamps, severity-aware logging) and the set of exposed commands.

Commands

serve

Builds the graph and starts the GraphQL server, MCP endpoint, Vault server, and portal.

rescile-ee serve --port 7600 --listen 0.0.0.0
  • --init: Run the bootstrap step before serving (copy/merge starter files from loaded modules).
  • --bootstrap-policy <POLICY>: Default bootstrap policy (once, append, merge, replace, skip) for assets that do not declare their own. Only used together with --init.
  • --write-outputs[=<DIR>]: After every reactive graph rebuild, write rendered output artifacts that have a filename property to <DIR> (defaults to the current working directory). Combine with --write-outputs-filter <PREFIX> to restrict which artifacts are synced.

validate

Validates workspace structure, data, TOML and Jsonnet rules, Canonical Rule IR, and central schema conformance. Human output uses service-safe formatting; --format json emits a stable machine-readable report.

# Use schemas declared in module.toml
rescile-ee validate

# Run only schema conformance against a supplied schema
rescile-ee validate --only schema --schema ./schemas/20260729.schema.json

# Strict full-workspace validation
rescile-ee validate --strict

# Validate rules and emit Canonical Rule IR
rescile-ee validate --render-ir

# Build and validate graph in memory
rescile-ee validate --build
  • Repeat --only <workspace|data|rules|schema|graph> to select categories. Bare validate runs all static categories.
  • --target <PATH> validates one rule file or uses a directory as workspace root.
  • --schema <SOURCE> uses only supplied schema sources and ignores schemas declared in module.toml.
  • --strict enables deep checks and treats warnings as errors.
  • --build adds an in-memory graph build without running generators or writing graph files.
  • --format json emits a machine-readable report; add --output <FILE> to write it to disk.
  • --render-ir emits validated Canonical Rule IR; --render-ir-schema emits its JSON Schema.

save [FILE]

Builds the graph and optionally writes the raw in-memory representation to a JSON file and/or exports rendered output artifacts to disk. Either FILE, --outputs, or both must be supplied.

rescile-ee save ./graph.json --init
rescile-ee save --outputs ./dist
rescile-ee save ./graph.json --outputs ./dist --output-filter .agents/skills
  • FILE: Optional path for the JSON graph dump. When omitted, no graph JSON is written.
  • --outputs[=<DIR>]: Export rendered output resources that have a filename property to <DIR> (defaults to the current working directory when the value is omitted).
  • --output-filter <PREFIX>: Restrict the export to output artifacts whose rendered filename starts with <PREFIX>. May be repeated.
  • --init: Run the bootstrap step before saving.
  • --bootstrap-policy <POLICY>: Default bootstrap policy (once, append, merge, replace, skip) for assets that do not declare their own. Only used together with --init.

mod <lock|check|update|fetch>

Module dependency management. Validation is available only through rescile-ee validate. See Module Dependencies.

info, license, vault

Information, license display, and vault client commands. These exit immediately without starting a graph build.

Logging

rescile-ee initializes env_logger with syslog-style formatting and disables console colors. Validation findings and build messages are routed through the log crate so they can be captured by journald or any systemd-aware log sink.

Exit codes

  • 0 — command succeeded and validation found no errors.
  • Non-zero — command failure or validation produced errors. Warnings and info notes alone do not cause a non-zero exit unless --strict is used.