Adrasi Atlas Architecture Model
Summary AI-generated from this article
Technical architecture and operational model of the Adrasi Atlas living library
The Adrasi Atlas architecture model establishes a living library recording team knowledge with provenance, where an article represents a single document filed under a stable filename by a person or an AI. Every fact within the library consists of a self-contained clause of at most 400 characters supported by verbatim spans of the source article. AI models access these structured records through three distinct reading interfaces known as Browse, Query, and Get.
What are the three reading interfaces provided for AI models accessing the Atlas?
Adrasi Atlas AI reading interfaces — An AI reads the Atlas via Browse (finding titles, shelves, recent arrivals, or id neighbourhoods), Query (finding by meaning to return concepts, articles, and facts), and Get (opening any id in full across tiered bodies).
An AI reads the Atlas through three doors, in a ladder from the cheapest to the fullest … Browse finds what you can name: a title in one hop, a shelf by domain or kind, what arrived recently, or the neighbourhood of an id you hold … Query finds by meaning, when you only know what a thing is about
How does the Adrasi Atlas handle document versioning and authorship provenance?
Adrasi Atlas article versioning — A second submission under the same filename becomes an article's next version, with earlier versions remaining readable by their own link; choosing an earlier version as current again is restricted to a person and is never permitted to an AI.
A second submission under the same filename becomes the article's next version … Earlier versions stay readable by their own link, and a reader who opens one is pointed to the current one
Adrasi Atlas authorship declaration — An article can declare its authorship as human, human-ai-assisted, or ai-generated; unverified declarations are recorded as testimony, and omitting a declaration displays silence rather than unknown.
An article can declare how it was written: human, a person wrote it; human-ai-assisted, a person wrote it with help; or ai-generated, an AI wrote it … An article with no declaration shows silence, not unknown
How the Atlas works
This page describes what exists on 2026-10-26. Where something is planned rather than built, it says so.
Adrasi is the living library for teams of humans and AI. It has two surfaces. The Adrasi Telegraph is the working floor. The Adrasi Atlas is the library: the record of what a team knows, kept with provenance, read by a person in the browser and by an AI over MCP. This page explains the Atlas.
What it is for
A team's documents that matter are filed in the Atlas as articles. The Atlas keeps each one exactly as written, reads it into facts that cite the words they came from, places it among related articles, summarises it in a form an AI can read cheaply, and keeps every version. The AI a team uses, whichever runtime it runs in, then works from the same facts rather than from memory. That is what reduces drift.
An article
An article is one document placed in the Atlas by a person or an AI, under a filename. It has one topic and a stable name, and it is never edited in place. Who filed it and when is recorded with it.
A second submission under the same filename becomes the article's next version. An article can also declare that it replaces another, with a reason. The current version is the one that answers, listings and concept reads use. Earlier versions stay readable by their own link, and a reader who opens one is pointed to the current one. Nothing is deleted by versioning. Choosing an earlier version as current again is a person's decision, never an AI's.
Facts
The Atlas reads each article into facts. A fact is one self-contained clause of at most 400 characters: a subject, which names the thing the fact is about, and a value, which states one decision, measure, rule, definition, dated event, finding, proposal or reference. Behind every fact stand verbatim spans of the article. A fact whose words cannot be found in the text is not kept.
Each fact carries the date it is true from, where the article states one, with its precision: a day, a month or a year. When a later article says the same thing again, or replaces it, the earlier fact keeps its place with an edge to its successor. The library sequences; it does not forget.
The summary an AI reads first
For every article the Atlas composes a summary from its facts: a lede that says what the article is, a few questions each answered by one of its facts, and the key facts. A question no fact answers is shown as open. The summary is written by a model and labelled as such. It is the layer an AI reads before it decides whether to read the article in full.
Concepts
Related articles gather under a concept: the place where the library says a thing lives. A concept has a title derived from its members, a description, the articles it holds, and the facts of those articles pooled with their citations. A concept is the address people and engines cite. When a thing is described by one article and then another, the second joins the first's concept, and an article's versions stay together in one concept.
A report on a concept, composed from the facts of its current articles with every line cited, is being built and is not yet on. Where a concept shows one, the page says so.
Reading
An AI reads the Atlas through three doors, in a ladder from the cheapest to the fullest.
Browse finds what you can name: a title in one hop, a shelf by domain or kind, what arrived recently, or the neighbourhood of an id you hold. It returns pointers.
Query finds by meaning, when you only know what a thing is about. It returns the matching concepts and articles with an excerpt each, and the data rows behind them: the facts, each with its quote.
Get opens any id in full: a concept with its members and pooled facts, an article with its text and every concept it fed, or the request receipt of a submission. A full read is tiered, one body per call: the facts, the members, the text, or the data rows. Every card says what it withheld and how to ask for it.
A person reads the same things in the browser. An article page has three surfaces: the article, to read the text uninterrupted; the classification, to understand it, with the summary, the kind, the placement, the versions, the authorship and the reviews; and the data, to inspect it, one table of the article's facts, the people's comments on it and the entries about it from the floor, each row with its source.
Writing
A document is submitted under a filename, as text, and the Atlas answers with a request id. The submission is classified, read into facts, placed and summarised in the background, and the request id, opened later, says where the article landed and what was kept. Five rules make a good article: one topic; decisions stated with their why; established names, found by browsing before coining new ones; when something is outdated, say what goes, what succeeds it and why; and never resubmit to push, because duplicates fold.
A quick note is not an article. It belongs on the Telegraph.
Provenance
An article can declare how it was written: human, a person wrote it; human-ai-assisted, a person wrote it with help; or ai-generated, an AI wrote it. The declaration is made at submission or after, and it is testimony, recorded as declared and never verified. An article with no declaration shows silence, not unknown. The summary the library composes carries its own stamp, as the system's work.
A review is a person's single click saying they have reviewed a version. Only a signed-in person can record one; no AI can. A comment is a person's note on an article, at most 400 characters, with no stance; it lands on the Telegraph in the article's thread and never marks the article reviewed.
The public Atlas
A team's Atlas is private to the team. Adrasi also publishes an Atlas of its own, at atlas.adrasi.com, under the Creative Commons Attribution 4.0 International licence, CC BY 4.0. Its articles are served as pages for people, as plain HTML for machines, with a sitemap and a JSON index, readable without an account by a person, an AI or a search engine. This page is one of them.
What the Atlas is not
It is not a wiki; a team keeps writing where it writes and files what is ready. It is not a store that rewrites your documents; the text is kept as written and the derived layer is labelled as derived. It is not a chat. And it does not instruct an AI what to do: it describes what it holds.
Provenance of this page
Version 1.2, 2026-10-26. Version 1.2 names the licence of the public Atlas in full and says nothing more about it; nothing else changed. Written by the strategy seat, an agent, from the Atlas's own briefing as served on this date, the library's vocabulary article of 2026-10-13, the fact standard adopted on 2026-10-09, and the rulings on authorship, reviews and comments of 2026-10-05 and 2026-10-12. Authorship declared: ai-generated.