alienctl/See proof

CONTROL FOR AI-AGENT ACTIONS · BUILT IN SWEDEN

Check an AI agent before it changes an external system.

alienctl checks the goal, identity, rules, and exact action. It saves the approved action before it sends it. It then saves the result. If the result is unclear, alienctl checks the provider without sending the action again.

See the GitHub test

WHAT WORKS TODAY

alienctl controls one type of GitHub status.

Repositoryone approved repository

Commitone exact 40-character commit ID

Statusone name, one approved result, and one short description

What alienctl does

  • checks the goal, authority, identity, policy, and action
  • saves the action before it sends it
  • sends only to an approved GitHub scope
  • runs locally or in the customer's environment; live mode is off by default

What alienctl does not promise

  • control of all agent tools or GitHub actions
  • an identity service
  • a guarantee that an external effect happens only once
  • correctness, safety, compliance, return on investment, or production readiness

HOW IT WORKS

Define → Check → Save → Send → Record → Verify

  1. 01

    Define

    State the goal and limits.

  2. 02

    Check

    Check identity, policy, and action.

  3. 03

    Save

    Save the exact approved action.

  4. 04

    Send

    Send only the approved action.

  5. 05

    Record

    Save the provider result.

  6. 06

    Verify

    Read the result if the reply is unclear. Do not send again.

prepared → dispatching → succeeded | failed | outcome_unknown
prepared → cancelled
ambiguous attempt → read-only reconciliation

LIVE TEST

A GitHub test created two approved statuses.

alienctl ran five test cases on the same public GitHub commit. GitHub created exactly two statuses. One reply was unclear. alienctl then read the status from GitHub without sending the action again. The proof also shows two test-tool failures.

Approved result

ALLOW → prepared → dispatching → succeeded → GitHub 201

Unclear result

dispatching → outcome_unknown → provider GET → reconciled

Provider POST count during reconciliation: 0.

See all test cases

TWO-WEEK PILOT

Test one real workflow and one external action.

We start with a technical review. We then decide if a pilot is a good fit. This site has no form. We handle email under the privacy notice.

Check pilot fit