mari-components · 0.1.0.dev0

Mari documentation

Mari Kit supplies backend-agnostic values, contracts, algorithms, plans, and conformance checks for knowledge built from changing company sources. The host application owns its databases, model calls, authorization policy, scheduler, graph semantics, and product behavior.

Start with an outcome

Build path	Result
Company search	Store revisions, filter authorized candidates, retrieve current evidence
Governed knowledge	Resolve typed evidence and commit reviewable derived knowledge
Agent knowledge	Convert completed activity into validated knowledge proposals
Conversation knowledge	Turn conversations into searchable episodes with original-message evidence
Dependency-aware updates	Reuse atom representations and rebuild affected derived outputs
Incremental maintenance	Keep conversation topics and search current through edits and regrouping

Each path includes an executable composition. The feature pages explain the individual tools and the choices available when an application needs a different implementation.

Compose one knowledge library

Use scoped references to carry identity from ingestion through retrieval and evidence. Reuse semantic atoms as source units, then declare the inputs consumed by each derived output in the dependency planner. Record completed outputs before releasing downstream work.

Start with installation, run an outcome example, then replace its model and storage callbacks at the application boundary.

Browse tools by area

Area	What it covers
Ingest	Documents, multimodal regions, code structure, polling/streaming connectors, synchronization, parsers
Retrieve	Lexical, dense, multi-vector, approximate, contradiction, graph, adaptive, and lifecycle retrieval
Govern	Evidence, trust-gated writes, source conflicts, retention, freshness, verification
Memory	Admission, mutation, scopes, promotion, segmentation, salience, organization, consolidation
Graphs	Semantic schemas, constraints, resolution, temporal facts, propagation, communities, projections
Agents	Adapters and analysis for turning observed activity into knowledge evidence
Platform	Portable bundles, living views, artifact lineage, stores, pipelines, task evaluation, compilation

Maturity labels

Core marks stable cross-system contracts. Supported marks APIs intended for application use. Reference marks local correctness-oriented implementations. Experimental and Research mark surfaces that may change. Proposed marks designs awaiting a supported implementation. See Maturity.

How to use these docs

Each feature page describes importable code in mari_components. Sources sit beside the mechanism they support. Code samples mark calls supplied by the application. They also show where data crosses a persistence boundary and how failures appear.

Package naming: Mari Kit is the project. mari-components is the Python distribution. Public imports use mari_components.