SECURITY · CURRENT LIMITS

Run alienctl in a local or customer-controlled environment.

The normal API listens only on the local computer. It does not include general login for a shared network. The installed customer profile adds controls for one use case. It is not a general enterprise service.

Credential and network rules

The customer creates and controls the limited GitHub credential.
alienctl loads the token only after it saves the approved action.
alienctl never accepts the token in command arguments or request JSON.
alienctl does not save the token in records, logs, or public proof.
Live mode uses one fixed GitHub HTTPS address. It has a five-second timeout, no redirects, and a 64 KiB response limit.
Test mode accepts only a local loopback address. It sends no Authorization header and reads no token.

Reference data inventory

Fields required by the demonstrated effect
Data	Purpose	Stored	Public proof
Mission/Mandate references and state	authority reconstruction	yes	synthetic references only
Actor and identity binding	attribution and verification	bounded evidence	synthetic metadata only
Policy ID and immutable version	decision reconstruction	yes	synthetic value
Repository, SHA, context, state, description	exact effect	yes	live sandbox scope
Request hash, correlation and idempotency IDs	fencing and reconstruction	yes	safe synthetic values
Bounded provider classification/status ID/result hash	result and reconciliation	yes	live bounded evidence
Credential, raw response body, raw prompts/source	not receipt data	no	never

What alienctl handles

Handled

wrong authority, identity, tenant, policy, or action scope
duplicate or changed requests
cancellation before the action starts
provider failure, timeout, unclear reply, or failure to save a result
restart without sending the action again
redirects, large replies, unsafe local addresses, and tokens in evidence

Not proven

security of a compromised computer, provider, or identity system
prevention of every bypass
cryptographic proof that a record cannot change
code correctness, production safety, compliance, or customer readiness
login for a shared network or isolation for a hosted service

Report a security problem

Email hello@alienctl.com. Above Sea Level AB monitors this address for security reports. We aim to confirm receipt within three business days. This is not a promise to fix the problem within three days.

Name the affected part or version. Explain the impact. Give the smallest safe way to reproduce the problem. Do not send credentials, tokens, customer data, or private source. Do not test production or the public test repository without written approval. Give us reasonable time to investigate before you publish the report.