memanto 0.0.1__tar.gz

memanto-0.0.1/.dockerignore

@@ -0,0 +1,51 @@
+# Version control
+.git/
+.gitignore
+
+# Python artifacts
+__pycache__/
+*.pyc
+*.pyo
+*.pyd
+*.egg-info/
+dist/
+build/
+.eggs/
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+
+# Secrets — never bake these into the image
+.env
+.env.local
+.env.*.local
+*.key
+*.pem
+*.crt
+secrets/
+
+# Dev / CI tooling (not needed at runtime)
+tests/
+.github/
+.pre-commit-config.yaml
+.ruff_cache/
+.mypy_cache/
+.pytest_cache/
+.tox/
+.nox/
+
+# Docs and assets (not needed at runtime)
+docs/
+assets/
+
+# Editor / OS noise
+.vscode/
+.idea/
+.claude/
+.DS_Store
+Thumbs.db
+*.swp
+*.swo

memanto-0.0.1/.env.example

@@ -0,0 +1,17 @@
+# Moorcheh SDK Configuration
+# Get your API key from https://app.moorcheh.ai
+# Free tier: 500 monthly credits = ~100,000 operations
+MOORCHEH_API_KEY=mk_your_api_key_here
+
+# AI / Answer Configuration (all optional — defaults shown)
+# ANSWER_MODEL=anthropic.claude-sonnet-4-20250514-v1:0
+# ANSWER_TEMPERATURE=0.7
+# ANSWER_LIMIT=5
+# ANSWER_THRESHOLD=0.25
+# RECALL_LIMIT=10
+
+# Session Configuration (all optional — defaults shown)
+# SESSION_DEFAULT_DURATION_HOURS=6
+# SESSION_AUTO_RENEW_ENABLED=True
+# SESSION_AUTO_RENEW_INTERVAL_HOURS=6
+# SESSION_EXTEND_THRESHOLD_MINUTES=30

memanto-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,70 @@
+name: CI
+
+on:
+  push:
+    branches: main
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  lint-and-type-check:
+    if: github.event_name == 'push' || (github.event_name == 'pull_request_review' && github.event.review.state == 'approved')
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.10"
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+
+    - name: Install dependencies
+      run: uv sync --all-extras --dev
+
+    - name: Run ruff linting
+      run: uv run ruff check .
+
+    - name: Run ruff formatting check
+      run: uv run ruff format --check .
+
+    - name: Run mypy type checking
+      run: uv run mypy .
+
+  test:
+    needs: lint-and-type-check
+    if: github.event_name == 'push' || (github.event_name == 'pull_request_review' && github.event.review.state == 'approved')
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version:
+          - "3.14"
+          - "3.13"
+          - "3.12"
+          - "3.11"
+          - "3.10"
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v5
+      with:
+        python-version: ${{ matrix.python-version }}
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+
+    - name: Install dependencies
+      run: uv sync --all-extras --dev
+
+    - name: Create version fallback
+      run: echo '__version__ = "0.0.0.dev0"' > memanto/app/_version.py
+
+    - name: Run tests
+      env:
+        MOORCHEH_API_KEY: test-api-key
+      run: uv run pytest tests/ -v --tb=short

memanto-0.0.1/.github/workflows/publish.yml

@@ -0,0 +1,49 @@
+name: Publish
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    name: Publish to PyPI
+    # Only run on releases starting with 'v'
+    if: github.event_name == 'release' && startsWith(github.event.release.tag_name, 'v')
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: read
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with:
+        python-version: "3.10"
+
+    - name: Install uv
+      uses: astral-sh/setup-uv@v4
+
+    - name: Install dependencies
+      run: uv sync --all-extras --dev
+
+    - name: Create version fallback
+      run: echo '__version__ = "0.0.0.dev0"' > memanto/app/_version.py
+
+    - name: Run tests
+      env:
+        MOORCHEH_API_KEY: test-api-key
+      run: uv run pytest tests/ -v --tb=short
+
+    - name: Build package
+      run: uv run python -m build
+
+    - name: Publish to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
+      with:
+        password: ${{ secrets.PYPI_API_TOKEN }}
+        packages-dir: dist/

memanto-0.0.1/.gitignore

@@ -0,0 +1,106 @@
+# Environment variables and secrets
+.env
+.env.local
+.env.*.local
+*.key
+*.pem
+*.crt
+secrets/
+.secrets
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+uv.lock
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Virtual environments
+venv/
+.venv/
+ENV/
+env/
+.env/
+
+# IDEs
+.vscode/
+.idea/
+.claude/
+*.swp
+*.swo
+*~
+.DS_Store
+
+# Testing
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.log
+.pytest_cache/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# Database
+*.db
+*.sqlite
+*.sqlite3
+
+# Logs
+logs/
+*.log
+pip-log.txt
+pip-delete-this-directory.txt
+
+# OS
+.DS_Store
+Thumbs.db
+Desktop.ini
+
+# Temporary files
+tmp/
+temp/
+*.tmp
+*.bak
+*.swp
+*.swo
+
+# Generated version file
+**/_version.py

memanto-0.0.1/.pre-commit-config.yaml

@@ -0,0 +1,23 @@
+repos:
+  - repo: local
+    hooks:
+      - id: ruff-check
+        name: ruff lint
+        entry: uv run ruff check .
+        language: system
+        pass_filenames: false
+        always_run: true
+
+      - id: ruff-format
+        name: ruff format check
+        entry: uv run ruff format --check .
+        language: system
+        pass_filenames: false
+        always_run: true
+
+      - id: mypy
+        name: mypy type check
+        entry: uv run mypy .
+        language: system
+        pass_filenames: false
+        always_run: true

memanto-0.0.1/CODE_OF_CONDUCT.md

@@ -0,0 +1,94 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders of the MEMANTO community pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+---
+
+## Our Standards
+
+**Examples of behavior that contributes to a positive environment:**
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive feedback
+- Focusing on what is best for the community and the project
+- Showing empathy toward other community members
+
+**Examples of unacceptable behavior:**
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information (e.g., physical or email addresses) without explicit permission
+- Dismissing or attacking inclusion-focused requests
+- Sustained disruption of discussions, talks, or contributions
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+---
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior. They will take appropriate and fair corrective action in response to any behavior they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, issues, and other contributions that are not aligned with this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+---
+
+## Scope
+
+This Code of Conduct applies in all community spaces — including the GitHub repository, Discord server, documentation, social media, and any official communication channels — and also applies when an individual is officially representing the project or community in public spaces.
+
+---
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders at:
+
+- **Email**: support@moorcheh.ai
+- **Subject line**: `[Code of Conduct] Brief description`
+
+All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+---
+
+## Enforcement Guidelines
+
+Community leaders will follow these guidelines when determining consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+---
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

memanto-0.0.1/CONTRIBUTING.md

@@ -0,0 +1,273 @@
+# Contributing to MEMANTO
+
+Thank you for your interest in contributing to MEMANTO — the universal memory layer for agentic AI. This guide will help you get set up and understand how we work.
+
+---
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Ways to Contribute](#ways-to-contribute)
+- [Reporting Bugs](#reporting-bugs)
+- [Requesting Features](#requesting-features)
+- [Development Setup](#development-setup)
+- [Project Structure](#project-structure)
+- [Code Style](#code-style)
+- [Running Tests](#running-tests)
+- [Submitting a Pull Request](#submitting-a-pull-request)
+- [Commit Message Convention](#commit-message-convention)
+- [Community](#community)
+
+---
+
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please read it before contributing.
+
+---
+
+## Ways to Contribute
+
+- **Bug reports** — open a GitHub issue with reproduction steps
+- **Feature requests** — open a GitHub issue describing the use case
+- **Documentation improvements** — fix typos, improve clarity, add examples
+- **Bug fixes and features** — submit a pull request (see below)
+- **Memory type integrations** — propose new memory type handlers or agent connectors
+
+---
+
+## Reporting Bugs
+
+Before opening an issue, please check that it hasn't been reported already.
+
+When filing a bug, include:
+
+1. **MEMANTO version** (`pip show memanto`)
+2. **Python version** (`python --version`)
+3. **Operating system**
+4. **Steps to reproduce** — a minimal, self-contained script is ideal
+5. **Expected behavior** vs. **actual behavior**
+6. **Relevant logs or error output**
+
+Open a bug report at: https://github.com/moorcheh-ai/memanto/issues
+
+> **Security vulnerabilities** must **not** be reported as public issues. See [SECURITY.md](SECURITY.md) for responsible disclosure instructions.
+
+---
+
+## Requesting Features
+
+Open a feature request at https://github.com/moorcheh-ai/memanto/issues and include:
+
+- A clear description of the problem you are trying to solve
+- Your proposed solution or API
+- Any alternatives you considered
+- Whether you are willing to implement it yourself
+
+---
+
+## Development Setup
+
+### Prerequisites
+
+- Python 3.10–3.12
+- [`uv`](https://github.com/astral-sh/uv) (recommended) or `pip`
+- A Moorcheh API key from https://console.moorcheh.ai/api-keys
+
+### 1. Fork and clone
+
+```bash
+git clone https://github.com/<your-username>/memanto.git
+cd memanto
+```
+
+### 2. Create a virtual environment and install dependencies
+
+**With uv (recommended):**
+
+```bash
+uv sync --group dev
+```
+
+**With pip:**
+
+```bash
+python -m venv .venv
+source .venv/bin/activate   # Windows: .venv\Scripts\activate
+pip install -e ".[all]"
+```
+
+### 3. Configure your environment
+
+```bash
+cp .env.example .env
+# Edit .env and add your MOORCHEH_API_KEY
+```
+
+### 4. Install pre-commit hooks
+
+```bash
+pre-commit install
+```
+
+The hooks run `uv run ruff check`, `uv run ruff format --check`, and `uv run mypy` on every commit automatically.
+
+---
+
+## Project Structure
+
+```
+memanto/
+├── memanto/
+│   ├── app/          # FastAPI application, routes, models
+│   └── cli/          # Typer CLI commands
+├── tests/            # pytest test suite
+├── docs/             # Additional documentation
+├── assets/           # Logos and diagrams
+├── pyproject.toml    # Project metadata and tool configuration
+└── SECURITY.md       # Security policy
+```
+
+---
+
+## Code Style
+
+We use **[Ruff](https://docs.astral.sh/ruff/)** for linting and formatting, and **[mypy](https://mypy.readthedocs.io/)** for static type checking. All tools are run via `uv run` so no global installs are needed.
+
+```bash
+# Check for lint errors
+uv run ruff check .
+
+# Check formatting (non-destructive — reports issues without modifying files)
+uv run ruff format --check .
+
+# Apply lint fixes and format in one go (use before committing)
+uv run ruff check . --fix && uv run ruff format .
+
+# Type check
+uv run mypy .
+```
+
+Key conventions:
+
+- Line length: 88 characters
+- Target Python version: 3.10+
+- Import order enforced by ruff (`isort` rules)
+- Do not suppress type errors with `# type: ignore` without a comment explaining why
+
+Running pre-commit manually:
+
+```bash
+uv run pre-commit run --all-files
+```
+
+---
+
+## Running Tests
+
+```bash
+# Run the full test suite
+pytest
+
+# Run a specific test file
+pytest tests/test_cli.py
+
+# Run with verbose output
+pytest -v
+
+# Run and stop on first failure
+pytest -x
+```
+
+Tests require a valid `MOORCHEH_API_KEY` in your environment or `.env` file for any integration tests. Unit tests that don't hit the network will run without a key.
+
+---
+
+## Submitting a Pull Request
+
+1. **Create a branch** from `main`:
+
+   ```bash
+   git checkout -b fix/describe-your-fix
+   # or
+   git checkout -b feat/describe-your-feature
+   ```
+
+   Branch naming:
+   | Prefix | Use for |
+   |--------|---------|
+   | `feat/` | new features |
+   | `fix/` | bug fixes |
+   | `docs/` | documentation only |
+   | `chore/` | maintenance, dependency updates |
+   | `test/` | adding or fixing tests |
+   | `refactor/` | code restructuring without behavior change |
+
+2. **Make your changes.** Keep each PR focused on a single concern.
+
+3. **Add tests** for any new behavior. PRs that reduce test coverage will be asked to add tests before merging.
+
+4. **Ensure all checks pass:**
+
+   ```bash
+   pre-commit run --all-files
+   pytest
+   ```
+
+5. **Push your branch** and open a pull request against `main`.
+
+6. **Fill in the PR description:**
+   - What problem does this solve?
+   - How did you test it?
+   - Link any related issues (e.g., `Closes #42`)
+
+7. A maintainer will review your PR. Please respond to feedback within a reasonable time. PRs with no activity for 30 days may be closed.
+
+### PR Checklist
+
+- [ ] Code follows the project style (`ruff`, `mypy` pass)
+- [ ] Tests added or updated for changed behavior
+- [ ] All existing tests pass
+- [ ] Documentation updated if the public API or CLI changed
+- [ ] No secrets or credentials in the diff
+
+---
+
+## Commit Message Convention
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+```
+<type>(<scope>): <short summary>
+
+[optional body]
+
+[optional footer(s)]
+```
+
+**Types:** `feat`, `fix`, `docs`, `chore`, `test`, `refactor`, `perf`, `ci`
+
+**Examples:**
+
+```
+feat(cli): add --type flag to recall command
+fix(app): handle empty memory list in daily-summary endpoint
+docs: update REST API section in README
+chore(deps): bump pydantic to 2.7.0
+```
+
+Rules:
+- Use the imperative mood in the summary ("add", not "added" or "adds")
+- Keep the summary under 72 characters
+- Reference issues in the footer: `Closes #123`
+
+---
+
+## Community
+
+- **Discord**: [Join our server](https://discord.gg/CyxRFQSQ3p) — the best place for quick questions and discussions
+- **GitHub Issues**: https://github.com/moorcheh-ai/memanto/issues — bugs and feature requests
+- **Email**: support@moorcheh.ai — for anything that doesn't fit the above
+- **Docs**: https://docs.memanto.ai
+
+We appreciate every contribution, no matter how small. Thank you for helping make MEMANTO better.