MESA Core · v0.9.3

Ecosystem boundaries

v0.9.3 source: docs/architecture-v4.md

This guide has equivalent English and Turkish versions. The source sections behind this page are at the bottom.

Purpose and boundaries#

MESA Data prepares reviewed Turkish legal releases. Core owns memory admission, canonical state and retrieval. Law consumes a V4 HTTP contract; current live integration is unverified. QA exercises behavior outside the baseline. E2E Certification evaluates a frozen Data → Core profile with external evidence; B4/B6/B7/B8 receipts and a fresh official PASS remain absent.

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.

Verified sources
Source reference for this page

The sections of the upstream file that back this page, unchanged. Source section links open the appendix automatically.

Ecosystem and ownership#

ProjectOwnershipCore release implication
MESA CoreRuntime, catalog/mutations, projections, scoped retrieval, SDK/MCPThis repository's package and GitHub release only
MESA_DataSource acquisition, metadata/identity, revisions/chunking, native publisherProducer must satisfy Core ingestion and provenance contracts
MESA_E2E_CertificationFreeze, official TEST, sealed answer context, scorer and verdictIndependent certification; Core unit tests cannot change its verdict
mesa_benchmarkComparative methodology, runner, external datasets/judgesCore mesa_evals is historical diagnostics plus deterministic RRF contract tooling
MESA_LawLegal product/integration work outside CoreNo Core legal-advice or legal-certification guarantee
mesa-model-testsIndependent DEV model qualificationModel quality and pending human review are separate from Core release

The source consumer contract is concepts and ingestion

and API. Supply exact content, immutable revision/chunk IDs,

source references and verified legal identity where appropriate. Core validates

schema/alias consistency and linkage; it does not fetch official laws or establish

that producer metadata is legally correct. SDK insertion currently lacks the HTTP

legal_identity parameter; use reviewed HTTP payloads for this contract.

Comparative benchmark methodology lives in the external mesa_benchmark

project's docs/METHODOLOGY.md. Core retains

`tests/test_v4_rrf_ablation.py` and

`mesa_evals/v4_rrf_ablation.py` for deterministic

retrieval contracts; these are not comparative model-quality measurements.

Official certification is owned and executed outside Core. A Core documentation

edit or unit-test result cannot change a sealed certification verdict. External

repository commit IDs and measured outcomes belong in dated evidence records,

not this ownership map.

Core ContextBuilder budget/provenance behavior and Profile B's independently

sealed Top-5/context/scorer settings are distinct contracts. A successful Core

DEV example proves the exercised path only, not native ecosystem delivery or

model accuracy. Provider pairing quality requires its own measured evidence.