Sovaria CLI

Operator CLI for gateway-backed Sovaria project and platform workflows.

Run

Examples below use sov ... command syntax.

If sov is installed on your PATH:

sov --help

From repo root without installation:

python -m apps.cli.src.main --help

Cross-SDK Happy Path Smoke

Use the repository smoke script to validate one shared happy path across:

• CLI auth + scoped SQL call
• TypeScript SDK SQL + engine health
• Python SDK SQL + engine health

SOVARIA_URL=http://localhost:8000 \
SOVARIA_ORG_ID=<org_uuid> \
SOVARIA_PROJECT_ID=<project_uuid> \
SOVARIA_EMAIL=<owner_email> \
SOVARIA_PASSWORD='<owner_password>' \
scripts/cli_sdk_happy_path.sh

If you already have valid CLI tokens, omit SOVARIA_EMAIL and SOVARIA_PASSWORD.

Core Command Groups

• sov auth ... auth login/logout
• sov scope ... default org/project/env scope
• sov data ... Atlas-Doc and Atlas-Rel
• sov realtime ... Pulse realtime and e2ee
• sov policy ... Guard policy management
• sov audit ... Echo audit and simulation
• sov chrono ... Chrono timeline/snapshot operations
• sov fn ... Forge function deploy/status/invoke
• sov project ... project config template + scaffold creation
• sov api call ... raw gateway API request

Project Bootstrap (Config JSON)

Create a template config file:

sov project init-config my-app --output sovaria.config.json

Then scaffold a project from that config:

sov project create --config sovaria.config.json --dir .

Function Sandbox Flow

Deploy a function bundle (zipped from local folder):

sov fn deploy ./my-function --name hello --project <project_id> --note "add audit logging"

Poll deployment status:

sov fn status <deploy_id> --project <project_id>

Invoke the deployed function in its project sandbox:

sov fn invoke hello --project <project_id> --data '{"message":"hi"}'

Run a simulation invocation (tracked separately from normal invoke):

sov fn invoke hello --project <project_id> --simulate --data '{"message":"dry-run"}'

Queue heavy async invocation and wait for completion:

sov fn invoke hello --project <project_id> --execution-profile heavy --async --wait --data-file payload.json

List function versions:

sov fn versions hello --project <project_id>

List functions with active versions + queue depth:

sov fn functions --project <project_id>

List invocation history:

sov fn history hello --project <project_id> --mode invoke

List durable async jobs:

sov fn jobs hello --project <project_id> --status QUEUED

Promote a specific function version:

sov fn promote hello --project <project_id> --version 3 --reason "promote stable release"

Rollback to previous active version:

sov fn rollback hello --project <project_id> --reason "rollback regression"

Diff two simulation invocations:

sov fn sim-diff hello <left_invocation_id> <right_invocation_id> --project <project_id>

Scope Requirement

Realtime and relational routes require org/project scope. You can pass scope per command (--org --project --env) or set defaults:

sov scope set <org_id> <project_id> --env <env_id>