Skip to main content

IA-RAG Core

Governed, structure-aware retrieval and execution planning for agentic systems.

IA-RAG Core makes the information architecture of a question explicit before execution. A domain describes entities, relations, capabilities, bounds, and world semantics. The runtime then turns a question into an inspectable semantic program, a typed logical plan, and one bounded executable plan before producing evidence, claims, a receipt, and a deterministic response.

Why information architecture comes first

Ordinary vector RAG is useful for ranking relevant text, but relevance is not the same as authoritative execution semantics. A similarity result does not by itself say which entities and relations are allowed, whether a traversal is complete, or what an empty result means.

IA-RAG Core puts those decisions in an explicit domain and plan. Retrieval strategies can supply candidates through neutral protocols; the canonical runtime still validates the structure, applies bounds, records evidence, and binds the result to the exact plan that ran.

Canonical pipeline

DomainPack
  -> PlannerRegistry
  -> Semantic interpretation
  -> CanonicalCompiler
  -> LogicalPlan
  -> deterministic lowering
  -> ExecutablePlan
  -> Admission and assurance
  -> PRE enforcement
  -> bounded execution
  -> POST enforcement
  -> Evidence and provenance
  -> Claims and truth state
  -> Receipt and lineage
  -> deterministic rendering

There is one selected planner, one logical-plan lineage, one executable plan, and one receipt bound to that executed plan. Plan and receipt digests are deterministic for the same query, domain configuration, and input facts.

Install and run

python -m pip install ia-rag-core

The offline reference demo is available from a repository checkout. From the checkout, install the development tools and run the tests and demo with the same Python interpreter:

python -m pip install '.[dev]'
python -m pytest -q
python examples/reference_demo.py

Using python -m pytest ensures the tests run with the same Python interpreter and virtual environment into which IA-RAG Core was installed.

The quick-start demo is offline, uses no external credentials, and runs on a small synthetic research-network domain. Its output includes the selected planner, plan digests, evidence, receipt, and response.

Truth and bounded execution

The reference domains demonstrate three explicit semantics:

  • OPEN_WORLD: an empty search does not prove that a fact is false, so the result may be UNKNOWN.
  • CLOSED_WORLD: within the declared domain and complete evidence boundary, an empty search can support a FALSE result.
  • REQUIRED_SUBGRAPH: when a declared required relation or traversal cannot be established, execution remains incomplete and the runtime does not emit a positive claim from the partial result.

These semantics describe the evidence boundary and execution state. They do not guarantee truth about the real world beyond the supplied domain and evidence.

Feature claim ledger

Status Claims supported by this candidate
DEMONSTRATED Typed canonical plans; deterministic planning and lowering; explicit assurance allow/deny; bounded in-memory graph execution; evidence/provenance; open- and closed-world truth behavior; required-subgraph enforcement; plan-bound receipts and lineage; deterministic rendering; synthetic reference domains.
ARCHITECTURALLY_SUPPORTED Neutral protocols for graph, document, lexical, vector, embedding, entity, language-model, and telemetry integrations; domain semantic extensions; injected assurance providers.
FUTURE Production retrieval adapters, persistent stores, model-backed interpretation, deployment integrations, and production identity or high-assurance services.
NOT A CLAIM Elimination of probabilistic retrieval, a guarantee of real-world truth, or production qualification of external services.

Deliberate scope

The base distribution has zero runtime dependencies and contains only the canonical runtime, neutral contracts, deterministic reference assurance, in-memory execution, and synthetic reference domains. External services, credentials, application data, and deployment-specific integrations are not part of this candidate.

IA-RAG Core is licensed under the Apache License 2.0; see LICENSE.

See the public architecture and the package boundary for the supported scope.

Metadata

Release files for ia-rag-core 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ia-rag-core 0.1.1
File Size Uploaded
ia_rag_core-0.1.1.tar.gz 75.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ia-rag-core 0.1.1
File Interpreter ABI Platform
ia_rag_core-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 159.5 kB

Release files / ia_rag_core-0.1.1.tar.gz

Download URL ia_rag_core-0.1.1.tar.gz
Size 75.4 kB
Tags Source
SHA-256 checksum
How to use checksums
0e061a4bf61c2aeda5413ae62f4f9a1f41631c71d86bd8798cdf3c0a492cbab1
BLAKE2b-256 checksum
How to use checksums
facbff4fbf5cab9910bb8fd6dd66f614452832724ada058403eee67598d8cf28
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 Sep 18, 2026.

Transparency log

Release files / ia_rag_core-0.1.1-py3-none-any.whl

Download URL ia_rag_core-0.1.1-py3-none-any.whl
Size 84.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
80044830ed8bef7ec215362773400b4c0d54348d8c33c697b57351367b74152b
BLAKE2b-256 checksum
How to use checksums
65396468a0d7680a78cb0e1dfda1741ce584fa29f8af1ad65d1a5dbd19e59714
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 Sep 18, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page