Configuration & API
Per-project configuration
Everything about the analysis model is tunable per project. Settings are stored as sparse overrides: you change only the values you care about, and everything you leave alone keeps tracking the product defaults across releases. This means a new release can improve the defaults without silently overwriting the choices you made.
The configuration is grouped into the following areas.
Scoring thresholds and health weights
The six health-score weights (structural, SLA, automation, governance, actor, path) and the thresholds that drive each sub-score. The weights must sum to 1.0, and the complexity and risk-tier boundaries must stay ordered. This is where you calibrate the model to your own definition of a healthy process.
Anti-pattern thresholds
The trigger points for each anti-pattern: god-stage ratio, spaghetti-flow complexity, bottleneck-actor ratio, SLA-blindspot gap, and manual-island length.
Portfolio thresholds
Clone-similarity threshold, automation maturity-tier boundaries, and the cutoffs for weak dimensions and critical health.
Standards criteria
The numeric bar for each control in the ISO 9001, COBIT, Lean, Six Sigma, and ITIL audits, plus the Pass and Partial thresholds that decide the overall status.
Frameworks and dimensions
Which compliance frameworks the standards audit runs, which regulatory frameworks the mapping considers, and which benchmark dimensions the benchmark scores.
Narrative parameters
- Industry: a declared sector that anchors benchmarking.
- Executive audience:
cto,coo, orboard, which shapes the tone of executive-facing narrative. - Redesign appetite:
conservative,balanced, oraggressive. - Prompt parameters: output language, a glossary of preferred terms, and a free-text addendum applied to the narrative agents.
Configuration is read and written through the config endpoints below, and surfaced in the Settings screen of the web application.
REST API
The web application is a client of this API. Every capability is available programmatically. The base path is api/insight, with related surfaces under api/enrich, api/redesign, and api/chat.
Analysis
| Method and path | Purpose |
|---|---|
POST /api/insight/analyze | Start an analysis job and receive a jobId |
GET /api/insight/projects/{projectId}/processes | List the processes in a project |
GET /api/insight/jobs/{jobId}/stream | Subscribe to the analysis progress stream (SSE) |
GET /api/insight/jobs/{jobId}/portfolio | Get the portfolio-level result |
GET /api/insight/jobs/{jobId}/processes/{processId} | Get a single process result |
GET /api/insight/jobs/{jobId}/status | Get job status |
GET /api/insight/projects | List available projects |
AI enrichments
| Method and path | Purpose |
|---|---|
POST /api/enrich/{jobId}/{processId}/benchmark | Regenerate the industry benchmark for a process |
POST /api/enrich/{jobId}/{processId}/regulatory | Regenerate the regulatory mapping for a process |
POST /api/enrich/{jobId}/{processId}/redesign | Regenerate redesign recommendations for a process |
POST /api/redesign/{jobId}/{processId} | Regenerate the redesign plan |
POST /api/chat/process | Chat with a single process |
POST /api/chat/portfolio | Chat with the portfolio |
Configuration
| Method and path | Purpose |
|---|---|
GET /api/insight/projects/{projectId}/config | Read the effective config plus the project's overrides |
PUT /api/insight/projects/{projectId}/config | Save a sparse override document |
All endpoints require authentication and act on behalf of the signed-in user. See the Installation guide for the auth model.