PRODUCT · WHAT WORKS TODAY

Check, save, send, and record one external action.

alienctl checks the authority and exact action before it sends anything. It then saves the provider result. If the result is unclear, alienctl keeps that uncertainty.

The six main records

Mission

The Mission states the goal, limits, and success rule.

Mandate

The Mandate states what authority the agent has for this goal.

ActionIntent

The ActionIntent states the exact action, target, actor, expiry, and required evidence.

Decision

The Decision allows, limits, denies, or pauses the action for approval.

Execution

The execution record saves the approved action before alienctl sends it.

Receipt

The Receipt links the authority, decision, action, provider result, and evidence.

Lifecycle and failure behavior

prepared → dispatching → succeeded | failed | outcome_unknown
prepared → cancelled
dispatching | succeeded | failed | outcome_unknown → reconciled

Reconciliation is read-only. It appends observation evidence and does not rewrite a succeeded or failed result. No ambiguous attempt automatically retries.

The exact action that works today

Connectoralienctl.github.check-status

Capabilitygithub.check_status.apply

Repositoryone approved repository

Commitone lowercase 40-character commit ID

Statusone exact name and one approved GitHub state

Descriptionone short text value

Commands

alienctl connector execution apply --request ./execution.json --live
alienctl connector execution show --attempt-id ID --tenant TENANT
alienctl connector execution reconcile --attempt-id ID --tenant TENANT

Live mode also requires three server-side settings. Omitting the explicit CLI flag remains non-executing.

What this product does not claim

alienctl does not control all GitHub actions. It is not an identity service. It does not prove that code is correct or compliant. It does not guarantee that an external action happens only once.

See the GitHub test