HUMΛN
Ask HUMΛN

Ask how HUMΛN governs an agent.

No account is required and no identity is collected. The question and the page path are logged with the session so answers can be reviewed. The deployment credential stays on the server. Sessions expire with the public Q&A contract.

HAIO · Human + AI Orchestration

What Companion will not do

A plaintext, enforceable list. Not marketing — engineering constraints.

Connect your AI host Open the Console

A plaintext, enforceable list. Not marketing — engineering constraints.

Prohibitions

✗ Send any message without human approval

Social media posts, emails, Slack messages, and SMS require explicit human approval for each instance. Draft approval ≠ send permission.

Technical proof: Companion's connector system gates write operations behind an approval token that can only be issued by an authenticated human session.

✗ Make payments or financial transactions

Companion cannot authorize spending of any kind. No invoice payment, no subscription purchase, no transfer.

Technical proof: Payment connectors are write-blocked at the protocol level. Companion can read invoices; it cannot approve them.

✗ Impersonate a human

When Companion engages on any platform, it discloses it is HUMΛN Companion — an AI agent. This is non-negotiable.

Technical proof: Social connectors prepend the Companion identity disclosure string to every draft before it reaches the HITL approval queue.

✗ Access data you have not connected

Companion only reads from integrations you explicitly authorized. It cannot crawl your file system, access tools you have not connected, or read data from deleted connections.

Technical proof: OAuth scopes are requested at minimum necessary level. Companion holds no persistent credentials — it calls your vault for each action.

✗ Delete data

Companion cannot delete emails, files, database records, or any other data. All deletions require a separate human action outside Companion.

Technical proof: Write connectors expose only create and update operations. Delete endpoints are not exposed to the Companion runtime.

✗ Share your data with third parties

Companion does not sell or share your personal or business data with third parties. We don't monetize your data — we monetize enterprise access to Companion's capabilities.

Technical proof: All data processing happens within your authorized connector scope. No data is logged to external analytics providers without your explicit opt-in.

✗ Act after you revoke access

Revoking a connector integration or pausing Companion stops all related agent activity within seconds.

Technical proof: Connector credentials are checked against your vault on every invocation. A revoked credential returns 401; the action is aborted and logged.

What happens if you disagree

If Companion ever violates these constraints, that is a bug — not a feature. Report it at security@haio.run. We will fix it, document it publicly, and update this list with what changed.

Build with HUMΛN

Agent authority