SaibleDocs
Control

A change, approved by a second person

Propose, replay over what already happened, approve. Then every gateway pulls it.

Describeor edit a ruleAReplayover yourrecorded requestsno model writes a figureProposenamesthe approverAReview queueimpact overthe last 30 daysApprovethe namedapprover + codeBB is never ASigned bundleone revisionSaible's keyGateways pullevery 60 ssignature checked↺ new records name the revision they were decided under;the next replay reads them
From a proposal to every gateway · A proposes, B approves
  • Policy revision
    the rules, and their mode
  • Detection pattern
    your own identifiers
  • Workload label profile
    what a workload does
  • Application
    a tool's approval
  • Recommendation
    auto ranking, alias order
  • Context manifest
    what a tool is wired to
  • Validation pack
    an evaluation, sealed
  • Evaluation regression
    a rerun's figures, acknowledged
  • Exposure report
    the report, sealed
  • Policy pack adoption
    a pack's rules, as a revision
  • Contract terms
    confirmed on Contracts
  • Bundle signing key
    Saible's key ceremony
  • Tick: decided here
What waits in the queue · each decision is a ledger record
Do it
  1. 1On Policy, drop or add a rule, or describe the change in a sentence.
  2. 2Read the replay: what would have changed over your recorded requests.
  3. 3Propose it, naming a second person to approve.
  4. 4The approver opens Review queue and clicks Approve, or Reject with a reason.
  5. 5On Gateways, watch the new revision reach every instance.
For your agents

This topic is also written as Agent Skills your agents can load: policy, review-queue, recommendations, policy-registry, code-scan, write-back. Ask us for them.

Next · Control Plane · EvidenceChains, checks and the evidence pack →