INDEPENDENT AGENT RELEASE AUTHORITY

Make every AI release earn production.

Scalarion binds the exact agent — its models, prompts, tools and permissions — to evidence, policy and an accountable human decision, then lets every pipeline, cloud and platform enforce the same signed authorization.

Build, check and see the verdict free — no account. Signing in is only to keep what you build.

ONE SUBJECT · ONE ENVIRONMENT · ONE EXPIRY · ONE CURRENT DECISION

02 · THE MUTABLE APPROVAL GAP

Your approval is attached to a ticket. Production receives a different object.

The ticket is approved, the eval dashboard is green — and the release presented to production is no longer the release that was reviewed. Both lanes below are watching the same mutation you trigger above.

03 · WHERE SCALARION SITS

One authority plane across a heterogeneous agent estate.

Every system below owns a fragment — source, framework, model, tools, evidence, delivery. None of them answers whether this exact agent release may act in this environment, now. Scalarion owns only that relation. Provenance and attestations flow in as evidence; the authorization is a separate, revocable decision.

1. 1 · CREATE

   Source, agent framework, model routing, tools and data. Many owners, all mutable.

2. 2 · PROVE

   SLSA provenance, evals, security and policy checks — consumed as evidence, never as the authorization itself.

3. 3 · DECIDE

   SCALARION

   Exact subject + policy + accountable human authority, sealed as a release-authorization predicate in an in-toto Statement, carried by a DSSE-compatible envelope.

4. 4 · ENFORCE

   CI, GitOps, Kubernetes admission or platform pre-deploy hook verifies and admits or denies.

5. 5 · OPERATE

   Change, drift and incident watchers suspend, revoke or narrow authority when facts change.

6. 6 · VERIFY

   Audit, procurement, insurer or customer verifies the same envelope offline, without trusting Scalarion.

• Generic CLI / API — any stackDESIGN PARTNER
• GitHub Actions / deploy gateDESIGN PARTNER
• GitLab · Azure DevOps · Jenkins · ArgoNEXT
• Trust network · third-party verifiersEXPLORING

GitHub deployment protection rules are a GitHub public-preview feature; private and internal repositories require GitHub Enterprise. The generic CLI/API path works in any CI. Availability labels come from one claim registry — nothing renders AVAILABLE without proof.

05 · ONE DECISION PROPAGATES EVERYWHERE

A decision the delivery system can act on.

The UI is not the enforcement point. It issues the artifact the enforcement points consume — the same state, sequence and reason code everywhere. All five surfaces below derive from the decision you made above.

06 · CONTINUOUS REAUTHORIZATION

Authority expires when its facts stop being true.

Your earlier tool-scope expansion traced this exact path — only the affected dependencies re-open, not the whole audit:

1. tool scopesecurity evidence: missing for payments
2. policyquorum required: risk + security
3. authorizationsuspended for the new subject
4. re-decisionnew sequence · scoped conditions · old decision superseded

07 · ORGANIZATIONAL RELEASE SYSTEM

From one protected release to the operating system for agent authority.

The portfolio answers four questions — and keeps authorization and deployment as independent axes. No composite risk score.

ILLUSTRATIVE PORTFOLIO · INTERACTIVE SAMPLE — NOT LIVE TELEMETRY

08 · PORTABLE TRUST

Verify the decision without trusting the dashboard — or Scalarion.

The authorization is a release-authorization predicate in an in-toto Statement, carried by a DSSE-compatible envelope, signed with an ECDSA P-256 / SHA-256 key backed by AWS KMS. Copy the sample — its subject digest is the one this page computed — and inspect it anywhere.

Raw prompts and traces need not be disclosed: hashes and scoped references are sufficient for third-party verification. SLSA provenance enters as evidence; it is never the authorization.

{
  "_comment": "INTERACTIVE SAMPLE — locally generated, unsigned",
  "payloadType": "application/vnd.in-toto+json",
  "payload": {
    "_type": "https://in-toto.io/Statement/v1",
    "subject": [
      {
        "name": "underwriting-triage",
        "digest": {
          "sha256": "c07b0ae8bdb152c3557af8a5d9fc20c4eef27f134aaf8c2d9b5a4a428f736bf7"
        }
      }
    ],
    "predicateType": "https://scalarion.dev/release-authorization/v1",
    "predicate": {
      "environment": "prod-eu-1",
      "approver": "role:head-of-underwriting",
      "conditions": [],
      "notAfter": "2026-09-14T00:00:00Z",
      "revocable": true,
      "decisionSequence": 4106
    }
  },
  "signatures": [
    {
      "keyid": "kms-ecdsa-p256 (sample — unsigned in this prototype)",
      "sig": null
    }
  ]
}

1 · fetch /.well-known/scalarion-trust.json
  2 · match the envelope keyid to a published key
  3 · verify the signature against that key alone