GovAI

Help center

What is GovAI?Contact for private pilotSign inSupport / contact

Support that behaves like the product

Search across help and documentation, follow guided triage paths, and copy the same commands we use in CI. Product reference lives in Documentation.

Status checks

Quick mental model: health means the process is up; readiness means dependencies (for example Postgres) are satisfied.

API

HTTP surface — use /health vs /ready deliberately.

Local

Local checks — curl probes and repo diagnostics from your machine.

CI

Artefact gate — digest + export cross-check, not smoke-only.

Humans

Contact — pilots, procurement, or a suspected incident.

Browse by topic

Each card opens the most relevant help or documentation page.

Getting startedHosted console walkthrough — API keys, first run, billing hooks.Local setup & healthAudit service liveness, readiness, and repo gates from your laptop.CI & GitHub ActionsArtefact-bound gate, digests, and why check alone is not enough.Audit ledger & evidencePOST /evidence, run IDs, and hash-chain behaviour.Compliance summaryVALID · INVALID · BLOCKED — one authoritative projection per run.Evidence exportsBundle hash, export JSON, and verify-evidence-pack.Dashboard & public siteDocs and help are static from Markdown; console routes require sign-in.DeploymentHosted backend probes, Postgres, Stripe webhooks.Security & trustTenant isolation, readiness vs liveness, trust center.TroubleshootingRed CI, BLOCKED verdicts, digest mismatches — guided flows.BillingStripe checkout, portal, usage reporting — when enabled.

What are you trying to do?

Pick a situation — we route you to the shortest path.

Interactive troubleshooting

Interactive troubleshooting

Symptom → verify command → expected signal → fix. Links jump to deeper docs.

Likely cause: Missing required evidence types and/or unmet approval / promotion prerequisites.

Verify

curl -fsS -H "Authorization: Bearer $GOVAI_API_KEY" \
  "$GOVAI_AUDIT_BASE_URL/compliance-summary?run_id=$GOVAI_RUN_ID" | jq '{verdict,missing_evidence,blocked_reasons}'

Expected: Structured JSON with non-empty missing_evidence or blocked_reasons

Next step: Replay the auditability scenario vocabulary for your policy pack, then append the missing events (see benchmarks/auditability-failures).

Animated explainers

Lightweight flows auto-advance — pause anytime. These mirror the same stages we reference in docs.

CI failure triage

Treat compliance-summary JSON as primary; logs only narrow the search space.

Evidence lifecycle

How an evidence event moves from emission to an auditable ledger record.

Compliance verdict flow

Prerequisites that must be satisfied before VALID is returned.

Export pipeline

From run_id to verifiable audit artefacts for buyers and regulators.

Deployment readiness

Binary up is not enough — /ready must reflect database and migrations.

Try consoles

GovAI try console
requires API key
Try thisCopy and run in your environment

Check audit service health

Differentiate liveness (process up) from readiness (dependencies such as Postgres).

Environment
export GOVAI_AUDIT_BASE_URL=http://127.0.0.1:8080
Command
curl -fsS "$GOVAI_AUDIT_BASE_URL/health"
Expected output
HTTP 200 — body varies by build

Next stepLocal checks guide

GovAI try console
local
Try thisCopy and run in your environment

Repository diagnostics

Run the same maintenance targets CI expects before a governance change lands.

Command
make oss-diagnostics
Expected output
PASS for checks relevant to your delta

Next stepContributing

Still stuck?

Send run_id (redacted), verdict JSON, and the failing command. For incidents include approximate time window (UTC).

← Back to home