Skip to content
Documentation

Everything there is to read, in one place

We say «the Standard is published» on four pages, and a careful reading asked us where. Here: the full format specification, the guide for beginners, the public repository, and the site itself in markdown.

The format Standard

It is the complete specification of the Markdown dialect IllAIra files use: the type tag on the first line, the permission zones, the attention anchors, the grammar of modules, nuclei, routines and logs, the sub-topics of diaries, deferred tracing. It is written for whoever implements a parser — in English, as it was born — and it says what the program accepts and what it rejects. It is the document the app abides by: when the two disagree, that is a defect, and we fix it.

IllAIra_Markdown_Standard_v1.13.md

Size
87 054 bytes · UTF-8 text, in English
SHA-256 fingerprint
f2d7182553004f601a3077ecffc862d0f0d584330a12a5833f10ff0ad2160699

Which parts of all this the app already reads, and which it treats as plain text, is written next to the examples, on the page that shows a file line by line.

Anatomy of a file

The version is in the file name, and it is the Standard’s own: a new version is a new file, with a new address. A link saved today still delivers this one.

There's also a page just for this, meant for whoever implements a parser and wants the short address to bookmark.

The Standard, at /standard

What is open, and what is filed

The format is published and can be used without asking anyone: a file written to the Standard is yours, opens in any editor and keeps working even if IllAIra shut down. The method — the Continuity Layer — is the subject of a filed patent application: patent pending. They are two different things. The first concerns how a file is written; the second concerns the method, not what you write inside it.

The code of the App and the WebApp is not published. We say it here because it is fair to know before looking for a source: what is public is the format, its specification and the documentation. What can be verified without the source is in the open anyway — the package fingerprint, the permissions it asks for, the signature — and the files remain yours in any case, which is the part that matters to whoever uses the method.

The guide for beginners

App and WebApp explained with the real names of the buttons, then the zones and where to upload the files. It is the same guide you find on «How it works» and on the download page, in five languages.

Download the user guideVersion 1.4 · PDF

WebApp and App, step by step. Names in bold are the ones you see on screen.

Language

The public repository on GitHub

The protocol has a public repository: the specification, how it works, the philosophy, the stress tests, the licence. It holds documentation, not the code of the apps.

The most up-to-date copy of the Standard is the one on this page: the repository is updated by hand and can fall a few versions behind. If you see two different numbers, the downloadable file above is the one that counts.

Open the repository

github.com/IllAIra-Labs/IllAIra-Continuity-Layer-Protocol

The pages that explain

The Standard says what the parser accepts. The in-depth pages say why it is made this way, with the real examples: how a file is built line by line, the permission zones one by one, where to upload model by model, and the three pages that answer whoever thinks they already have the same thing — a Skill, a graph of notes, a structure that would suffice.

The in-depth pages

And the most common objections — whether the model honours it, the cost in tokens, «it’s just markdown», lock-in, the headlines outside of here — each have a written answer, in a single list.

The objections, and where they are already answered

For whoever reads with a model

Every page of the site also exists in markdown, at the same address with «.md» at the end, and the index of everything is at illaira.com/llms.txt, in the site’s five languages. Same text, a fraction of the tokens. Nothing hidden on the page: the pointer is in the footer, in robots.txt and in a link declared in the head of every page.

The markdown index