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 languageAIL 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.
// 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;
}“Earth orbitts the Sun” leaves a receiver guessing. AIL’s strict registry check can flag the undefined term before your application processes it.
AIL/0.2 M{id=demo1;act=A01;registry=ail-core:0.2;body=P(ail:earth,ail:orbitts,ail:sun);conf=1;}{
"id": "demo1",
"act": "A01",
"registry": "ail-core:0.2",
"body": [
"ail:earth",
"ail:orbitts",
"ail:sun"
],
"conf": 1
}Both approaches catch this error when their vocabulary rules are enforced. AIL supplies conventions for acts, propositions and display aliases; a JSON application can implement equivalent rules.
Recorded Python results, not live browser validation. No AI service is called. A structurally valid message can still be false.
Read the comparison and alias example · Inspect test evidence · Browse source
AIL separates a message’s meaning from the question of who signed an ownership claim.
Write facts and queries in AIL’s canonical message form. The reference kit includes a parser, concept registry, normalizer, and examples.
AIL 0.2 languageCheck 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 toolsCreate an owner wallet locally and sign a public packet. Python and JavaScript verifiers check the signature and required packet fields.
AIL 0.3 owner kitSwitch between supplied examples and inspect each field. This browser explorer is an explanation of the format; run the downloaded Python tools for authoritative validation.
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.
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
Check permitted use before experimentation. 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.
Recorded September 27, 2026. JavaScript cryptography, console-handler, and compatibility checks also passed. Inspect output and reproduce the checks. 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; read the license and permitted uses.
No. The website introduces AIL. Integrations require an application or API that translates between AIL and each platform’s supported tool interface.
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.
The experimental kit is available as a free download. No open-source or product-integration license is granted by the download. The existing notice does not expressly grant an evaluation license. Read the permitted-use summary and original terms, then obtain written permission for experimentation or integration. A public contact channel is not currently listed.
No. Parsing and validation check form and registered terms. The receiving system remains responsible for authentication, authorization, and safety decisions.