SaibleDocs
Control

A change, approved by a second person

A change is proposed, replayed over past requests and approved. Every gateway then pulls it.

Describeor edit a ruleAReplayover yourrecorded requestsno figure is written by a modelProposenamesthe approverAReview queueimpact overthe last 30 daysApprovethe namedapprover + codeBB is never ASigned revisionone policy revisionSaible's keyGateways pullevery 60 ssignature checked↺ new records name the policy revision they were decided under;the next replay reads them
From a proposal to every gateway · person A proposes, person B approves
  • Policy revision
    the rules and their mode
  • Detection pattern
    patterns for your own identifiers
  • Workload label profile
    the labels that describe a workload
  • Application
    the approval of an application
  • Recommendation
    automatic ranking and alias order
  • Context manifest
    the context an application uses
  • Validation pack
    a sealed evaluation
  • Evaluation regression
    the figures of a rerun, acknowledged
  • Exposure report
    the sealed report
  • Policy pack adoption
    the rules of a pack, as a policy revision
  • Contract terms
    confirmed on Contracts
  • Policy signing key
    Saible's key ceremony
  • Tick: decided here
Changes that wait in the queue · each decision is a record in the evidence ledger
Steps
  1. 1On Policy, remove or add a rule, or describe the change in a sentence.
  2. 2Read the replay, which shows what would have changed over your recorded requests.
  3. 3Propose the change and name a second person to approve it.
  4. 4The approver opens Review queue and clicks Approve, or Reject with a reason.
  5. 5On Gateways, confirm that the new policy revision reaches every gateway instance.
For your agents

This topic is also documented as Agent Skills that your agents can load: policy, review-queue, recommendations, policy-registry, code-scan, write-back. Request them from Saible.

Next · Control Plane · EvidenceEvidence ledgers, checks and the evidence pack →