EXPERIMENTAL REFERENCE PROJECT v0.3.4

Make AI messages readable, testable, and accountable.

AIL is a small structured language for expressing facts and queries. Its owner kit adds locally signed identity packets that a receiver can verify.

A research stage project. AIL does not train models or grant permissions on other platforms.

message.ailAIL / 0.2
// A fact expressed as a relation
AIL/0.2
M{
  id=f001;
  act=A01;
  registry=ail-core:0.2;
  body=P(ail:earth,ail:orbits,ail:sun);
  conf=1.0;
}
● Reference examplefact_query.ail
01 Human-readable syntax02 Python validation03 Signed owner packets04 Cross-language verification
THE IDEA

One format. Clear boundaries.

AIL separates a message’s meaning from the question of who signed an ownership claim.

{ }

Describe

Write facts and queries in AIL’s canonical message form. The reference kit includes a parser, concept registry, normalizer, and examples.

AIL 0.2 language
✓

Validate

Check syntax and registry use before another system acts on a message. A valid request is still data; a receiving application must authorize any action.

Python reference tools
⌁

Verify

Create an owner wallet locally and sign a public packet. Python and JavaScript verifiers check the signature and required packet fields.

AIL 0.3 owner kit
INTERACTIVE EXPLORER

See the message structure.

Switch between supplied examples and inspect each field. This browser explorer is an explanation of the format; run the downloaded Python tools for authoritative validation.

FIELD GUIDE

A fact about the Earth

TRUST MODEL

A signature answers a specific question.

It can show that a packet was signed by the corresponding private key and that signed contents were not changed. A signed packet begins with a self asserted identity claim. An independently fetched HTTPS anchor can associate that key with control of a domain.

Neither check proves a person’s legal identity or overrides a platform’s security rules.

01
Signed packetKey control and signed-content integrity
02
Optional domain anchorAssociation with control of an HTTPS origin
03
Receiving systemDecides what actions, if any, are permitted
FREE EXPERIMENTAL DOWNLOAD

Try the AIL developer toolkit.

Experimental 0.3.4 includes the Python parser and validator, a local signing and verification console, source code, examples, documentation, and tests. It is designed for developers and technical testers.

It is not a standalone AI and does not automatically connect AI services. The language format remains AIL/0.2.

ZIP · 292 KiB · No payment required. Release notes · Download checksum

Extract the ZIP, then open OPEN_AIL_OWNER.bat on Windows or owner_app/index.html in your browser. Existing owners: use step 2 with your saved wallet to retain your key.

VERSIONExperimental 0.3.4
CREATORWakely Wolf
CHECKS34 Python tests passed

JavaScript cryptography, console-handler, and compatibility checks also passed. Full browser coverage and an independent security audit remain outstanding.

Keep your private wallet and password private. This download contains neither. A signature alone does not establish the signer's identity.

Free to download. This is not an open-source license; see LICENSE.txt for the existing terms.

GOOD TO KNOW

Questions before you begin.

Does this website connect AIL to ChatGPT or Grok?

No. The website introduces AIL. Integrations require an application or API that translates between AIL and each platform’s supported tool interface.

Is the public ownership anchor live?

The existing public key file is available at /.well-known/ail-owner.json and is preserved in this update. Use an independently trusted fingerprint or verified HTTPS anchor when recognizing a known key. Domain control does not prove legal identity.

Can I use AIL in my own product?

The experimental kit is available as a free download. No open-source or product-integration license is granted by the download. Consult LICENSE.txt; product integration requires permission from the project owner.

Does a valid AIL message make an action safe?

No. Parsing and validation check form and registered terms. The receiving system remains responsible for authentication, authorization, and safety decisions.