papez 0.6.0__tar.gz

papez-0.6.0/.dockerignore

@@ -0,0 +1,19 @@
+__pycache__
+*.pyc
+.git
+.env
+.venv
+venv
+node_modules
+genesys-ui/node_modules
+genesys-ui/.next
+tests
+benchmarks
+phases
+schemas
+*.md
+!README.md
+.mypy_cache
+.pytest_cache
+.ruff_cache
+docker-compose.yml

papez-0.6.0/.env.example

@@ -0,0 +1,48 @@
+# Required: AI providers (OPENAI_API_KEY not needed when GENESYS_EMBEDDER=local)
+OPENAI_API_KEY=sk-...
+ANTHROPIC_API_KEY=sk-ant-...
+
+# Storage backend (this library ships the zero-dependency in-memory store)
+GENESYS_BACKEND=memory
+
+# Embedding provider: openai | local
+# "openai" = OpenAI text-embedding-3-small (1536-dim, requires OPENAI_API_KEY)
+# "local"  = sentence-transformers all-MiniLM-L6-v2 (384-dim, no API key needed)
+#            pip install papez[local]
+GENESYS_EMBEDDER=openai
+
+# Persist path for in-memory backend (saves state across restarts)
+# GENESYS_PERSIST_PATH=.genesys_state.json
+
+# Default user ID (single-tenant / dev mode)
+GENESYS_USER_ID=default_user
+
+# Engine thresholds (all have sensible defaults — only override if tuning)
+# See src/papez/engine/config.py for full list and documentation
+# GENESYS_ACTR_DECAY=0.5                       # ACT-R decay exponent (d parameter)
+# GENESYS_RELEVANCE_VECTOR_WEIGHT=0.7           # Vector similarity weight in relevance
+# GENESYS_RELEVANCE_KEYWORD_WEIGHT=0.3          # Keyword overlap weight in relevance
+# GENESYS_MIN_CONNECTIVITY=0.1                  # Floor for connectivity factor
+# GENESYS_TAGGED_EXPIRE_HOURS=24                # Hours before orphan tagged nodes expire
+# GENESYS_ACTIVE_EPISODIC_THRESHOLD=0.6         # Decay score below this increments counter
+# GENESYS_ACTIVE_EPISODIC_SESSIONS=3            # Consecutive low-score sessions to downgrade
+# GENESYS_DORMANCY_THRESHOLD=0.15               # Decay score threshold for dormancy
+# GENESYS_DORMANCY_DAYS=90                      # Days inactive before dormancy eligible
+# GENESYS_DORMANCY_MAX_REACTIVATIONS=3          # Max reactivations allowed for dormancy
+# GENESYS_FORGETTING_THRESHOLD=0.01             # Decay score floor for forgetting
+# GENESYS_CORE_THRESHOLD=0.55                   # Consolidation score for core promotion
+# GENESYS_CORE_ACTIVATION_WEIGHT=0.4            # Activation weight in consolidation score
+# GENESYS_CORE_HUB_WEIGHT=0.3                   # Hub importance weight
+# GENESYS_CORE_SCHEMA_WEIGHT=0.2                # Schema match weight
+# GENESYS_CORE_STABILITY_WEIGHT=0.1             # Stability weight
+# GENESYS_AUTO_PROMOTE_CATEGORIES=professional,educational,family,location
+# GENESYS_RECALL_MIN_SIMILARITY=                # Recall vector floor (default: embedder-recommended, OpenAI 0.5 / other 0.2)
+# GENESYS_CORE_INJECT_MIN_SIMILARITY=           # Core-injection floor (default: embedder-recommended, OpenAI 0.45 / other 0.2)
+# GENESYS_AUTOLINK_MIN_SIMILARITY=              # Auto-link floor (default: embedder-recommended, OpenAI 0.6 / other 0.45)
+# GENESYS_AUTOLINK_MAX_EDGES=3                  # Max auto-links per memory_store (fan-out cap)
+# GENESYS_AUTOLINK_MAX_NODE_DEGREE=10           # Max auto_link edges a node may accumulate (hub cap)
+# GENESYS_CONFLICT_MIN_SIMILARITY=              # possible_conflicts scan floor (default: the recall floor)
+# GENESYS_CONFLICT_SCAN_K=8                     # possible_conflicts vector window
+# GENESYS_CASCADE_DEPTH=2                       # Max hops for spreading activation
+# GENESYS_CASCADE_DECAY_FACTOR=0.3              # Decay per hop in cascade
+# GENESYS_MAX_INGEST_FILE_MB=100                # Max file size for conversation imports

papez-0.6.0/.gitignore

@@ -0,0 +1,84 @@
+# Python
+__pycache__/
+*.pyc
+*.pyo
+*.egg-info/
+dist/
+build/
+.venv/
+venv/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/
+
+# Node / Next.js
+node_modules/
+.next/
+out/
+.pnp.*
+*.tsbuildinfo
+
+# Environment
+.env
+.env.*
+!.env.example
+
+# OS
+.DS_Store
+
+# Benchmark logs
+benchmarks/logs/
+
+claude_desktop_config.json
+
+# Project-specific exclusions
+/ui/
+/genesys-ui/
+Dockerfile.ui
+data/
+
+# IDE
+.idea/
+.vscode/
+
+# Benchmark data files (large datasets)
+benchmarks/locomo10.json
+benchmarks/locomo_eval_results.json
+benchmarks/locomo_judged.json
+benchmarks/.genesys_state*.json
+
+# Internal docs (not for OSS)
+phases/
+schemas/
+
+# Stitch design files
+*.html
+
+# Claude config
+CLAUDE.md
+
+# Internal notes
+lessons.md
+prompts/
+
+# State snapshots
+.genesys_state*.json
+
+# Database migrations (production only)
+alembic/
+alembic.ini
+
+# Handoff docs
+genesys-neuro-handoff/
+/local_storage/
+
+# private / local / business — never publish
+.claude/
+.playwright-mcp/
+.coverage
+*.docx
+/*.png
+*AUDIT*.md
+yc-*.md
+PATENT_*.md
+seed_*.py

papez-0.6.0/.pre-commit-config.yaml

@@ -0,0 +1,24 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.6.0
+    hooks:
+      - id: check-yaml
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: check-added-large-files
+        args: ['--maxkb=1000']
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.4.8
+    hooks:
+      - id: ruff
+        args: [--fix]
+
+  - repo: local
+    hooks:
+      - id: no-hardcoded-secrets
+        name: Detect hardcoded secrets
+        language: pygrep
+        entry: '(sk_test_\w|sk_live_\w|sk-ant-api\w|AKIA[0-9A-Z]{16})'
+        types: [text]
+        exclude: '(\.env\.example|\.pre-commit-config\.yaml|CONTRIBUTING\.md)$'

papez-0.6.0/CHANGELOG.md

@@ -0,0 +1,65 @@
+# Changelog
+
+## 0.6.0 (unreleased)
+
+### Renamed: genesys-memory is now papez
+
+- PyPI package `genesys-memory` -> `papez`; module `genesys_memory` -> `papez`; console script `genesys-memory` -> `papez`.
+- The MCP server announces itself as `papez`. Update client configs: `claude mcp add papez -- python -m papez`.
+- A final `genesys-memory` 0.6.0 release depends on `papez` and aliases every `genesys_memory.*` import to the same `papez.*` module, with a `DeprecationWarning`.
+- Environment variables keep the `GENESYS_` prefix. Nothing about the data format changed.
+
+## [0.4.2] - 2026-07-17
+
+### Fixed
+
+- **`memory_traverse` induced subgraph now includes the start node** and its incident edges. The in-memory provider returned the start node from `traverse()`; the Postgres provider excludes it (`WHERE id != start`), so on Postgres backends every edge incident to the start node was dropped from `edges` — including the sole match when `edge_types` filtered to a start-incident edge (e.g. traversing from an amended node with `edge_types=["supersedes"]` returned the right neighbor but zero edges). Normalized in the tool layer so all backends behave identically: the start node leads the node set and its edges appear.
+
+## [0.4.1] - 2026-07-17
+
+### Fixed (0.4.0 field-retest round 2)
+
+- **Conflict-hint precision**: `possible_conflicts` numeric check now anchors numbers to the nearest *non-stopword* word and carries the number's unit (currency prefix, `%`, or following unit word). "latency is 200ms" no longer flags "budget is $50,000", and "6 weeks" vs "8 months" no longer collide; "budget $50,000" vs "budget $80,000" still fires.
+- **Recall superseder down-ranking (latent)**: when the superseded memory fell outside the result set, recall marked the *superseding* memory as superseded and decayed it. SUPERSEDES is directed new→old; only targets are tagged now.
+- **`memory_explain` edge direction**: edge entries gain a `direction` ("outgoing"/"incoming") field — an incoming `supersedes` edge previously read as if this node superseded the other. Legacy `target` (= other end) unchanged for compatibility.
+- **Search/enumeration supersede visibility**: `memory_search` hits (both modes) now carry `superseded_by`, so change-cursor consumers can distinguish current from superseded memories without traversing edges.
+
+## [0.4.0] - 2026-07-17
+
+### Added
+
+- **`memory_amend` MCP tool** (tool count 12 → 13). Records a correction as a new memory that `SUPERSEDES` an existing one, reusing the `memory_store` hot path (embedding + auto-link + eventing). The old memory is intentionally kept — recall already decays superseded hits and tags them `superseded_by`, and the transitions engine demotes them naturally. Ownership-checked. Returns `{node_id, supersedes, status: "amended"}`.
+- **Writer-specified typed edges** in `memory_store` via a new `related` argument: `[{"id", "type"}]`, directed `new_node --type--> target`, validated fail-fast (invalid edge types rejected before the node is created). Writers can now express `supersedes` / `contradicts` / `part_of` etc. instead of everything collapsing to `caused_by`. The legacy `related_to` argument is unchanged (still `caused_by`).
+- **`category` argument** on `memory_store`, closing the half-wired category path (nodes carried a `category` field and `list_core_memories` filtered on it, but there was no way to set it). A caller-set category is never overwritten by the background LLM classifier.
+- **Concise recall**: `memory_recall(verbosity="concise")` returns only `id/summary/status/score/activation/is_core` (plus `superseded_by` when set) and skips the expensive causal-chain enrichment. `verbosity="full"` remains the default and is unchanged. Reactivation writes still occur in both modes.
+- **`activation` alias** for `decay_score` on every recall hit and in `memory_explain`, plus a `score_model` block in `memory_explain` (formula, live per-force `connectivity_factor`/`activation_factor`, and a `staleness_note`). Makes the score legible: it is an activation/retention weight that *rises* on retrieval, not a countdown to deletion. See `docs/scoring.md`.
+- **`memory_traverse` now returns edges**: `edges` (`source/target/type/weight/created_by`) and `edge_count` for the induced subgraph among reachable nodes — a superset of the BFS tree, so paths can be reconstructed. Backed by a new `get_connecting_edges()` storage method (edge-type + org-visibility filtering done in storage; de-duped by edge id). The tool degrades gracefully when the provider does not implement `get_connecting_edges` (returns `edges: []`, `edge_count: 0` — same guard pattern as `get_causal_chains_batch`). **Parity note for genesys-server:** the postgres, falkordb, mongo, and obsidian providers do NOT yet implement `get_connecting_edges` and need it added to return traverse edges in production; until then production `memory_traverse` returns empty `edges`.
+- **`active_since` filter** on `memory_search` (filters on `last_reactivated_at`), a sibling of the existing `since` (which filters `created_at`). Both accept tz-naive ISO dates (treated as UTC).
+- **Enumeration mode on `memory_search`** ("what's new since I last looked"): an empty `query` skips vector search entirely and lists nodes by `last_reactivated_at` descending, honoring the same filters — works with no embedder configured, no seed query needed. Search hits (both modes) now also carry `last_reactivated_at` and `source_session` (additive fields) for provenance.
+- **Embedder-aware auto-link tuning**: `GENESYS_AUTOLINK_MIN_SIMILARITY` (env override), `GENESYS_AUTOLINK_MAX_EDGES` (default 3, per-store fan-out cap), and `GENESYS_AUTOLINK_MAX_NODE_DEGREE` (default 10, per-node *accumulation* cap — a node that already carries that many `auto_link` edges accretes no more, so hubs stop growing one edge per store). The similarity floor resolves via `config.resolve_autolink_min_similarity()` — explicit env > embedder recommendation (OpenAI 0.6 / local 0.45) > 0.45 fallback — replacing the hardcoded 0.3. The non-OpenAI floor sits *above* the local genuine-match band top (~0.4) because MiniLM noise pairs were observed at ~0.44: under local embeddings only near-duplicate content auto-links. `recommended_autolink_min_similarity` added to the embedding providers.
+- **`possible_conflicts` hint** on `memory_store`: a pure-stdlib `heuristic_conflict_signal` flags lexical numeric/negation divergence against vector-similar candidates. Advisory only — never materialized as `CONTRADICTS` edges. The conflict scan has its **own floor**, decoupled from the auto-link floor (`GENESYS_CONFLICT_MIN_SIMILARITY`, defaulting to the recall floor via `config.resolve_conflict_min_similarity()`) and a wider candidate window (`GENESYS_CONFLICT_SCAN_K`, default 8) — so raising the auto-link floor doesn't shrink conflict detection. `numeric_mismatch` only fires when differing numbers appear in a *comparable position* (same nearest-preceding context word, e.g. "costs 50" vs "costs 75"), not on any two texts that merely both contain numbers (dates vs IDs no longer trigger it).
+- **Structured tool errors in the stdio server**: `call_tool` no longer propagates tool exceptions as protocol-level MCP failures. Missing required arguments and tool exceptions return a `{"error": ..., "retryable": bool}` payload; `retryable` is true only for read tools (`memory_recall`/`memory_search`/`memory_traverse`/`memory_explain`/`memory_stats`/`list_core_memories`), matching the README retry guidance (never blind-retry writes).
+- `docs/scoring.md` — the scoring legibility doc (three forces, stability, status/pinning override, conjunctive forgetting, worked numbers).
+- `SUPPORTIVE_EDGE_TYPES` and `NEGATIVE_EDGE_TYPES` enum sets in `models/enums.py` for explicit edge classification.
+- `get_supportive_degree()` method on all storage providers (base protocol, in-memory, Postgres, FalkorDB, MongoDB, Obsidian).
+- LLM reasoning is now captured in contradiction detection and causal inference edge metadata. The `reason` field from `detect_contradiction` and `infer_causal_edges` is persisted in the edge's `metadata` dict.
+
+### Changed
+
+- **Auto-link is less permissive (fixes the "hairball")**: higher, embedder-aware similarity floor plus a per-store fan-out cap (`AUTOLINK_MAX_EDGES`) keep traversal neighborhoods scoped. Auto-linking now de-dupes against *any* existing edge between a pair (any type, either direction), so a `user_explicit` `caused_by` is never shadowed by a parallel `auto_link related_to`.
+- `memory_store`'s `summary` is generated by word-boundary truncation (`≤200` chars incl. ellipsis) so words are never split mid-token. Still truncation, not an LLM summary.
+
+- **Edge semantics correctness (breaking behavior change):** Nodes with only `CONTRADICTS` or `SUPERSEDES` edges are now considered orphans for forgetting purposes. Previously, any edge — including contradiction edges — prevented a node from being classified as an orphan, which meant contradicted memories were immune to pruning and could be incorrectly promoted to core status.
+
+- **Core promotion now uses supportive degree:** The hub score component of `consolidation_score()` now counts only supportive edges (`CAUSED_BY`, `SUPPORTS`, `DERIVED_FROM`, `RELATED_TO`), excluding `CONTRADICTS` and `SUPERSEDES`. Nodes whose connectivity comes entirely from contradiction edges will no longer be promoted to core. **Note for existing instances:** This change is forward-only. Nodes already promoted to CORE status are not re-evaluated automatically (`evaluate_core_promotion` skips CORE nodes). Existing CORE nodes promoted under the old rules stay CORE until manually demoted via `unpin_memory`. Production instances upgrading to this version should consider running a one-time backfill to re-evaluate CORE nodes under the stricter rules — specifically, any CORE node whose only edges are CONTRADICTS/SUPERSEDES may have been mis-promoted.
+
+- **Superseded nodes deprioritized in retrieval:** Nodes with incoming `SUPERSEDES` edges now receive a 0.3x multiplier on their retrieval rank score. They still appear in results (for audit trail purposes) but are ranked lower than their replacements.
+
+### Fixed
+
+- **Positional backward compatibility of `memory_store`**: the new `related` and `category` parameters are appended *after* the original positional tail (`created_at`, `visibility`, `org_id`), not inserted mid-signature — existing positional callers of the published API keep working.
+- `memory_search`'s `since`/`active_since` filters no longer raise `TypeError` on tz-naive ISO input (e.g. `"2050-01-01"`); naive timestamps are normalized to UTC, same as `memory_store`'s `created_at`.
+- `is_orphan()` across all storage providers now uses supportive degree instead of raw degree. A node with only negative edges (contradictions, supersessions) is correctly identified as an orphan.
+- `get_orphans()` updated to match new orphan semantics across all providers.
+- Contradiction reasoning was being requested from the LLM but discarded at parse time. Now captured and stored.
+- Causal inference prompt now requests reasoning; previously only asked for target, type, and confidence.

papez-0.6.0/CLA.md

@@ -0,0 +1,49 @@
+# Papez Contributor License Agreement
+
+Thank you for your interest in contributing to Papez, owned and maintained by Astrix Labs ("Company"). This Contributor License Agreement ("Agreement") is a legal document that clarifies the intellectual property rights granted with contributions from any person or entity ("Contributor") to the Company for the Papez project.
+
+By submitting a pull request or otherwise contributing to the Papez project, you accept and agree to the following terms and conditions.
+
+## 1. Definitions
+
+**"Contribution"** means any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by the Contributor to the Company for inclusion in the Papez project. "Submitted" means any form of electronic, verbal, or written communication sent to the Company or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Company, but excluding communication that is conspicuously marked or otherwise designated in writing by the Contributor as "Not a Contribution."
+
+**"Copyright"** means all rights protecting works of authorship, including copyright, moral, and neighboring rights, as appropriate, for the full term of their existence.
+
+## 2. Grant of Copyright License
+
+Subject to the terms and conditions of this Agreement, the Contributor hereby grants to the Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Contributions and such derivative works.
+
+## 3. Grant of Patent License
+
+Subject to the terms and conditions of this Agreement, the Contributor hereby grants to the Company a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer Contributions, where such license applies only to those patent claims licensable by the Contributor that are necessarily infringed by the Contribution alone or by combination of the Contribution with the project to which the Contribution was submitted.
+
+## 4. Right to Grant Licenses
+
+The Contributor represents that they are legally entitled to grant the above licenses. If the Contributor's employer(s) has rights to intellectual property that the Contributor creates, the Contributor represents that they have received permission to make Contributions on behalf of that employer, or that the employer has waived such rights for Contributions to the Papez project.
+
+## 5. Original Work
+
+The Contributor represents that each Contribution is the Contributor's original creation. The Contributor represents that Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which the Contributor is aware and which are associated with any part of the Contributions.
+
+## 6. No Support Obligation
+
+The Contributor is not expected to provide support for Contributions, except to the extent the Contributor desires to provide support. Support, if any, is provided on a voluntary basis.
+
+## 7. Relicensing Rights
+
+The Contributor acknowledges and agrees that the Company may, at its sole discretion, relicense the Papez project (including the Contributor's Contributions) under different license terms, including but not limited to commercial or proprietary licenses. This right is necessary for the Company to offer dual-licensed commercial deployments of Papez.
+
+## 8. Notification
+
+The Contributor agrees to notify the Company of any facts or circumstances of which the Contributor becomes aware that would make these representations inaccurate in any respect.
+
+---
+
+## How to Sign
+
+By opening a pull request against the Papez repository, you acknowledge that you have read this Agreement and agree to its terms. Your git commit metadata (name and email address) serves as your electronic signature.
+
+If you are contributing on behalf of a company or organization, please have an authorized representative email cla@astrixlabs.ai with the subject "Corporate CLA — [Company Name]" to sign a corporate version of this agreement.
+
+For questions, contact: cla@astrixlabs.ai

papez-0.6.0/CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributing to Papez
+
+Thanks for your interest in contributing! Papez is open source under the [GNU Affero General Public License v3.0](LICENSE).
+
+## Contributor License Agreement
+
+All contributors must agree to our [Contributor License Agreement](CLA.md) before their code can be merged. By opening a pull request, you acknowledge that you have read the CLA and agree to its terms. Your git commit metadata (name and email) serves as your electronic signature.
+
+The CLA grants Astrix Labs the right to include your contributions under the project's license (AGPLv3) and, where necessary, under commercial license terms for the hosted Papez service. You retain copyright over your contributions.
+
+## Architecture overview
+
+Papez is a scoring engine, causal graph, and lifecycle manager for AI memory. The codebase is organized as:
+
+```
+src/papez/
+├── engine/             # Scoring, transitions, forgetting, reactivation
+│   ├── config.py       # All tunable thresholds (env-configurable)
+│   ├── scoring.py      # Three-force multiplicative decay scoring
+│   ├── transitions.py  # Status FSM (TAGGED -> ACTIVE -> EPISODIC -> DORMANT)
+│   ├── forgetting.py   # Conjunctive active forgetting
+│   └── reactivation.py # BFS cascade reactivation
+├── core_memory/        # Core promotion logic (graph-derived)
+├── storage/            # Storage provider abstractions + in-memory implementation
+│   ├── base.py         # Abstract interfaces (GraphStorageProvider, etc.)
+│   └── memory.py       # In-memory (zero deps)
+├── retrieval/          # Embedding providers (OpenAI, local sentence-transformers)
+├── mcp/                # MCP tool definitions
+├── server.py           # Lightweight stdio MCP server
+└── providers.py        # Provider wiring (in-memory backend, optional embeddings)
+```
+
+Key design principles:
+- **Storage abstraction is mandatory.** All data access goes through provider interfaces in `storage/base.py`. Never import a database client directly in business logic.
+- **Background processing for heavy operations.** Embedding generation, entity extraction, LLM-based inference, and consolidation are all async background tasks.
+- **The scoring formula is sacred.** `decay_score = relevance x connectivity x reactivation`. Multiplicative — zero on any axis means zero total.
+
+## Getting started
+
+1. Fork the repo and clone it
+2. Install dependencies: `pip install -e ".[dev]"`
+3. Run tests: `pytest`
+
+```bash
+# Run the lightweight MCP server (stdio transport, no infrastructure needed)
+python -m papez
+```
+
+## Code style
+
+- **Python 3.11+**, async-first
+- **Linting**: `ruff check src/` (config in `pyproject.toml`, line length 120)
+- **Type checking**: `mypy src/papez --ignore-missing-imports` (strict mode configured)
+- **Formatting**: follow existing patterns — type hints throughout, minimal comments
+- Engine thresholds live in `engine/config.py` and are env-configurable. Don't hardcode magic numbers in engine files.
+
+## Testing
+
+```bash
+# Run all unit tests
+pytest tests/ -v
+
+# With coverage
+pytest tests/ -v --cov=src/papez --cov-report=term-missing
+```
+
+Tests are in `tests/` and use `pytest-asyncio` (auto mode). When adding new engine logic, add corresponding test cases in the relevant test file.
+
+## Pull requests
+
+- Keep PRs focused — one feature or fix per PR
+- Add tests for new functionality
+- Make sure `pytest` and `ruff check src/` pass before submitting
+- If your change touches engine logic (scoring, transitions, forgetting, promotion), run the full test suite — these modules are tightly coupled
+
+## Reporting issues
+
+Open an issue on GitHub with:
+- Steps to reproduce
+- Python version and backend
+- Relevant error output or logs
+
+## Good first issues
+
+Look for issues labeled [`good first issue`](https://github.com/Astrix-Labs/papez/labels/good%20first%20issue). These are scoped, well-defined tasks suitable for new contributors.
+
+## Code of conduct
+
+Be kind. We're all here to build something useful.

papez-0.6.0/Dockerfile.mcp

@@ -0,0 +1,10 @@
+FROM python:3.12-slim
+
+WORKDIR /app
+
+COPY pyproject.toml README.md ./
+COPY src/ src/
+
+RUN pip install --no-cache-dir .
+
+ENTRYPOINT ["python", "-m", "papez"]