# Base Layer > Base Layer is an open-source pipeline that turns your writing into a specification for AI agents. It derives plain-text claims about how you reason, communicate and decide from your chats, essays, notes and transcripts. An agent reads the specification before acting for you. Last updated 2026-10-19 to match the BaseLayer README at version 0.5.0. Some pages on this site were written before the current pipeline. If a page disagrees with this file, the README (https://github.com/agulaya24/BaseLayer#readme) and the paper (https://arxiv.org/abs/2605.28969) are the record. A longer version is available at https://www.base-layer.ai/llms-full.txt . If you are an agent working in the source repository, read AGENTS.md there. ## What a specification is - It has three layers. ANCHORS describes the certainties the person reasons from. CORE describes how they communicate and the context needed to understand them. PREDICTIONS describes how they are likely to respond in a given kind of situation. - Every claim has an id and can state when it applies through an `Active when` line. - In the cited build, every claim cites the facts it rests on. Every fact quotes the person's own words. - Base Layer works alongside memory systems but is not a memory system. The same set of facts can be interpreted differently. A memory system stores the facts, and Base Layer guides how an agent interprets them for this person. - It describes how someone reasons. It is not a copy of the person, a biography or a summary. - It is unconfirmed. Models produce the reading. Only the person it describes can confirm that it represents them. - It is written for the agent working for the person. The person reads it to correct it. ## Two builds - The cited build is the method. It takes eight commands. These are `init`, `import`, `extract --turn-contract`, `distill` and `assemble` for each layer, followed by `author-from-package`, `verify-spec` and `consolidate`. Every claim must cite facts. By default, extraction runs on Claude Haiku 5.5, the leaf stage (`distill`) runs on Claude Sonnet 5, and authoring runs on Claude Opus 5. The build is experimental. It does not yet serve its result to an agent automatically. `consolidate` writes `served.txt` and `index.json`, which you put in a system prompt by hand. - `baselayer run` is the older, quicker pipeline. It takes one command and makes far fewer checks. Claude Haiku 4.5 extracts facts. Claude Sonnet 4.6 writes the three layers in separate calls, each from a size-capped selection of facts. Citations are optional. Each claim is then linked to the facts nearest it in meaning. These links show related facts. They do not show which facts the writer used. It serves its result to Claude Code over MCP. ## Models and providers Base Layer has been tested almost entirely on Anthropic's models. Every language-model call goes to the Anthropic API, except extraction, which can run on a local model through Ollama (`baselayer extract --backend ollama`). The local models tested fell well short of the pipeline's needs. You can also paste the three layer files into a system prompt by hand. Fact search is unavailable that way. ## Install Version 0.5.0 is pre-1.0. It is not on PyPI. The `baselayer` name there belongs to another project. It requires Python 3.10 or later, git, and an Anthropic API key in `ANTHROPIC_API_KEY`. ```bash pip install git+https://github.com/agulaya24/BaseLayer.git baselayer run chatgpt-export.zip claude mcp add --scope user --transport stdio base-layer -- baselayer-mcp ``` Run it on your own writing, or on writing by someone who has agreed to it. `baselayer run` estimates the extraction cost and asks before spending. That estimate covers extraction only and has been too low, so treat it as a floor. The cited build's commands are in docs/PIPELINE.md in the repository. ## Cost These are the API costs for one specification, from the README. The projections scale the per-fact costs from recorded cited builds. The `baselayer run` extractor has not been priced on a recorded run, so treat that column as an order-of-magnitude estimate. - About 50,000 words. The cited build costs $5 to $7, and `baselayer run` costs $1 to $2. Both are projected. - About 150,000 words. The cited build costs about $17, and `baselayer run` costs $3 to $4. Both are projected. - About 300,000 words. The cited build costs about $28 (derived), and `baselayer run` costs about $6 (projected). - A chat history of about 1.4 million words. The cited build costs about $92 (derived), and `baselayer run` costs about $47 (projected). ## Research - Beyond Recall (arXiv:2605.28969, v2) is a preprint testing specifications on 14 public-domain autobiographies. A panel of five model judges scored the results. Facts plus a specification scored higher than no context on 12 of 14 subjects (mean +0.55 on a 1 to 5 rubric). Compared with the same facts alone, the mean gain was +0.08. Gains were largest where the model knew the person least. On questions that require recall, the specification can interfere rather than help. The study has not been replicated with living users. - The study's evaluation design and pre-registered analysis plan, including later deviations, are documented in the [Beyond Recall repository](https://github.com/agulaya24/beyond-recall). - A later test, separate from the paper, used recorded responses to the same decisions under nine specifications. A simple classifier identified the right specification 51.6% of the time from the reasoning and 13.4% from the decision alone, against 11.1% chance. The test used no model judge. It did not rule out differences in tone and length. - Claim boundary: "Specifications changed how decisions were argued in every situation tested. They changed the decision itself in some situations." - Another model's ability to distinguish a specification from others establishes distinguishability, without establishing fidelity. Only the person can confirm it. - The Conformance Layer is an independent prototype design. It is not an official AAuth document, and AAuth's authors have not endorsed it. It uses a specification to decide whether an agent's proposed action should proceed, be revised, or go to the person. It is not a validated result, and the paper does not evaluate it. - [Behavioral envelopes](https://www.base-layer.ai/research/behavioral-envelopes) is a framework with provider, organization and individual as three overlapping limits on what an agent acting for a person may do. It includes one worked example. - [Delegation Model](https://www.base-layer.ai/research/delegation-model) is a work in progress draft for comment, November 2026. It describes how an agent acting for a person behaves around an organization's rules. Its legal readings have not yet been reviewed by legal experts. The five documents are also published as plain markdown files: - [Operating Principles](https://www.base-layer.ai/delegation-protocol/1_Operating_Principles.md) - [Glossary](https://www.base-layer.ai/delegation-protocol/2_Glossary.md) - [Pattern Review](https://www.base-layer.ai/delegation-protocol/3_Pattern_Review.md) - [Agent Cards](https://www.base-layer.ai/delegation-protocol/4_Agent_Cards.md) - [Delegation Terms](https://www.base-layer.ai/delegation-protocol/5_Delegation_Terms.md) ## Pages - [Research](https://www.base-layer.ai/research) has dated studies, including null results. Parts of this page describe the earlier pipeline. - [Beyond Recall](https://www.base-layer.ai/research/beyond-recall) is the paper on the site. It shows an earlier draft. arXiv v2 is the current version. - [The Conformance Layer](https://www.base-layer.ai/research/conformance-layer) covers the prototype design, 33 worked verdicts and the measured record. - [Examples](https://www.base-layer.ai/examples/franklin) has ten example specifications. All ten predate citations. The cited example, `zitkala_sa`, is in the repository under `examples/zitkala_sa/` and is not yet on this site. - [Try it](https://www.base-layer.ai/try-it) explains how to build a specification. The install section above and the README are current. - [Journey](https://www.base-layer.ai/journey) explains how the project developed. - [Glossary](https://www.base-layer.ai/glossary) defines a few terms. The full list is docs/DEFINITIONS.md in the repository. - [Vision](https://www.base-layer.ai/vision), [Thoughts](https://www.base-layer.ai/thoughts), [Neutrality essay](https://www.base-layer.ai/essays/neutrality) and [Signals](https://www.base-layer.ai/signals) contain earlier essays and notes. ## Source, paper and data - [BaseLayer source](https://github.com/agulaya24/BaseLayer) is licensed under Apache 2.0 and includes the local MCP server - [arXiv:2605.28969](https://arxiv.org/abs/2605.28969) is Beyond Recall - [Study repository](https://github.com/agulaya24/beyond-recall) contains the data, scripts and judge outputs behind the paper - [Dataset](https://huggingface.co/datasets/agulaya24/beyond-recall) ## Machine-readable - [Example specification API](https://www.base-layer.ai/api/identity/franklin) supports GET /api/identity/{slug} and returns JSON with no authentication - [OpenAPI](https://www.base-layer.ai/api/openapi.json) - [A2A agent card](https://www.base-layer.ai/.well-known/agent-card.json) - [Agent directory](https://www.base-layer.ai/.well-known/agents.json) - [MCP server card](https://www.base-layer.ai/.well-known/mcp/server-card.json) Author: Aarik Gulaya. ORCID: 0009-0009-5902-9557. Contact: aarik@base-layer.ai.