memoryking 0.1.0a1__tar.gz

memoryking-0.1.0a1/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor 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
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You 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 the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

memoryking-0.1.0a1/NOTICE

@@ -0,0 +1,12 @@
+MemoryKing
+Copyright 2026 James King
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+this software except in compliance with the License. A copy of the License is in
+the file LICENSE and at http://www.apache.org/licenses/LICENSE-2.0.
+
+This distribution includes the cl100k_base tokenizer vocabulary from the tiktoken
+project, Copyright (c) 2022 OpenAI, Shantanu Jain, under the MIT License; its notice
+is kept at src/memoryking/adapters/tokenizers/LICENSE. The optional local embedding
+model is not included; its manifest records the model's own Apache-2.0 licence and
+it is downloaded only on request.

memoryking-0.1.0a1/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.4
+Name: memoryking
+Version: 0.1.0a1
+Summary: MemoryKing local memory, checkpoint and recovery service
+Author: James King
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/jamesking-us/memoryking
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: <3.13,>=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: jsonschema==4.26.0
+Provides-Extra: tokenizers
+Requires-Dist: tiktoken==0.12.0; extra == "tokenizers"
+Provides-Extra: embeddings
+Requires-Dist: onnxruntime==1.23.2; extra == "embeddings"
+Requires-Dist: numpy==2.5.4; extra == "embeddings"
+Requires-Dist: tokenizers==0.23.3; extra == "embeddings"
+Provides-Extra: shared
+Requires-Dist: psycopg[binary]==3.3.6; extra == "shared"
+Requires-Dist: psycopg-pool==3.3.3; extra == "shared"
+Requires-Dist: mcp==2.3.0; extra == "shared"
+Dynamic: license-file
+
+<p align="center"><img src="src/memoryking/adapters/web/elephant.png" width="180" alt="MemoryKing" /></p>
+
+# Give your AI agents a memory they can pick up again
+
+MemoryKing keeps the useful context behind an agent's work: what it learned, what it tried, what must not be forgotten, and what should happen next.
+
+Think of it as a **shared project notebook with a save point**. When a conversation ends, an agent restarts, or another agent takes over, the work can continue from a recorded state instead of starting with a blank page.
+
+It is a service that you connect to your agents. It does not automatically read your chats or run agents for you.
+
+## Why it is useful
+
+Imagine an agent investigating a checkout bug. It discovers that a retry can charge a customer twice, tries a fix that fails, and runs out of context before finishing.
+
+With MemoryKing, it can leave the next agent:
+
+- **The goal:** fix the retry without creating duplicate charges.
+- **The evidence:** the relevant error and test output, with their sources.
+- **The failed approach:** what was tried and why not to repeat it.
+- **The unfinished work:** the patch state, missing tests and next action.
+- **The boundaries:** use the sandbox and keep production changes subject to approval.
+
+The next agent receives a focused briefing and the saved task state. A reviewer can see the evidence and what is still unverified. This is an illustrative workflow; your integration supplies the observations and checks.
+
+```mermaid
+flowchart LR
+    A[Agent does work] --> B[Save findings and task state]
+    B --> C[MemoryKing checks access and relevance]
+    C --> D[Next session gets a focused briefing]
+    D --> E[Agent continues or hands off]
+    E --> B
+```
+
+## What it does for agents
+
+| Need | What MemoryKing provides |
+| --- | --- |
+| Remember useful findings | Searchable observations with source attribution; reviewed knowledge stays distinct from unverified notes. |
+| Resume unfinished work | Checkpoints containing the objective, constraints, failed attempts, verification gaps and next actions, opened by a three-sentence "where this left off" summary. |
+| Work together | Handoffs bound to the recipient's current permissions. |
+| Keep context manageable | Focused briefings with explicit output budgets and links back to evidence. |
+| Avoid stale advice | Repository identity, applicability rules and freshness checks for guidance tied to code. |
+| Recover safely | Records of uncertain operations and history-aware backup/restore, so a restart does not silently authorize repeating an action. |
+| Understand what happened | A dashboard with capacity, task progress, a per-project timeline, a memory graph, on-demand briefings with their receipts, and retrieval history. |
+| Fit any agent host | A lean five-tool MCP profile with defaults for Claude Code, Codex, Grok or any stdio host; cited Markdown briefings; capture from the CLI, pytest or git hooks. |
+| Know what to do when something is refused | Every error reply carries a one-line hint, and a [generated page](docs/error-codes.md) lists them all. |
+
+The core runs locally **without a model account, GPU or paid API**. A shared PostgreSQL profile supports multiple agents and tenants. Optional local embeddings add semantic search. If you do want MemoryKing itself to talk to a model (Anthropic, OpenAI, xAI, Google Vertex AI, or one running on your own machine), you write a short policy saying which, and every request it sends is checked against that policy and recorded.
+
+## See it work
+
+You need Python **3.12** and Git. Repository access is currently private. From a terminal:
+
+```sh
+git clone https://github.com/jamesking-us/memoryking.git
+cd memoryking
+python3.12 -m venv .venv
+.venv/bin/python -I -m pip install --require-hashes -r requirements-build.lock -r requirements-core.lock
+.venv/bin/python -I -m pip install --no-build-isolation --no-deps .
+.venv/bin/python examples/remember_and_resume.py
+```
+
+The example creates a temporary store, saves a finding and an unfinished task, closes the first connection, and resumes through a new client. It prints a readable walkthrough, makes no model requests, and removes its temporary data when finished.
+
+For a lasting installation and the browser dashboard, follow the [getting started guide](docs/getting-started.md): name your store once with `memoryking profile add`, then `status`, `doctor`, `dashboard open` and `credential issue` need no paths. If you are evaluating the idea rather than installing software, start with the [agent workflows](docs/agent-guide.md).
+
+## See what your agents are doing
+
+![MemoryKing dashboard overview showing capacity for each bounded resource, a project card with record counts and latest activity, and a synthetic task opened by its three-sentence "where this left off" summary](docs/images/dashboard.jpg)
+
+*Dashboard overview with synthetic example data: capacity first, then the projects you can read, then the project's task activity with its summary. Progress reflects saved agent reports and evidence.*
+
+The dashboard helps you inspect recorded work without reading a long chat transcript. Projects you can read are listed with their record counts; pick one and every view follows it.
+
+- **Overview:** capacity use for each bounded resource, with a warning from 80 percent.
+- **Task activity:** saved goals, completed and pending criteria, blockers and observed heartbeats.
+- **Memory:** ask for the briefing an agent would receive and verify its replay, browse the project timeline, review proposed knowledge, preview a purge, and explore an interactive graph of memories and evidence, coloured by how far each record has been reviewed, with a tap through to the briefings that used it.
+- **History and review:** inspect changes, review proposals and preview affected content.
+- **Retrieval history:** see the exact briefing returned, its sources and recorded usage.
+- **Team:** who did what in a project, the permissions that allow it, a revoke button, and an audit export; the overview lists your projects as cards you can open and link to.
+- **Appearance:** textured dark and light themes, a crowned cybernetic elephant, an optional depth-tilt animation that respects reduced motion, and a phone layout for checking on agents away from the desk.
+
+Agents must publish their state through the supported interfaces. A displayed heartbeat is an observation, not proof that an agent is still working; missing cost data stays unknown.
+
+## Choose your setup
+
+| Setup | Suitable for | What runs |
+| --- | --- | --- |
+| Local | One person or agents on one computer | Python service, SQLite, private local files; optional browser dashboard. |
+| Shared | Multiple agents using a central service | PostgreSQL, authenticated HTTP/MCP, separate database roles and recovery storage. |
+| Docker evaluation | Trying the shared profile on one machine | A source-built Compose stack with loopback HTTPS. |
+
+See [deployment and configuration](docs/deployment.md) for commands, prerequisites, backup and recovery.
+
+## Read the documentation
+
+| Guide | What you will learn |
+| --- | --- |
+| [Getting started](docs/getting-started.md) | Install, run the demo, create a store and open the dashboard. |
+| [Using MemoryKing with agents](docs/agent-guide.md) | Capture → brief → checkpoint → resume → handoff; Python, lean and full MCP profiles for any host, and automatic capture from hooks. |
+| [Deployment and configuration](docs/deployment.md) | Local/shared/Docker setups, credentials, configuration, upgrades and recovery. |
+| [How it is designed](docs/design.md) | Storage, knowledge review, retrieval, permissions and recovery guarantees. |
+| [Feature and API reference](docs/reference.md) | Interfaces, optional capabilities, limits and capacity, metrics, migration and troubleshooting. |
+| [Error codes](docs/error-codes.md) | Every error code with the next move, generated from the service's own table. |
+| [Contributing](CONTRIBUTING.md) | Build, test and maintain the project locally. |
+
+## Current status
+
+**Early preview for local evaluation; not yet production-qualified.** Core behavior has automated coverage, but measured workload targets have not been met. Improved real-task success or reduced token cost has not yet been demonstrated. Windows, complete browser/device coverage, automatic failover and production recovery targets are not qualified. Third-party agent hosts need integration testing.
+
+MemoryKing helps preserve and inspect context; it does not make an agent's conclusions automatically correct. Use reviewed evidence and appropriate human approval for consequential work. See the [security model](SECURITY.md) and [current limits](docs/reference.md#current-limits).
+
+MemoryKing is released under the [Apache License 2.0](LICENSE). A packaged release (a Python wheel and a container image, each with recorded checksums) is built from this repository; the first public upload is in preparation. See [distribution](CONTRIBUTING.md#distribution).

memoryking-0.1.0a1/README.md

@@ -0,0 +1,113 @@
+<p align="center"><img src="src/memoryking/adapters/web/elephant.png" width="180" alt="MemoryKing" /></p>
+
+# Give your AI agents a memory they can pick up again
+
+MemoryKing keeps the useful context behind an agent's work: what it learned, what it tried, what must not be forgotten, and what should happen next.
+
+Think of it as a **shared project notebook with a save point**. When a conversation ends, an agent restarts, or another agent takes over, the work can continue from a recorded state instead of starting with a blank page.
+
+It is a service that you connect to your agents. It does not automatically read your chats or run agents for you.
+
+## Why it is useful
+
+Imagine an agent investigating a checkout bug. It discovers that a retry can charge a customer twice, tries a fix that fails, and runs out of context before finishing.
+
+With MemoryKing, it can leave the next agent:
+
+- **The goal:** fix the retry without creating duplicate charges.
+- **The evidence:** the relevant error and test output, with their sources.
+- **The failed approach:** what was tried and why not to repeat it.
+- **The unfinished work:** the patch state, missing tests and next action.
+- **The boundaries:** use the sandbox and keep production changes subject to approval.
+
+The next agent receives a focused briefing and the saved task state. A reviewer can see the evidence and what is still unverified. This is an illustrative workflow; your integration supplies the observations and checks.
+
+```mermaid
+flowchart LR
+    A[Agent does work] --> B[Save findings and task state]
+    B --> C[MemoryKing checks access and relevance]
+    C --> D[Next session gets a focused briefing]
+    D --> E[Agent continues or hands off]
+    E --> B
+```
+
+## What it does for agents
+
+| Need | What MemoryKing provides |
+| --- | --- |
+| Remember useful findings | Searchable observations with source attribution; reviewed knowledge stays distinct from unverified notes. |
+| Resume unfinished work | Checkpoints containing the objective, constraints, failed attempts, verification gaps and next actions, opened by a three-sentence "where this left off" summary. |
+| Work together | Handoffs bound to the recipient's current permissions. |
+| Keep context manageable | Focused briefings with explicit output budgets and links back to evidence. |
+| Avoid stale advice | Repository identity, applicability rules and freshness checks for guidance tied to code. |
+| Recover safely | Records of uncertain operations and history-aware backup/restore, so a restart does not silently authorize repeating an action. |
+| Understand what happened | A dashboard with capacity, task progress, a per-project timeline, a memory graph, on-demand briefings with their receipts, and retrieval history. |
+| Fit any agent host | A lean five-tool MCP profile with defaults for Claude Code, Codex, Grok or any stdio host; cited Markdown briefings; capture from the CLI, pytest or git hooks. |
+| Know what to do when something is refused | Every error reply carries a one-line hint, and a [generated page](docs/error-codes.md) lists them all. |
+
+The core runs locally **without a model account, GPU or paid API**. A shared PostgreSQL profile supports multiple agents and tenants. Optional local embeddings add semantic search. If you do want MemoryKing itself to talk to a model (Anthropic, OpenAI, xAI, Google Vertex AI, or one running on your own machine), you write a short policy saying which, and every request it sends is checked against that policy and recorded.
+
+## See it work
+
+You need Python **3.12** and Git. Repository access is currently private. From a terminal:
+
+```sh
+git clone https://github.com/jamesking-us/memoryking.git
+cd memoryking
+python3.12 -m venv .venv
+.venv/bin/python -I -m pip install --require-hashes -r requirements-build.lock -r requirements-core.lock
+.venv/bin/python -I -m pip install --no-build-isolation --no-deps .
+.venv/bin/python examples/remember_and_resume.py
+```
+
+The example creates a temporary store, saves a finding and an unfinished task, closes the first connection, and resumes through a new client. It prints a readable walkthrough, makes no model requests, and removes its temporary data when finished.
+
+For a lasting installation and the browser dashboard, follow the [getting started guide](docs/getting-started.md): name your store once with `memoryking profile add`, then `status`, `doctor`, `dashboard open` and `credential issue` need no paths. If you are evaluating the idea rather than installing software, start with the [agent workflows](docs/agent-guide.md).
+
+## See what your agents are doing
+
+![MemoryKing dashboard overview showing capacity for each bounded resource, a project card with record counts and latest activity, and a synthetic task opened by its three-sentence "where this left off" summary](docs/images/dashboard.jpg)
+
+*Dashboard overview with synthetic example data: capacity first, then the projects you can read, then the project's task activity with its summary. Progress reflects saved agent reports and evidence.*
+
+The dashboard helps you inspect recorded work without reading a long chat transcript. Projects you can read are listed with their record counts; pick one and every view follows it.
+
+- **Overview:** capacity use for each bounded resource, with a warning from 80 percent.
+- **Task activity:** saved goals, completed and pending criteria, blockers and observed heartbeats.
+- **Memory:** ask for the briefing an agent would receive and verify its replay, browse the project timeline, review proposed knowledge, preview a purge, and explore an interactive graph of memories and evidence, coloured by how far each record has been reviewed, with a tap through to the briefings that used it.
+- **History and review:** inspect changes, review proposals and preview affected content.
+- **Retrieval history:** see the exact briefing returned, its sources and recorded usage.
+- **Team:** who did what in a project, the permissions that allow it, a revoke button, and an audit export; the overview lists your projects as cards you can open and link to.
+- **Appearance:** textured dark and light themes, a crowned cybernetic elephant, an optional depth-tilt animation that respects reduced motion, and a phone layout for checking on agents away from the desk.
+
+Agents must publish their state through the supported interfaces. A displayed heartbeat is an observation, not proof that an agent is still working; missing cost data stays unknown.
+
+## Choose your setup
+
+| Setup | Suitable for | What runs |
+| --- | --- | --- |
+| Local | One person or agents on one computer | Python service, SQLite, private local files; optional browser dashboard. |
+| Shared | Multiple agents using a central service | PostgreSQL, authenticated HTTP/MCP, separate database roles and recovery storage. |
+| Docker evaluation | Trying the shared profile on one machine | A source-built Compose stack with loopback HTTPS. |
+
+See [deployment and configuration](docs/deployment.md) for commands, prerequisites, backup and recovery.
+
+## Read the documentation
+
+| Guide | What you will learn |
+| --- | --- |
+| [Getting started](docs/getting-started.md) | Install, run the demo, create a store and open the dashboard. |
+| [Using MemoryKing with agents](docs/agent-guide.md) | Capture → brief → checkpoint → resume → handoff; Python, lean and full MCP profiles for any host, and automatic capture from hooks. |
+| [Deployment and configuration](docs/deployment.md) | Local/shared/Docker setups, credentials, configuration, upgrades and recovery. |
+| [How it is designed](docs/design.md) | Storage, knowledge review, retrieval, permissions and recovery guarantees. |
+| [Feature and API reference](docs/reference.md) | Interfaces, optional capabilities, limits and capacity, metrics, migration and troubleshooting. |
+| [Error codes](docs/error-codes.md) | Every error code with the next move, generated from the service's own table. |
+| [Contributing](CONTRIBUTING.md) | Build, test and maintain the project locally. |
+
+## Current status
+
+**Early preview for local evaluation; not yet production-qualified.** Core behavior has automated coverage, but measured workload targets have not been met. Improved real-task success or reduced token cost has not yet been demonstrated. Windows, complete browser/device coverage, automatic failover and production recovery targets are not qualified. Third-party agent hosts need integration testing.
+
+MemoryKing helps preserve and inspect context; it does not make an agent's conclusions automatically correct. Use reviewed evidence and appropriate human approval for consequential work. See the [security model](SECURITY.md) and [current limits](docs/reference.md#current-limits).
+
+MemoryKing is released under the [Apache License 2.0](LICENSE). A packaged release (a Python wheel and a container image, each with recorded checksums) is built from this repository; the first public upload is in preparation. See [distribution](CONTRIBUTING.md#distribution).

memoryking-0.1.0a1/pyproject.toml

@@ -0,0 +1,67 @@
+[build-system]
+requires = ["setuptools==84.2.1", "wheel==0.48.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "memoryking"
+version = "0.1.0a1"
+description = "MemoryKing local memory, checkpoint and recovery service"
+readme = "README.md"
+requires-python = ">=3.12,<3.13"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "James King" }]
+dependencies = ["jsonschema==4.26.0"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Intended Audience :: Developers",
+  "Operating System :: MacOS",
+  "Operating System :: POSIX :: Linux",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.12",
+  "Topic :: Software Development :: Libraries",
+]
+
+[project.urls]
+Repository = "https://github.com/jamesking-us/memoryking"
+
+[project.scripts]
+memoryking = "memoryking.__main__:main"
+memoryking-migrate = "memoryking.migration:main"
+memoryking-shared = "memoryking.shared:main"
+memoryking-reference-agent = "memoryking.reference_agent:main"
+memoryking-repository-worker = "memoryking.repository_worker:main"
+memoryking-embedding-worker = "memoryking.embedding_worker:main"
+
+[project.optional-dependencies]
+tokenizers = ["tiktoken==0.12.0"]
+embeddings = ["onnxruntime==1.23.2", "numpy==2.5.4", "tokenizers==0.23.3"]
+shared = ["psycopg[binary]==3.3.6", "psycopg-pool==3.3.3", "mcp==2.3.0"]
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+"memoryking" = ["py.typed"]
+"memoryking.contracts" = ["*.json", "py.typed"]
+"memoryking.adapters" = ["*.sql", "*.json", "web/*", "tokenizers/*", "models/*.json"]
+
+[tool.ruff]
+target-version = "py312"
+line-length = 100
+extend-exclude = ["tmp", "docs/reports", "output"]
+
+[tool.ruff.lint]
+select = ["E4", "E7", "E9", "F", "I", "B"]
+
+[tool.ruff.format]
+exclude = ["src/memoryking/contracts/generated.py", "src/memoryking/contracts/retrieval_generated.py", "src/memoryking/contracts/working_generated.py", "src/memoryking/contracts/handoff_generated.py", "src/memoryking/contracts/inference_generated.py", "src/memoryking/contracts/repository_generated.py", "src/memoryking/contracts/embedding_generated.py", "src/memoryking/contracts/processing_generated.py", "src/memoryking/contracts/experience_generated.py"]
+
+[tool.mypy]
+python_version = "3.12"
+strict = true
+files = ["src/memoryking"]
+
+[[tool.mypy.overrides]]
+module = ["jsonschema", "jsonschema.*"]
+ignore_missing_imports = true

memoryking-0.1.0a1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

memoryking-0.1.0a1/src/memoryking/__init__.py

@@ -0,0 +1,3 @@
+"""MemoryKing local evidence, checkpoint and recovery service with a bound client SDK."""
+
+__version__ = "0.1.0a1"