Owner identity guide

0.3.4 update: existing owners keep their saved wallet; see RELEASE_NOTES_0.3.4.md at the package root. The new-key form starts blank.

AIL 0.3.3 Owner Identity Guide

Purpose

AIL Owner Console 0.3.3 lets Wakely Wolf create a persistent Ed25519 owner key, protect its private half with a password, sign an AIL owner passport, and produce one JSON identity packet for another AI to inspect.

First use

  1. Double-click OPEN_AIL_OWNER.bat or open owner_app/index.html.
  2. Confirm the name and principal shown on screen.
  3. Choose a unique password containing at least 12 characters.
  4. Select Generate protected owner wallet.
  5. Download the private wallet and signed AI identity packet. The public key file is optional.
  6. Store the wallet and password separately in safe locations.
  7. Upload only AIL_Identity_Packet.json to another AI.

What the files mean

File Share it? Purpose
AIL_Owner_Wallet_PRIVATE.ailwallet.json No Encrypted private signing key
AIL_Identity_Packet.json Yes Public claims, passport, key, signature, and verification instructions
ail-owner.json Yes Public-key anchor intended for a controlled website

Losing the wallet or its password means losing the ability to make new packets with that key. Anyone who obtains both can impersonate the owner key.

What verification proves

A successful verification proves that the packet was produced by whoever controls the private key corresponding to its public key and that its signed claims were not changed afterward. A signature-only check remains ail:self_asserted_key. A verified HTTPS anchor adds a domain-key association, but does not independently verify Wakely Wolf as a person.

The included grant means full access to the AIL language project. It does not grant access to another company's accounts, tools, hidden prompts, data, or security boundaries.

Stronger identity anchoring

A website is optional. Leave the URL blank until AIL has a separate address under your control. Later, use the same saved wallet to sign a fresh packet with that AIL URL and download its matching ail-owner.json public key file. Publish only that public file at the declared HTTPS address. Do not publish the private wallet or its password.

Verification limits in 0.3.1

Packet verifiers reject changes to the unsigned outer metadata and instructions by comparing them with expected values. A successful signature alone does not verify the person's identity or grant access to another system. The 0.3.1 verifier did not fetch an anchor; 0.3.2 adds an explicit HTTPS CLI check.

Domain key check in 0.3.2

Publish ail-owner.json at the exact HTTPS URL in the signed packet. The command-line verifier accepts a URL the recipient chose independently and fetches the file over HTTPS without following redirects. A key match means that the HTTPS origin serves the matching public key; it does not establish the named person's legal identity. Comparing a downloaded or uploaded file without verifying its origin remains a self-asserted key check.