Dara

Governance

Stop it before the money.

A policy is a document attached to a project. It is enforced at four points — the first of them before any provider is called.

Committed defaults

Enforcement points

4 checks per run
1Pre-flight

Before any provider is called

Cost is estimated from the model registry and compared with budget. Providers, models, modality, aspect ratio, step, variant and attempt limits are all checked. A run that would exceed budget is rejected at zero cost.

2Pre-step

Before every provider step

Each step is re-checked against the per-step ceiling and the remaining run budget, so a fallback route cannot quietly overspend.

3Post-step

After quality assurance

The vision QA score is compared with the required minimum. Whether a failure blocks or merely warns is itself part of the policy.

4Pre-publish

After embedding, before delivery

Manifest embedding and share redaction are verified before anything reaches a client, so a disclosure cannot leak what policy withheld.

pol_standard

Standard

Advisory QA

Budget

Per step
$0.5000
Per run
$2.00
Per day
$1.00
Overrun tolerance
25%

Shape

Max steps
6
Max variants
4
Max attempts
3
Max duration
10s

Providers and models

Allowed providers
openaireplicate
Denied providers
none
Allowed models
*
Modalities
image
Aspect ratios
1:12:33:2

Quality

Minimum QA score
0.75
QA requiredBlock on QA failureApproval required before publish

Disclosure and retention

Embed manifestRedact brief on shareStrip parameters on share
Asset retention
365d
Manifest retention
2555d

The live policy engine is unreachable, so these are the defaults committed in the API. Values are copied from source, not invented. Studio simulates the selected policy against your brief before anything is spent.