SYUNE
The control layer between knowledge and AI agents.
SYUNE is a governed memory, context and model-execution runtime for AI systems. It gives agents persistent memory without giving them uncontrolled access to memory.
Traditional RAG primarily asks: What information is relevant? SYUNE also governs:
- Who may use it, and for what purpose?
- Which version is current, and what was valid at a requested time?
- Where did the information come from?
- Is it still active and retrievable?
- What bounded context actually reached the model?
How it differs
SYUNE can use retrieval and RAG techniques; it adds governance before information becomes model-visible.
Traditional RAG SYUNE
Query Query
↓ ↓
Retrieval Identity + Purpose
↓ ↓
Top-K context Authorization
↓ ↓
LLM Temporal / Version eligibility
↓
Hybrid Retrieval
↓
Lifecycle
↓
Provenance
↓
Bounded Context
↓
ModelGateway
↓
LLM
Lean v1 architecture
flowchart TD
App[Application or agent] --> API[SDK / API / MCP]
API --> Lean[SYUNE Lean v1]
Lean --> Memory[Governed memory]
Lean --> Context[Bounded context]
Lean --> Gateway[ModelGateway]
Memory --> Retrieval[Hybrid retrieval]
Context --> Governance[Authorization · identity · purpose · scope]
Context --> Temporal[Temporal/version eligibility]
Context --> Provenance[Provenance · lineage · lifecycle]
Memory --> Result[Governed result]
Retrieval --> Result
Governance --> Result
Temporal --> Result
Provenance --> Result
Gateway --> OpenAI[OpenAI Responses]
Gateway --> Compatible[OpenAI-compatible / local]
Gateway --> Future[Additional adapters]
Result --> Audit[Durable audit / observability]
Gateway --> Audit
See the Lean v1 architecture for boundaries, storage, detachability modes, and the default-disabled research surfaces.
Why SYUNE
Governed agent memory
An agent retrieves relevant memory without receiving records outside its authorized identity or scope. Purpose and task context are carried through retrieval and audit.
Version-aware knowledge
Applications distinguish CURRENT, HISTORICAL, and AS_OF information instead of
treating every stored record as simultaneously current.
Traceable context
Model-visible context retains provenance and lineage so developers can determine where the information came from and correlate it with durable audit events.
Reliable model execution
ModelGateway centralizes structured output, retry, repair, fallback, budgets, provider policy, health, evidence, and audit without coupling the memory layer to one provider.
Quick start
Requires Python 3.12 or newer (below 4).
pip install syune
syune init --state-root .syune-demo
from syune import ContextRequest, ProvenanceMode, Syune
with Syune.open(state_root=".syune-demo") as memory:
stored = memory.remember("The deployment window is Friday at 18:00 UTC.")
context = memory.context(ContextRequest(
"deployment window",
purpose="release-planning",
provenance_mode=ProvenanceMode.FULL,
))
print(stored.data["memory_id"])
print(context.data["rendered"])
print(context.data["items"][0]["provenance"])
The full quickstart covers revision, CURRENT, historical/AS_OF
queries, lifecycle, durable audit, shutdown, and restart. More focused programs are in
examples/.
Validated behavior
One frozen synthetic validation compared Strong RAG with Lean SYUNE on authorized useful recall and context cleanliness:
| Metric | Strong RAG | Lean SYUNE |
|---|---|---|
| Authorized useful recall | 100% | 100% |
| Precision | 45.5% | 100% |
| Context precision | 45.5% | 100% |
SYUNE excluded 60 unauthorized records, one superseded record, one future-invalid record, and six lifecycle-ineligible records. This is one controlled validation, not a universal benchmark claim. SYUNE did not improve authorized useful recall over Strong RAG in this dataset; it improved the cleanliness and governance of the resulting context.
Read the Lean v1 validation for methodology, limitations, and canonical evidence links.
Documentation
Start with the documentation index, public API, Python SDK, MCP interface, configuration, and security policy.
What v1 is not
SYUNE v1 is not an AGI, an autonomous truth engine, or an autonomous organizational- learning system. Research cognition, learning, Council, Planner, and Executive code is experimental, retained for compatibility, and disabled by default.
Major limitations
- Deployment is single-node SQLite.
- The default vector backend is local-linear, not a production ANN service.
- High-contention multi-process writes are unsupported.
- Research cognition and learning are disabled by default.
See known limitations for the complete list.
SYUNE 1.0.1 exposes Public API v1 and is licensed under the Apache License 2.0.
Metadata
Release files for syune 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| syune-1.0.1.tar.gz | 183.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| syune-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 392.6 kB
Release files / syune-1.0.1.tar.gz
| Download URL | syune-1.0.1.tar.gz |
|---|---|
| Size | 183.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3cae507b4143578d6b13dfd96c47473e2a858ac1f1721fbb2c19f8b86504702
|
|
BLAKE2b-256 checksum How to use checksums |
12dc08b0412c959856cbd9644ab37e6d133159da664a55121a369d0661c8de0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / syune-1.0.1-py3-none-any.whl
| Download URL | syune-1.0.1-py3-none-any.whl |
|---|---|
| Size | 208.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4750f2988e867ac75a2b9731eedb96c63e452f224347442ef492fd67a621f7ac
|
|
BLAKE2b-256 checksum How to use checksums |
e80a5d01a814d1cf5054d03b25f0296395f9b4b831dab985b3246040cbb21569
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log