portable-memory 0.1.2__tar.gz

portable_memory-0.1.2/.github/ISSUE_TEMPLATE/adapter_or_implementation.yml

@@ -0,0 +1,18 @@
+name: Adapter or implementation
+description: Propose or track an adapter (e.g. ChatGPT/Claude/Letta export) or an implementation in another language.
+labels: ["adapter", "interop"]
+body:
+  - type: input
+    id: target
+    attributes:
+      label: Source / language
+      description: e.g. "ChatGPT export → .mem", or "Go implementation of the reader".
+    validations:
+      required: true
+  - type: textarea
+    id: mapping
+    attributes:
+      label: Mapping / scope
+      description: How does it map to the model (episode/core/entity/…)? What rides in `ext`/passthrough? What conformance level do you target?
+    validations:
+      required: true

portable_memory-0.1.2/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,39 @@
+name: Bug report
+description: Something in the SDK or a bundle doesn't behave as specified.
+labels: ["bug"]
+body:
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened
+      description: What did you do, what did you expect, and what happened instead?
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Reproduction
+      description: Steps, code, or a minimal `.mem` bundle that reproduces it.
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: SDK version / commit
+      description: e.g. "portable-memory 0.1.0" or a git commit SHA.
+    validations:
+      required: true
+  - type: input
+    id: python
+    attributes:
+      label: Python version
+      description: Output of `python --version` (e.g. "3.12.4").
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      description: e.g. "Ubuntu 24.04", "macOS 15.1", "Windows 11".
+    validations:
+      required: true

portable_memory-0.1.2/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/MacPaw/portable-memory/security/advisories/new
+    about: Please report vulnerabilities privately via GitHub Security Advisories, not as a public issue.

portable_memory-0.1.2/.github/ISSUE_TEMPLATE/spec_change.yml

@@ -0,0 +1,32 @@
+name: Spec / format change
+description: Propose a change to the on-disk format, schemas, or a normative requirement.
+labels: ["spec"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Format-affecting changes are discussed **before** implementation (see
+        CONTRIBUTING and GOVERNANCE). Please describe the change and its compatibility
+        impact.
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed change
+      description: What should change in the spec / schemas, and why?
+    validations:
+      required: true
+  - type: dropdown
+    id: compat
+    attributes:
+      label: Compatibility impact
+      options:
+        - Backward-compatible addition (minor format bump)
+        - Breaking change (major format bump)
+        - Clarification only (no wire change)
+    validations:
+      required: true
+  - type: textarea
+    id: impls
+    attributes:
+      label: Affected implementations / adapters
+      description: Which implementations or adapters would need to change? (e.g. this Python SDK, the Swift SDK, an adapter.)

portable_memory-0.1.2/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+<!-- Thanks for contributing to Portable Memory! -->
+
+## What & why
+
+<!-- What does this change and why? Link any issue. -->
+
+## Type of change
+
+- [ ] SDK change (no wire-format impact)
+- [ ] **Spec / format change** (discussed in an issue first — see CONTRIBUTING)
+- [ ] New adapter / other-language implementation
+- [ ] Docs / conformance / fixtures
+
+## Checklist
+
+- [ ] `pytest -q` passes (run `pip install -e .[dev]` first)
+- [ ] Added/updated tests for the change
+- [ ] If the wire format changed: the spec, `Schemas/`, the Python DTOs, and the sample
+      fixture are all in sync, and the `format` version bump follows GOVERNANCE
+- [ ] If the wire format changed: kept parity with the Swift reference SDK
+      (bundles stay byte-identical across both implementations)
+- [ ] Updated `CHANGELOG.md` under **Unreleased**
+- [ ] Commits are signed off (`git commit -s`, DCO)

portable_memory-0.1.2/.github/workflows/ci.yml

@@ -0,0 +1,37 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: ${{ matrix.os }} (Python ${{ matrix.python-version }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install (editable, with dev extras)
+        run: pip install -e .[dev]
+      - name: Test
+        run: pytest -q
+
+  fixture-integrity:
+    name: Conformance fixture checksums
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Verify sample.mem CHECKSUMS
+        run: cd Conformance/fixtures/sample.mem && sha256sum -c CHECKSUMS

portable_memory-0.1.2/.github/workflows/publish.yml

@@ -0,0 +1,65 @@
+name: Publish to PyPI
+
+# Publishes the package when a GitHub release is published (tag == pyproject version).
+# Uses PyPI Trusted Publishing (OIDC) — no API token is stored anywhere. One-time setup on
+# pypi.org: project "portable-memory" → Publishing → add a GitHub publisher with
+# owner "MacPaw", repository "portable-memory", workflow "publish.yml", environment "pypi".
+# (For the very first release, register it as a *pending* publisher under your account.)
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade pip build twine
+          python -m build
+          python -m twine check dist/*
+
+      - name: Verify the package version matches the release tag
+        if: github.event_name == 'release'
+        run: |
+          TAG="${GITHUB_REF_NAME}"
+          VER="$(python -c 'import tomllib; print(tomllib.load(open("pyproject.toml", "rb"))["project"]["version"])')"
+          if [ "$TAG" != "$VER" ]; then
+            echo "::error::release tag '$TAG' does not match pyproject version '$VER'"
+            exit 1
+          fi
+
+      - name: Smoke-test the built wheel
+        run: |
+          python -m venv /tmp/smoke && /tmp/smoke/bin/pip install -q dist/*.whl
+          /tmp/smoke/bin/python -c "import portable_memory, portable_memory.adapters; print('portable_memory', portable_memory.__version__ if hasattr(portable_memory, '__version__') else 'ok')"
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # OIDC token for Trusted Publishing
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - uses: pypa/gh-action-pypi-publish@release/v1

portable_memory-0.1.2/.gitignore

@@ -0,0 +1,17 @@
+# Byte-compiled / cached
+__pycache__/
+*.pyc
+*.pyo
+*.pyd
+
+# Test / type-checker caches
+.pytest_cache/
+.mypy_cache/
+
+# Build artifacts / packaging
+build/
+dist/
+*.egg-info/
+
+# Virtual environments
+.venv/

portable_memory-0.1.2/CHANGELOG.md

@@ -0,0 +1,70 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/). The SDK package version is
+independent of the on-disk **format** version (`format` in the manifest).
+
+## [Unreleased]
+
+## [0.1.2] - 2026-09-13
+
+First release published to PyPI: `pip install portable-memory`.
+
+### Added
+
+- **Paper citation** — README callout and *Citation* section (BibTeX), `CITATION.cff` for
+  GitHub's "Cite this repository", and a paper link in the spec header (the spec stays
+  byte-identical with the Swift repository). Paper:
+  <https://research.macpaw.com/publications/portable-memory>.
+- **PyPI packaging** — project URLs (paper, changelog, issues), richer keywords and
+  classifiers, and a Trusted-Publishing release workflow
+  (`.github/workflows/publish.yml`) that builds, checks, and publishes the package when
+  a GitHub release is published — no long-lived API token.
+
+### Fixed
+
+- **Package version alignment** — `pyproject.toml` still declared `0.1.0` while the
+  repository was tagged `0.1.1`. The package version now tracks the git tag, and the
+  release workflow refuses to publish when they disagree.
+
+## [0.1.1] - 2026-07-03
+
+First public release of the Python reference SDK, reaching parity with the Portable Memory
+format (`format` **1.0.0**) and byte-for-byte interoperability with the
+[Swift reference SDK](https://github.com/MacPaw/portable-memory-swift). Versioned `0.1.1`
+to match the Swift SDK's release of the same day.
+
+### Added
+
+- **Python SDK** — `BundleExporter` / `BundleImporter` / `BundleValidator`, the
+  `PortableMemoryStore` seam an adopter subclasses, and dataclass DTOs for all record
+  kinds. Fully **synchronous** — local file I/O is done inline, no `async`/`await`.
+- **Canonical JSON** — the serialization/hashing helpers in `portable_memory/_codec.py`
+  produce output byte-for-byte identical to the Swift SDK's `MemCodec` (spec §1.1), so
+  checksums and signatures match across implementations. Whole-valued floats serialize
+  as integers, timestamps are whole-second UTC `Z`, NaN/Infinity are rejected, and
+  scalar fields are type-checked on decode.
+- **Pure-stdlib core** — the core depends only on the standard library (`json`, `hashlib`,
+  `dataclasses`, `datetime`). Signing is an optional `[signing]` extra (`cryptography`),
+  imported lazily so bundles can be produced and read without it.
+- **Deletion propagation (L2)** — portable tombstones with proof-of-reach, applied before
+  additions; no-resurrection enforced for **every** kind (not just episodes).
+- **Ed25519 signing (L3)** — detached bundle signatures (`manifest.sig`) and tombstone
+  signatures, verified against caller-supplied trusted keys.
+- **Cross-vendor losslessness** — foreign episode fields via `ext` and foreign kinds via
+  verbatim passthrough; a mem0 adapter (`portable_memory/adapters/mem0.py`, verified
+  against mem0's documented export shapes), an OpenAI adapter for the ChatGPT data
+  export (`adapters/openai.py` — `conversations.json` + a saved-memories fallback), and
+  a Claude adapter for Claude memory files (`adapters/claude.py` — `MEMORY.md` + topic
+  files with frontmatter).
+- **JSON Schemas** for every record kind, the manifest, tombstones, and the audit log,
+  validated against samples in the test suite.
+- **Conformance kit** — a sample `.mem` fixture and a signed fixture shared with the
+  Swift SDK, plus golden canonical-JSON vectors
+  (`Conformance/vectors/canonical-json.json`) that every implementation must reproduce.
+- **Untrusted-input hardening** — path-traversal + symlink-escape rejection, unlisted-file
+  rejection, and a per-file size bound (`MemLimits`).
+
+[Unreleased]: https://github.com/MacPaw/portable-memory/compare/0.1.2...HEAD
+[0.1.2]: https://github.com/MacPaw/portable-memory/compare/0.1.1...0.1.2
+[0.1.1]: https://github.com/MacPaw/portable-memory/releases/tag/0.1.1

portable_memory-0.1.2/CITATION.cff

@@ -0,0 +1,28 @@
+cff-version: 1.2.0
+message: "If you use Portable Memory in your work, please cite the paper below."
+title: "Portable Memory — Python reference SDK"
+type: software
+license: MIT
+repository-code: "https://github.com/MacPaw/portable-memory"
+url: "https://research.macpaw.com/publications/portable-memory"
+authors:
+  - family-names: Kryvoblotskyi
+    given-names: Sergii
+  - family-names: Stulova
+    given-names: Nataliia
+  - family-names: Hamolia
+    given-names: Vladyslav
+preferred-citation:
+  type: generic
+  title: "Memory Belongs to the User: Portable Memory, an Open Standard Proposal for Cross-Vendor AI Memory"
+  authors:
+    - family-names: Kryvoblotskyi
+      given-names: Sergii
+    - family-names: Stulova
+      given-names: Nataliia
+    - family-names: Hamolia
+      given-names: Vladyslav
+  year: 2026
+  month: 7
+  url: "https://research.macpaw.com/publications/portable-memory"
+  notes: "Standards proposal — preprint for community review. MacPaw Research."

portable_memory-0.1.2/CODE_OF_CONDUCT.md

@@ -0,0 +1,50 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our 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, socio-economic status, nationality, personal appearance,
+race, 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 include demonstrating
+empathy and kindness, respecting differing opinions and experiences, giving and
+gracefully accepting constructive feedback, and focusing on what is best for the
+community.
+
+Unacceptable behavior includes sexualized language or imagery, trolling or derogatory
+comments, public or private harassment, publishing others' private information without
+permission, and other conduct which could reasonably be considered inappropriate in a
+professional setting.
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing these standards and will
+take appropriate and fair corrective action in response to any behavior they deem
+inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces and when an individual is
+officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to
+the maintainers responsible for enforcement at **tech-research@macpaw.com**. All complaints
+will be reviewed and investigated promptly and fairly. Community leaders are obligated to
+respect the privacy and security of the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1,
+available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

portable_memory-0.1.2/CONTRIBUTING.md

@@ -0,0 +1,69 @@
+# Contributing to Portable Memory
+
+Thanks for helping build an open, vendor-neutral memory format. Contributions of every
+kind are welcome — SDK code, new adapters, other-language implementations, spec
+clarifications, and conformance fixtures.
+
+## Ways to contribute
+
+- **Implement the spec** in another language. The format is defined by
+  [`Spec/portable-memory-spec.md`](Spec/portable-memory-spec.md) and the language-neutral
+  [`Schemas/`](Schemas); you don't need this Python SDK to interoperate.
+- **Write an adapter** that maps another vendor's export into the model (see
+  `portable_memory/adapters/mem0.py` for the pattern — map what's modeled, keep the rest
+  in `ext`/`metadata` so a later export stays lossless).
+- **Improve the SDK** — bug fixes, robustness, docs.
+- **Propose a spec change** (see below).
+
+## Building & testing
+
+```sh
+pip install -e .[dev]
+pytest
+```
+
+The `[dev]` extra pulls in `pytest`, `jsonschema` (for validating `Schemas/` against
+samples), and `cryptography` (so signing paths are exercised). Please add a test with any
+behavior change; the reference in-memory store in the test suite shows the shape an adopter
+implements by subclassing `PortableMemoryStore`.
+
+## SDK changes vs spec changes
+
+- **SDK change** (code/tests/docs, no wire-format impact): open a PR.
+- **Spec change** (anything that alters the on-disk format, schemas, or a normative
+  requirement): open an issue using the **Spec change** template first, so the design can
+  be discussed before implementation. Format-affecting changes follow semver on the
+  manifest `format` field and are decided per [`GOVERNANCE.md`](GOVERNANCE.md).
+
+Keep the spec, the JSON Schemas, the Python DTOs, and the sample fixture **in sync** — a PR
+that changes one usually needs to touch the others. `pytest` validates the shipped fixture;
+please also validate `Schemas/` against your samples. Because there are now two reference
+SDKs (Python here and [Swift](https://github.com/MacPaw/portable-memory-swift)), a
+format-affecting change must land in both before the format version is bumped — see
+[`GOVERNANCE.md`](GOVERNANCE.md).
+
+## Conventions
+
+- Match the surrounding style; keep the SDK dependency-light. The core is **pure standard
+  library** (`json`, `hashlib`, `dataclasses`, `datetime`); the only optional dependency is
+  `cryptography`, behind the `[signing]` extra and imported lazily. Don't add runtime
+  dependencies to the core.
+- The SDK is fully **synchronous** — local file I/O is done inline, no `async`/`await`.
+  (The Swift SDK uses `async` for actor isolation; the Python side has no such requirement.)
+- Canonical JSON rules are normative (spec §1.1) — don't introduce serialization that
+  diverges from the canonical helpers in `portable_memory/_codec.py`. Serialize and hash
+  through those helpers so bytes match the Swift SDK exactly.
+- Update [`CHANGELOG.md`](CHANGELOG.md) under **Unreleased**.
+
+## Developer Certificate of Origin (DCO)
+
+We use the [DCO](https://developercertificate.org/) rather than a CLA. Sign off each
+commit (`git commit -s`), certifying you have the right to submit it under the project's
+MIT license:
+
+```
+Signed-off-by: Your Name <you@example.com>
+```
+
+By contributing, you agree your contributions are licensed under the repository's
+[MIT license](LICENSE).

portable_memory-0.1.2/Conformance/README.md

@@ -0,0 +1,65 @@
+# Conformance kit
+
+How to claim a Portable Memory conformance level, and how to check a bundle.
+
+## Levels
+
+| Level | Requirement | How to demonstrate |
+|---|---|---|
+| **L0** | Read / Export | `BundleValidator().validate(bundle=...)` returns `ok` on your exported bundle. |
+| **L1** | Import / Merge | Export → import into a fresh store reproduces counts/content; a second import is a no-op (idempotent). |
+| **L2** | **Deletion propagation** (badge) | Delete an item, then prove it is unreachable via **every** route your engine supports + a tombstone was written (the probe below). |
+| **L3** | Governed | Full audit trail + Evidence Pack export + signed tombstones. |
+
+## Validate a bundle (L0)
+
+```python
+from portable_memory import BundleValidator
+
+result = BundleValidator().validate(bundle="path/to/bundle.mem")
+assert result.ok, "\n".join(result.issues)
+```
+
+The validator checks: the manifest parses, every listed file matches its `sha256` and
+byte count, no unlisted/injected files are present, and every known-kind stream
+decodes. Unknown (vendor) kinds are intentionally opaque and pass through.
+
+Language-neutral validation: the `Schemas/` JSON Schemas cover `manifest.json`, every
+`items/<kind>.jsonl` record kind, and the `audit/` records (`tombstone`, `log`), so a
+non-Python implementer can validate a bundle without the SDK. Unknown (vendor) kinds have
+no schema by design — they are opaque passthrough.
+
+## The deletion-propagation probe (L2 — the gate)
+
+This is the guarantee the badge rests on. For each of a handful of distinctive
+"needle" memories:
+
+1. Add it; confirm it is retrievable.
+2. Delete it.
+3. Assert it is unreachable via **every** route your engine exposes — at minimum:
+   dense vector search, lexical/full-text, any k-hop graph, any embedding/derived
+   cache, the bi-temporal `as_of` historical view, and any synced replica.
+4. Assert a portable tombstone was written for it (positive proof, not mere absence).
+
+A conformant `delete` reaches every artifact derived from the content; a conformant
+`import` applies tombstones **before** additions, so a bundle that still carries the
+stale rows can never resurrect deleted content.
+
+The reference SDK demonstrates the offline, bundle-level part of this probe in
+`tests/` — the tombstone-first / no-resurrection cases: tombstones are applied before
+additions, so a stale bundle re-import can never resurrect a deleted item of **any**
+kind. The live, all-routes assertion (dense / lexical / graph / cache / replica) is
+completed by an adopter against its own retrieval stack.
+
+## Fixtures
+
+`fixtures/sample.mem/` is a small, valid bundle exercising episodes, an entity, an
+edge, an episode carrying a foreign `ext` field, a vendor-specific passthrough kind,
+and a tombstone (with proof-of-reach). Use it to test your importer and validator.
+
+## Vectors
+
+`vectors/` holds the language-neutral conformance oracle — `canonical-json.json`
+(`input → canonical bytes → sha256`) and a `signed.mem` fixture with its test keypair.
+Reproduce every vector and you are byte-interoperable with the reference SDKs. See
+[`vectors/README.md`](vectors/README.md).

portable_memory-0.1.2/Conformance/fixtures/sample.mem/CHECKSUMS

@@ -0,0 +1,5 @@
+1c7a4081b2f8601c37633442837f62acc9d7afbc39de68f5024f77d092a40b8d  audit/tombstones.jsonl
+a46150e36da3bed28dead6afc6c14d39c6737758389c5ceb4a2638825bb77869  items/edge.jsonl
+7473a09c9fec9ec42f7a1497314b7aa1477d16a827332d7f257605b2490cd44b  items/entity.jsonl
+67ef60b8686b8d5cfdde69700fc54ddb513caa97480c81228dcac11a6a737de5  items/episode.jsonl
+83654ab56d668010b6d8957ec8f3888c6df14d1ff031b62f20908af1e44e1243  items/vendorThing.jsonl

portable_memory-0.1.2/Conformance/fixtures/sample.mem/audit/tombstones.jsonl

@@ -0,0 +1 @@
+{"actor":"user","deletedAt":"2024-03-09T16:00:00Z","derived":{"chunkIDs":[],"edgeIDs":[],"embeddingCacheKeys":["abc"],"entityIDs":[],"episodeLinkCount":0,"factIDs":["fact_x"],"sentenceIDs":[]},"id":"tomb_0001","op":"delete","reason":"user erasure","targetID":"ep_legacy","targetKind":"episode"}

portable_memory-0.1.2/Conformance/fixtures/sample.mem/items/edge.jsonl

@@ -0,0 +1 @@
+{"confidence":0.9,"dstEntityID":"ent_pv","edgeType":"launches_on","evidenceEpisodeIDs":["ep_0001"],"id":"edge_0001","ingestionTime":"2023-11-14T22:13:20Z","srcEntityID":"ent_pv","tValidFrom":"2023-11-14T22:13:20Z"}

portable_memory-0.1.2/Conformance/fixtures/sample.mem/items/entity.jsonl

@@ -0,0 +1 @@
+{"aliases":[],"canonicalName":"Project Vermilion","id":"ent_pv","sensitivity":"low","summary":"","type":"project","updatedAt":"2023-11-14T22:13:20Z"}

portable_memory-0.1.2/Conformance/fixtures/sample.mem/items/episode.jsonl

@@ -0,0 +1,2 @@
+{"accessCount":0,"actors":[],"categories":[],"confidence":0.7,"details":"Project Vermilion launches on Pi Day 2027.","eventTime":"2023-11-14T22:13:20Z","extractionState":"done","id":"ep_0001","importance":0.5,"ingestionTime":"2023-11-14T22:13:20Z","lifecycleState":"HOT","mentionTime":"2023-11-14T22:13:20Z","metadata":{},"pinned":false,"sensitivity":"low","sourceType":"note","summary":"Project Vermilion launches on Pi Day 2027.","vaultRefs":[]}
+{"accessCount":0,"actors":[],"categories":[],"confidence":0.7,"details":"The Reykjavik lab is led by Dr. Sabine Holt.","eventTime":"2023-11-14T22:13:20Z","extractionState":"done","id":"ep_0002","importance":0.5,"ingestionTime":"2023-11-14T22:13:20Z","lifecycleState":"HOT","mentionTime":"2023-11-14T22:13:20Z","metadata":{},"pinned":false,"sensitivity":"low","sourceType":"note","summary":"The Reykjavik lab is led by Dr. Sabine Holt.","vaultRefs":[],"vendorScore":0.92}

portable_memory-0.1.2/Conformance/fixtures/sample.mem/items/vendorThing.jsonl

@@ -0,0 +1 @@
+{"id":"vt_1","blob":"opaque"}

portable_memory-0.1.2/Conformance/fixtures/sample.mem/manifest.json

@@ -0,0 +1 @@
+{"capabilities":["bitemporal","tombstones","redaction","evidence-pack","ext","passthrough"],"conformanceLevel":"L2","counts":{"edge":1,"entity":1,"episode":2,"tombstone":1,"vendorThing":1},"createdAt":"2026-06-30T20:23:59Z","embeddingDim":8,"embeddingModel":"test-embed","embeddingsIncluded":false,"exportMode":"full","files":[{"bytes":295,"path":"audit/tombstones.jsonl","sha256":"1c7a4081b2f8601c37633442837f62acc9d7afbc39de68f5024f77d092a40b8d"},{"bytes":215,"path":"items/edge.jsonl","sha256":"a46150e36da3bed28dead6afc6c14d39c6737758389c5ceb4a2638825bb77869"},{"bytes":150,"path":"items/entity.jsonl","sha256":"7473a09c9fec9ec42f7a1497314b7aa1477d16a827332d7f257605b2490cd44b"},{"bytes":919,"path":"items/episode.jsonl","sha256":"67ef60b8686b8d5cfdde69700fc54ddb513caa97480c81228dcac11a6a737de5"},{"bytes":30,"path":"items/vendorThing.jsonl","sha256":"83654ab56d668010b6d8957ec8f3888c6df14d1ff031b62f20908af1e44e1243"}],"format":"1.0.0","generator":"test/1.0","schemaVersion":1}

portable_memory-0.1.2/Conformance/vectors/README.md

@@ -0,0 +1,65 @@
+# Conformance vectors
+
+Language-neutral test data that pins the parts of the format most likely to drift
+between implementations: **Canonical JSON** serialization (spec §1.1) and **signature**
+verification (§1.3). If your implementation reproduces these, it is byte-interoperable
+with the reference SDKs.
+
+These files are **byte-identical** in the Swift and Python repositories.
+
+## `canonical-json.json`
+
+An array of `vectors`, each with:
+
+| field | meaning |
+|---|---|
+| `name` | what the case pins |
+| `input` | a JSON value |
+| `canonical` | the exact Canonical JSON serialization of `input` (spec §1.1) |
+| `sha256` | `sha256( utf8(canonical) )`, lowercase hex |
+
+**Conformance:** for every vector, `canonicalize(input)` MUST equal `canonical`
+byte-for-byte, and its SHA-256 MUST equal `sha256`. A ~10-line test in any language does
+this; see `tests/` in either SDK for the reference loaders.
+
+The cases cover whole-valued floats (`1.0` → `1`), shortest-round-trip fractions,
+negative zero, exact integers through `UInt64.max` (**integer fields beyond 2^53 require
+a bigint-aware JSON parser** — `JSON.parse` in JS silently rounds them), raw non-ASCII,
+short vs `\uXXXX` escapes, `/` unescaped, recursive key sorting, and array-order
+preservation.
+
+## `signed.mem` + `signing-test-key.json`
+
+A complete, signed bundle plus the **test keypair** used to sign it (a fixed 32-byte seed
+`00 01 … 1f` — obviously not a real secret). Use it to prove signature interop:
+
+- **Verify:** load `publicKeyHex`, verify `manifest.sig` against `manifest.json` → MUST
+  pass; flip one byte of `manifest.json` → MUST fail.
+- **Sign + verify:** load `privateKeyHex`, sign the manifest bytes, verify your own
+  signature with the public key → MUST pass.
+
+> **Signatures are verify-interoperable, not byte-reproducible.** Ed25519 signature bytes
+> may differ between implementations (swift-crypto randomizes the nonce; Python's
+> `cryptography` is deterministic) — both are valid. So `manifest.sig` is **excluded** from
+> the byte-identity guarantee of §1.1; the data files, `manifest.json`, and `CHECKSUMS`
+> are covered, the signature is not.
+
+## Known cross-implementation residuals (out of scope for v1)
+
+The reference SDKs are **not** guaranteed byte-identical for these, so no vector asserts
+them. Keep them ASCII / in-range where cross-impl byte-identity matters:
+
+- **Object keys outside the BMP** (e.g. emoji as a JSON *key*): key ordering differs
+  (UTF-16 code-unit vs code-point). Native record keys are all ASCII; only exotic foreign
+  `ext` keys are affected.
+- **Integral numeric magnitudes ≥ 1e16** and **integers beyond `UInt64.max`**: exponent
+  form and precision handling diverge. Real memory values (scores, counts) never reach
+  this range.
+- **Record/line ordering for non-ASCII ids**: within-file ordering differs for non-ASCII
+  identifiers; use ASCII, kind-prefixed ids.
+
+## Regenerating
+
+`generate.py` (Python repo) rebuilds every file deterministically from the reference
+encoder and the fixed test seed. Re-run it after any change to the canonicalization rules,
+then confirm both SDK test suites stay green.