SSigillum DocsOpen dashboard

Controls

Policy and Budget Controls

Sigillum should use one shared policy model across personas: recommendation thresholds, optional score ceilings, and spend caps before payment happens.

Shared policy model

The policy story should stay consistent across GitHub maintainers, indie builders, and autonomous agents. Different personas can package the controls differently, but the underlying rule semantics should stay the same.

Risk gates

The minimum serious risk gate set is recommendation threshold plus optional maximum Sigillum Risk Score.

  • Always stop on `block`
  • Optionally fail or pause on `warn`
  • Optionally enforce a maximum risk score

Budget gates

The quote is the natural budget checkpoint. Spend policy should be able to stop a risky action before x402 payment happens.

  • Max spend per action
  • Daily or monthly caps
  • Persist why a quote was skipped or blocked by budget

Related

Dashboard policy surface