15-Minute First-Boot Setup Guide
After signing in as admin, follow this exact 6-step dependency order so your engineering team can submit their first governed change order and read-only query without hitting 1001 VALIDATION_FAILED:
- Add an AI Provider (
/admin/review-engine/providers): Configure an HTTPS OpenAI-compatible cloud endpoint (defaultanonymized profile) or an internal RFC1918 vLLM/Ollama endpoint (sanprofile forSAN-2B/SAN-4B/SQL-Audit-Nano), run Test Connection, and enable it. - Enable Built-in Skills & Create a Rule Set (
/admin/review-engine/skills->/admin/rule-sets): Enable baseline skills (builtin.dml-require-where,builtin.forbid-truncate,builtin.ddl-require-primary-key,builtin.max-affect-rows) and combine them into a published Rule Set. Everychange_reviewflow requires a non-emptyrule_set_id. - Register Target Datasources (
/admin/datasources): Create dedicated read-only (yearning_ro) and execution (yearning_exec) DB accounts (see Datasources & DB Grant SQL), fill mandatoryversion_constraint(e.g.>=8.0,<9.0), and verify connection + identity fingerprint. - Create Users & Approval/Query Flows (
/admin/users->/admin/flows): Configurechange_review(1..Nserial datasource stages,1..10approval steps, executors) andquery_access(datasources, optionalcan_export, sensitive column masking). - Grant Flows via Permission Groups (
/admin/permission-groups): Add developers/DBAs to groups and attach the authorized flows. Note that built-inadmindoes not implicitly override frozen business flows. - Configure
public_base_url& Notifications (/admin/settings/general&/notifications): Set your public HTTPS URL (used for OIDC callbacks and order links) and configure Email / DingTalk / Feishu / Slack rules.