Configuration & API
Per-project configuration
Logic Guard has two per-project surfaces, both stored as sparse overrides.
Ruleset
Which of the 143 baseline rules are enabled, and per-rule severity reclassifications, organized by section. This is the surface managed from the Rules screen and covered in Customization.
Scan configuration
Config name scan. This carries:
- Strictness:
conservative,standard, orthorough. - Section context: a per-section note that scopes a checker's judgment.
- Prompt parameters: output language, a glossary of preferred terms, and a free-text addendum applied to the checkers.
REST API
The base path is api/governance. The web application is a client of this API, so every capability is available programmatically.
Scanning
| Method and path | Purpose |
|---|---|
POST /api/governance/scan | Start a scan and receive a jobId |
GET /api/governance/jobs/{jobId}/stream | Subscribe to the scan progress stream (SSE) |
GET /api/governance/jobs/{jobId}/sections/{sectionId} | Get a section's findings |
GET /api/governance/jobs/{jobId} | Get job status |
GET /api/governance/sections | List the available checker sections |
GET /api/projects | List available projects |
Ruleset and configuration
| Method and path | Purpose |
|---|---|
GET /api/governance/projects/{projectId}/rules | Read the per-project ruleset |
PUT /api/governance/projects/{projectId}/rules | Save the per-project ruleset |
GET /api/governance/sections/{sectionId}/baseline-rules | Get the baseline rule catalog for a section |
GET /api/governance/projects/{projectId}/scan-config | Read the effective scan config plus overrides |
PUT /api/governance/projects/{projectId}/scan-config | Save a sparse scan-config override |
All endpoints require authentication and act on behalf of the signed-in user. See the Installation guide for the auth model.