chronem 0.1.0__tar.gz

chronem-0.1.0/.cursor/rules/chronem-core.mdc

@@ -0,0 +1,24 @@
+---
+description: Cursor entrypoint for the shared Chronem agent instructions.
+globs:
+alwaysApply: true
+---
+
+# Chronem Cursor Rule
+
+The canonical cross-agent instructions live in @AGENTS.md.
+
+Before making non-trivial changes, read:
+- @AGENTS.md
+- the linked GitHub Issue in full
+- @docs/architecture.md
+- @docs/decisions/README.md
+- @docs/product-requirements.md
+- @docs/roadmap.md
+- @docs/project-status.md
+- @docs/development-workflow.md
+
+Follow the source-of-truth order in @AGENTS.md. Do not duplicate architecture
+or product rules in this Cursor-only file. Put durable changes in the shared
+repository documentation so Cursor, Codex, and future agents receive the same
+context.

chronem-0.1.0/.github/actions/validate-distribution/action.yml

@@ -0,0 +1,41 @@
+name: Validate Python distribution
+description: Build, inspect, install, and smoke-test Chronem's wheel and sdist
+
+runs:
+  using: composite
+  steps:
+    - name: Install packaging tools
+      shell: bash
+      run: python -m pip install "build>=1.2,<2" "twine>=6,<7"
+
+    - name: Build wheel and sdist
+      shell: bash
+      run: python -m build
+
+    - name: Validate package metadata
+      shell: bash
+      run: python -m twine check --strict dist/*
+
+    - name: Validate artifact names and contents
+      shell: bash
+      run: python scripts/validate_distribution.py dist
+
+    - name: Smoke-test the installed wheel in a fresh environment
+      shell: bash
+      run: |
+        smoke_dir="$(mktemp -d "$RUNNER_TEMP/chronem-wheel-smoke.XXXXXX")"
+        python -m venv "$smoke_dir"
+        "$smoke_dir/bin/python" -m pip install --upgrade pip
+        wheels=(dist/*.whl)
+        "$smoke_dir/bin/python" -m pip install "${wheels[0]}[postgres]"
+        cp scripts/smoke_installed_wheel.py "$smoke_dir/"
+        cp scripts/smoke_installed_wheel_postgres.py "$smoke_dir/"
+        cp examples/deterministic_lifecycle.py "$smoke_dir/"
+        (
+          cd "$RUNNER_TEMP"
+          "$smoke_dir/bin/python" "$smoke_dir/smoke_installed_wheel.py"
+          "$smoke_dir/bin/python" "$smoke_dir/deterministic_lifecycle.py"
+          "$smoke_dir/bin/python" "$smoke_dir/smoke_installed_wheel_postgres.py" \
+            --database-url "$CHRONEM_DISTRIBUTION_DATABASE_URL" \
+            --source-root "$GITHUB_WORKSPACE"
+        )

chronem-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,34 @@
+## Linked issue
+
+Closes #
+
+## Summary
+
+
+## Scope
+
+**In scope:**
+
+**Out of scope:**
+
+## Architecture / ADR impact
+
+None, or describe the accepted decision added/changed.
+
+## Validation
+
+List tests and results.
+
+## Security / privacy impact
+
+None, or describe user-isolation, data-handling, or privacy effects.
+
+## Risks / follow-ups
+
+
+## Checklist
+
+- [ ] I read `AGENTS.md`, the linked Issue, and relevant shared documentation.
+- [ ] I stayed within the Issue scope and documented any approved changes.
+- [ ] Required quality gates pass.
+- [ ] I did not add secrets or real personal data.

chronem-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,109 @@
+name: CI
+
+on:
+  push:
+    branches: ["main"]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  distribution:
+    name: Distribution package
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: public.ecr.aws/docker/library/postgres:16
+        env:
+          POSTGRES_DB: chronem_distribution
+          POSTGRES_USER: chronem
+          POSTGRES_PASSWORD: chronem_distribution_password
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U chronem -d chronem_distribution"
+          --health-interval 5s
+          --health-timeout 5s
+          --health-retries 10
+    env:
+      CHRONEM_DISTRIBUTION_DATABASE_URL: postgresql+psycopg://chronem:chronem_distribution_password@127.0.0.1:5432/chronem_distribution
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v7
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Build and validate distributions
+        uses: ./.github/actions/validate-distribution
+
+      - name: Upload validated distributions
+        uses: actions/upload-artifact@v7
+        with:
+          name: python-distributions-${{ github.sha }}
+          path: dist/
+          if-no-files-found: error
+          retention-days: 7
+
+  quality:
+    name: Quality gates (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: true
+      matrix:
+        python-version: ["3.11", "3.12"]
+
+    services:
+      postgres:
+        image: public.ecr.aws/docker/library/postgres:16
+        env:
+          POSTGRES_DB: chronem_test
+          POSTGRES_USER: chronem
+          POSTGRES_PASSWORD: chronem_test_password
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U chronem -d chronem_test"
+          --health-interval 5s
+          --health-timeout 5s
+          --health-retries 10
+
+    env:
+      CHRONEM_TEST_DATABASE_URL: postgresql+psycopg://chronem:chronem_test_password@127.0.0.1:5432/chronem_test
+
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v7
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install package and development dependencies
+        run: |
+          python -m pip install --upgrade pip
+          python -m pip install -e ".[dev]"
+
+      - name: Lint
+        run: ruff check .
+
+      - name: Type check
+        run: mypy src
+
+      - name: Unit tests with coverage
+        run: pytest -m "not postgres" --cov=chronem --cov-report=term-missing
+
+      - name: PostgreSQL integration tests
+        run: pytest -m postgres --cov=chronem --cov-append --cov-report=term-missing
+
+      - name: Deterministic contract evaluation
+        run: python scripts/run_deterministic_evaluation.py
+
+      - name: Enforce lifecycle coverage
+        run: coverage report --include="*/chronem/lifecycle/*" --fail-under=90

chronem-0.1.0/.github/workflows/release-dry-run.yml

@@ -0,0 +1,56 @@
+name: Release dry run
+
+on:
+  workflow_dispatch:
+    inputs:
+      ref:
+        description: Commit, branch, or tag to validate
+        required: true
+        default: main
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  validate:
+    name: Build and validate release artifacts
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: public.ecr.aws/docker/library/postgres:16
+        env:
+          POSTGRES_DB: chronem_distribution
+          POSTGRES_USER: chronem
+          POSTGRES_PASSWORD: chronem_distribution_password
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U chronem -d chronem_distribution"
+          --health-interval 5s
+          --health-timeout 5s
+          --health-retries 10
+    env:
+      CHRONEM_DISTRIBUTION_DATABASE_URL: postgresql+psycopg://chronem:chronem_distribution_password@127.0.0.1:5432/chronem_distribution
+    steps:
+      - name: Check out requested ref
+        uses: actions/checkout@v7
+        with:
+          ref: ${{ inputs.ref }}
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Build and validate distributions
+        uses: ./.github/actions/validate-distribution
+
+      - name: Upload dry-run artifacts
+        uses: actions/upload-artifact@v7
+        with:
+          name: release-dry-run-${{ github.sha }}
+          path: dist/
+          if-no-files-found: error
+          retention-days: 14

chronem-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,87 @@
+name: Release Python distribution
+
+on:
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: Existing version tag to build, such as v0.1.0
+        required: true
+        type: string
+      publish:
+        description: Publish validated artifacts to PyPI
+        required: true
+        default: false
+        type: boolean
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build tagged release artifacts
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: public.ecr.aws/docker/library/postgres:16
+        env:
+          POSTGRES_DB: chronem_distribution
+          POSTGRES_USER: chronem
+          POSTGRES_PASSWORD: chronem_distribution_password
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd "pg_isready -U chronem -d chronem_distribution"
+          --health-interval 5s
+          --health-timeout 5s
+          --health-retries 10
+    env:
+      CHRONEM_DISTRIBUTION_DATABASE_URL: postgresql+psycopg://chronem:chronem_distribution_password@127.0.0.1:5432/chronem_distribution
+    steps:
+      - name: Check out release tag
+        uses: actions/checkout@v7
+        with:
+          ref: ${{ inputs.tag }}
+          fetch-depth: 0
+
+      - name: Set up Python 3.12
+        uses: actions/setup-python@v7
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Validate tag, version, and changelog
+        env:
+          RELEASE_TAG: ${{ inputs.tag }}
+        run: python scripts/validate_release_tag.py "$RELEASE_TAG"
+
+      - name: Build and validate distributions
+        uses: ./.github/actions/validate-distribution
+
+      - name: Upload validated release artifacts
+        uses: actions/upload-artifact@v7
+        with:
+          name: python-release-${{ inputs.tag }}
+          path: dist/
+          if-no-files-found: error
+          retention-days: 30
+
+  publish:
+    name: Publish to PyPI with trusted publishing
+    if: ${{ inputs.publish }}
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/chronem/
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - name: Download validated release artifacts
+        uses: actions/download-artifact@v8
+        with:
+          name: python-release-${{ inputs.tag }}
+          path: dist/
+
+      - name: Publish distributions
+        uses: pypa/gh-action-pypi-publish@release/v1

chronem-0.1.0/.gitignore

@@ -0,0 +1,220 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# uv
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs/Zensical documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore that
+#   can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, you
+#   could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

chronem-0.1.0/AGENTS.md

@@ -0,0 +1,132 @@
+# Shared Agent Instructions
+
+This is the canonical engineering entrypoint for every AI agent working in
+Chronem, including Codex and Cursor. Tool-specific files may point here, but must
+not maintain a separate copy of project semantics.
+
+Chronem is the current project name. Issue #38 records the naming decision, and
+Issue #39 performs the clean pre-v0.1.0 rename with no legacy import package.
+
+## Read before implementation
+
+Use this source-of-truth order:
+
+1. The linked GitHub Issue: task scope and acceptance criteria.
+2. This file: shared engineering and workflow rules.
+3. [Open-source plan](docs/open-source-plan.md): strategic North Star, current
+   growth phase, direction changes, and adoption/release priorities.
+4. [Architecture](docs/architecture.md): current boundaries and invariants.
+5. [Accepted decisions](docs/decisions/README.md): durable decisions that must
+   not be silently revisited.
+6. [Product requirements](docs/product-requirements.md): established product
+   requirements and MVP boundaries.
+7. [Roadmap](docs/roadmap.md): technical/project phase ordering and intended
+   outcomes.
+8. [Project status](docs/project-status.md): current implementation and review
+   state.
+9. Tool-specific entrypoints such as `.cursor/rules/*.mdc`.
+
+Also read the current sprint specification when the Issue or project status
+links one. If these sources conflict, stop and surface the contradiction to the
+maintainer/architect. Do not guess or silently change architecture.
+
+## Scope and workflow
+
+- Treat the GitHub Issue as the task-specific source of truth, within accepted
+  architecture and product decisions.
+- Implement only the Issue. Do not add adjacent features, infrastructure, or
+  dependencies without explicit authorization.
+- Never do feature work directly on `main`; use a focused branch and PR.
+- Follow the review and repair lifecycle in
+  [Development workflow](docs/development-workflow.md).
+- An implementation agent must not mark its own work reviewed or approved.
+
+## Architecture boundaries
+
+Chronem is a reusable temporal personal-memory engine, not a generic notes app or
+a thin RAG wrapper. The consumer product is a separate layer.
+
+The hard boundary is:
+
+> Probabilistic systems interpret language. Deterministic code controls memory
+> lifecycle and persistence decisions.
+
+Extractors may propose candidate memories. They must not directly persist,
+delete, supersede, complete, cancel, expire, or otherwise bypass deterministic
+domain rules. The five top-level memory kinds are `FACT`, `PREFERENCE`,
+`CURRENT_STATE`, `EVENT`, and `INTENT`.
+
+Do not change lifecycle semantics, add a memory kind, or cross an accepted
+boundary without explicit Issue scope and an update or addition under
+`docs/decisions/`. See [Architecture](docs/architecture.md) for the complete
+invariants.
+
+## Correctness, security, and privacy
+
+Use this priority order when tradeoffs conflict:
+
+1. user data correctness and safety;
+2. deterministic memory semantics;
+3. preservation of history and provenance;
+4. testability;
+5. simple public API;
+6. performance;
+7. implementation convenience.
+
+User isolation is a domain invariant, not only a higher-layer concern. Any
+operation that receives another user's memory must fail closed rather than
+silently filter it. Never commit secrets, credentials, local environment files,
+or real personal user data.
+
+Prefer no answer to an unsupported personal claim. Preserve capture provenance,
+semantic time, and historical records unless explicit deletion requirements say
+otherwise.
+
+## Code and test conventions
+
+- Python 3.11 or newer; maintain Python 3.11 and 3.12 CI compatibility.
+- Pydantic v2 and full annotations on public interfaces.
+- Keep the domain independent of web frameworks, model providers, databases,
+  vector stores, and network calls.
+- Prefer small pure functions, explicit transitions, and no hidden side effects.
+- Use timezone-aware datetimes, preferably UTC internally.
+- Do not use mutable default arguments, broad exception swallowing, or
+  unexplained type ignores.
+- Add behavior tests for behavior changes; favor sequence tests for lifecycle
+  behavior.
+- Do not weaken lint, typing, or coverage settings to make a change pass.
+
+Before declaring implementation complete, run:
+
+```bash
+ruff check .
+mypy src
+pytest --cov=chronem --cov-report=term-missing
+coverage report --include="*/chronem/lifecycle/*" --fail-under=90
+```
+
+Fix failures rather than bypassing a gate. CI exposes the stable checks
+`Quality gates (Python 3.11)` and `Quality gates (Python 3.12)`.
+
+## Documentation responsibilities
+
+Keep durable context in the repository, not only in chat:
+
+- update `docs/architecture.md` when the current architecture changes;
+- add or update an ADR when an accepted architecture decision changes;
+- update `docs/product-requirements.md` only with maintainer-approved product
+  requirement changes;
+- update `docs/open-source-plan.md` when the open-source strategy, growth
+  phase, milestone interpretation, or major direction changes;
+- update `docs/roadmap.md` when phase sequencing or outcomes change;
+- update `docs/project-status.md` when implementation or review state changes;
+- update tests and user/developer documentation affected by the change.
+
+Unknown future choices must be marked `TBD` instead of guessed. Preserve useful
+history when moving documentation and repair every affected reference.
+
+## Dependency policy
+
+Keep the core lightweight. Before adding a dependency, identify the concrete
+problem, confirm the standard library/current dependencies do not solve it, and
+avoid coupling domain semantics to infrastructure.