Skip to main content

coreason-archive

Persistence layer for "Cognitive State" across the CoReason ecosystem.

CI/CD Docker codecov Python License Ruff pre-commit Poetry Pydantic v2

Executive Summary

coreason-archive is the persistence layer for "Cognitive State" across the CoReason ecosystem. It addresses the critical failure mode of modern AI: "Digital Amnesia."

Standard RAG (Retrieval Augmented Generation) only looks at static documents (coreason-mcp). coreason-archive looks at Dynamic Experience. It stores the reasoning traces, decisions, and user preferences generated during runtime.

Version 3.0 upgrades the architecture from a simple Vector Cache to a Hybrid Neuro-Symbolic Memory System. It combines Vector Search (for semantic similarity) with a Knowledge Graph (for structural relationships) and a Temporal Engine (for time-decay). This ensures that an agent doesn't just recall "similar text" but understands "who, when, and why" a decision was made, respecting strict enterprise boundaries.

Functional Philosophy

The agent must implement the Scope-Link-Rank-Retrieve Loop:

  1. Hybrid Memory Structure (Neuro-Symbolic):
    • Semantic (Vector): "Find thoughts similar to 'Dosing Protocol'."
    • Structural (Graph): "Find all thoughts linked to 'Project Apollo' and 'Dr. Smith'."
    • SOTA Best Practice: Using vectors for fuzzy matching and graphs for explicit entity tracking prevents "Context Collapse" in complex workflows.
  2. Federated Scoping (The Hierarchy of Truth):
    • Memory is not a flat bucket. It is a hierarchy: User > Project > Department > Global.
    • A "User Preference" (e.g., "Don't use tables") overrides a "Global Default."
  3. Active Epistemic Decay:
    • Knowledge has a half-life. A cached thought about "Q3 Strategy" is worthless in Q4.
    • We implement Time-Aware Retrieval where older memories have lower retrieval scores unless explicitly pinned.
  4. Memory Portability (The Digital Twin):
    • When a user moves departments, their personal cognitive state follows them, but their former team's secrets are left behind.
  5. Asynchronous & Framework-Agnostic:
    • The system utilizes a TaskRunner abstraction (defaulting to asyncio/anyio) to handle background ingestion tasks, ensuring it can be integrated into any Python stack (FastAPI, Django, CLI) without vendor lock-in.

Getting Started

Prerequisites

  • Python 3.12+
  • Poetry

Installation

  1. Clone the repository:
    git clone https://github.com/example/example.git
    cd my_python_project
    
  2. Install dependencies:
    poetry install
    

Usage

  • Run as a Service (REST API):
    poetry run uvicorn coreason_archive.server:app --host 0.0.0.0 --port 8000
    
  • Run CLI (Add Thought):
    poetry run python src/coreason_archive/main.py add --prompt "Test" --response "Test Response" --user "Alice"
    
  • Run the linter:
    poetry run pre-commit run --all-files
    
  • Run the tests:
    poetry run pytest
    

For detailed documentation, please refer to the docs/ folder or the MkDocs site.

Metadata

Release files for coreason-archive 0.6.0

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

Source distribution (sdist)

Source distribution for coreason-archive 0.6.0
File Size Uploaded
coreason_archive-0.6.0.tar.gz 25.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for coreason-archive 0.6.0
File Interpreter ABI Platform
coreason_archive-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 59.5 kB

Release files / coreason_archive-0.6.0.tar.gz

Download URL coreason_archive-0.6.0.tar.gz
Size 25.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e9e8902daff026b539bc59a2202aff91f69ec66917b5ee478ee95eed83227eff
BLAKE2b-256 checksum
How to use checksums
63c8fa2116141660cbb88e69dfe795b566be8a50921d22d77cf16793d7cd1e68
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 30, 2026.

Transparency log

Release files / coreason_archive-0.6.0-py3-none-any.whl

Download URL coreason_archive-0.6.0-py3-none-any.whl
Size 34.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5dfd3f8180e1e489001ed1acd07e7cee44e9be6861ef0e6a4f0cc1df5d2434a7
BLAKE2b-256 checksum
How to use checksums
e7530c659034b2811bddd5900ae488a3f2faf35ef39f59d74bc76a36e48cb347
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Jan 30, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.6.0 This release

2 release files

0.5.1

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.0

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