AXIS Documentation / Operations / Operations

Operations

VerifiedRuntime visibility

Day-to-day operations: monitor the gate, review decisions and approvals, update policy safely, verify evidence, and back up the audit trail.

Monitoring

Checks

curl -sS http://localhost:6543/health
curl -sS http://localhost:6543/runtime/stats
curl -sS "http://localhost:6543/logs?level=error"

Endpoint	Use for
`GET /health`	Liveness; non-ok when the startup chain (WAL, manifest, policy) failed
`GET /runtime/stats`	Request counts by query type, policy version, pending approvals, uptime
`GET /logs`	Operational log buffer (bounded, in-memory — not durable proof)
`GET /audit`	Review recent decision/execution events with filters

Alert on: health non-ok, audit_corruption_detected, db_unavailable, execution_state: unknown events, and any emergency bypass events.

Approval operations

Review pending approvals: GET /approvals?status=pending; each record shows the exact SQL, classification and context.
Resolve: POST /approvals/<approval_id>/resolve with decision: approve|reject and a note; resolution is immutable and writes evidence.
Purge expired approvals: POST /approvals/purge (operator token).
TTL control: AXIS_APPROVAL_DEFAULT_TTL_SECONDS (default 300).

Policy operations

Validate the candidate: POST /policy/validate — read-only, no side effects.

Diff against active: POST /policy/diff — rule-level changes, flags action changes.

Dry-run real SQL: POST /policy/dry-run — decision preview without execution or audit writes.

Create candidate: POST /policy/candidates (operator token).

Activate: POST /policy/activate with expected_hash — failure keeps the previous policy.

Roll back if needed: POST /policy/rollback to an archived valid version.

Old versions are never deleted; statuses are active, candidate, archived, rejected. Controlled policy reload is internal-only in v0.9 and disabled by default.

Audit & evidence review

Verify integrity: GET /evidence/verify and POST /audit/verify (per-file).
Export ranges: POST /audit/evidence with start_seq/end_seq; bundles include first/last hashes for out-of-band comparison; optional Ed25519 signing.
The JSONL projection is human-readable but not canonical; deleting it does not affect verification.
Corruption is reported, never silently repaired.

Backup and retention

Back up audit.wal, audit.log, approvals.sqlite and the policies directory together; evidence bundles reference the WAL ranges.
Store at least one copy off-box; run /evidence/verify after restore.
Retention policy is a deployment decision; v1 provides no auto-archival of evidence.

Control Plane usage

The Control Plane (port 3000) provides dashboards for health, runtime stats, logs, approvals, policy status and audit/evidence. It reads live endpoints through the server-side proxy; mock mode is explicit demo-only. Production mode requires HTTPS, admin credentials and NEXTAUTH_URL.