MESA Core · v0.9.3
Documentation map
This guide has equivalent English and Turkish versions. The source sections behind this page are at the bottom.
Purpose and boundaries#
Start with installation and the model-disabled quickstart, then learn source identity, ingestion, architecture and retrieval. Integrate through the versioned API/SDK or MCP. Operators should read security, configuration, runbook, rebuild, migration and limitations together. Historical audits and ADRs remain dated context, not the maintained product contract.
Continue with the maintained contracts#
Use the pinned source reference below for complete tables and operator details. Related guides: architecture, API, operations and release limits.
Source reference for this page
The sections of the upstream file that back this page, translated to English where the original mixes in Turkish. The GitHub link shows the exact original.
This folder holds 12 usage/development guides and 8 architecture decision records.
You do not need to read them in order. Pick the entry point below that matches your goal.
Package version 0.9.3; V4 is the current API.
Where should I start?#
| Your goal | Document to read |
|---|---|
| Install MESA and run the first example | Installation and first run |
| Set model, provider, port or capacity | Configuration |
| Use it over HTTP, the Python SDK or terminal commands | API, SDK and CLI |
| Connect Codex/Antigravity | MCP guide |
| Understand tenant, dataset, revision and mutation | Concepts and ingestion |
| Understand the system's modules and boundaries | Architecture |
| Understand search scores, the graph and context | Retrieval and graph |
| Handle permissions, backups, failures or upgrades | Operations guide |
| Regenerate vector/graph stores from existing V4 data | Projection rebuild |
| Learn the access and data security boundaries | Security |
| Run the tests and read CI results | Testing and CI |
| Publish a new release | Release procedure |
Where did merged topics go?#
- Docker and runtime profiles: installation.
- Terminal commands: CLI.
- MCP management endpoints and approval IDs: control API.
- Error table: troubleshooting.
- Upgrading older V4 data: v0.8.0 upgrade.
- Responsibilities of the other MESA projects: ecosystem.
- Capacity and unsupported features: limits.
- Scope of the GitHub checks: CI.
- v0.8.1 release status and exceptions: CHANGELOG.
Design decisions and technical files#
The ADR index explains why the design was chosen. Seven current
decisions have their own files; the index holds a short history of retired decisions.
Historical decisions are not a current feature or performance guarantee.
The OpenAPI snapshot is a generated API schema; the running
application's /openapi.json output and the route/schema code are the current authority.
The Prometheus rules are alert rules loaded into the monitoring
system; they are not a Markdown guide.
Keeping the docs current#
Update the main document above for each topic; do not open new
“final/latest/current” files about the same topic. Keep API/package version, the V3/V4
split, implemented features and measured results apart.
Production readiness is judged by the release gates; unit test
success or a version number is not a production GO.
When moving content, update links and the documentation tests together; then run the
documentation check in the testing guide. Older full texts are in
Git history. for_mvp/ is a working plan and outside this arrangement.
