mitos-adr 0.17.1__tar.gz

mitos_adr-0.17.1/LICENSE

@@ -0,0 +1,201 @@
+                                 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.

mitos_adr-0.17.1/MANIFEST.in

@@ -0,0 +1,5 @@
+include mitos/format-spec.md
+include README.md
+include SETUP.md
+include LICENSE
+include docker-compose.yml

mitos_adr-0.17.1/PKG-INFO

@@ -0,0 +1,132 @@
+Metadata-Version: 2.4
+Name: mitos-adr
+Version: 0.17.1
+Summary: Architectural decision memory for LLM-native workflows — markdown for humans, a graph for agents.
+Author-email: Vinga Luksaite <vinga@skyforge.sh>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/dovahkiin-v/mitos
+Project-URL: Repository, https://github.com/dovahkiin-v/mitos
+Project-URL: Documentation, https://github.com/dovahkiin-v/mitos#readme
+Project-URL: Issues, https://github.com/dovahkiin-v/mitos/issues
+Keywords: adr,architectural-decisions,decision-records,llm,ai-agents,mcp,knowledge-graph,qdrant
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Documentation
+Classifier: Operating System :: POSIX
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: filelock>=3.0.0
+Requires-Dist: google-genai>=1.66.0
+Requires-Dist: anthropic<1,>=0.84.0
+Requires-Dist: mcp<2,>=1.26.0
+Requires-Dist: requests>=2.0.0
+Provides-Extra: test
+Requires-Dist: pytest>=8.0; extra == "test"
+Requires-Dist: pytest-asyncio>=1.0; extra == "test"
+Requires-Dist: pytest-xdist>=3.8; extra == "test"
+Dynamic: license-file
+
+# Mitos
+
+![Status: Alpha](https://img.shields.io/badge/status-alpha-orange) ![Python 3.13+](https://img.shields.io/badge/python-3.13+-blue) ![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue)
+
+> 🔧 **Early release** — actively developed
+
+When you build software with AI assistants over months, the *reasoning* behind your decisions gets lost. The assistant forgets why you chose one approach, re-suggests options you already rejected, and your design notes drift out of sync with what was actually decided. Mitos is a memory layer for those decisions: it records each decision, the alternatives you ruled out, and how later decisions replace earlier ones — then feeds that history back to your AI assistant in a compact, trustworthy form.
+
+The result: your AI collaborator stays consistent with the calls you've actually made — it stops contradicting a past decision or re-opening a settled question, and your decision record never silently rots.
+
+Under the hood: markdown for humans (`decisions.md` is the source of truth you can always read and grep), a typed graph for the agents (SQLite + a local Qdrant for semantic recall), and an MCP server so agents check precedent before deciding and record decisions as they make them.
+
+---
+
+## Fastest install: hand it to your agent
+
+If you work with an AI coding agent (Claude Code, Cursor, Gemini CLI, …), the easiest path is to let it do the setup. In the project you want mitos in, give your agent:
+
+```text
+Read https://github.com/dovahkiin-v/mitos/blob/main/SETUP.md and set up mitos
+for this project. When done, run `mitos status .` from the project directory
+and report the result.
+```
+
+What your agent will end up doing — the same steps a human follows, all in [SETUP.md](SETUP.md) where you can read them first:
+
+- install the `mitos` CLI via pipx, from this repository;
+- start a local Qdrant container (`qdrant/qdrant` on port `7333`, isolated from any Qdrant you already run);
+- register the MCP server once for the whole machine, if it isn't registered already;
+- initialize the project workspace, which also registers the project by name;
+- ask you to set your API keys yourself (`mitos set-key`) — a Gemini key (required), and an Anthropic key for the conflict-audit layer (strongly recommended); the setup guide tells agents not to handle key values.
+
+How much your agent asks along the way is governed by your own agent's settings, not by this prompt.
+
+## Manual setup
+
+The same steps by hand — full detail in **[SETUP.md](SETUP.md)**:
+
+1. **Install** (once per machine): `pipx install git+https://github.com/dovahkiin-v/mitos`
+2. **Start Qdrant** (once per machine, shared by all projects): `docker compose up -d` from this repo — mitos runs its own instance on `:7333`, so it never touches a Qdrant you use for other work.
+3. **Register the MCP server** (once per machine, recommended for agents): `claude mcp add --scope user mitos -- mitos serve`. One registration serves every project — see [SETUP.md](SETUP.md) for what it costs, for other harnesses, and for why a leftover per-project `.mcp.json` entry has to go.
+4. **Per project**: `mitos init` from the project root, then `mitos set-key --global <your-Gemini-key>` (one key covers everything; get it at <https://aistudio.google.com/app/apikey>). Gemini is the tested embedding provider today; a multi-provider abstraction is on the roadmap.
+5. **Verify**: `mitos status .` → `READY ✓`.
+
+`mitos status .` is the compass throughout: it says exactly what's done, what's missing, and what to do next for that project. With no project named, `mitos status` answers the other question — what does this machine have — listing every registered project and checking Qdrant.
+
+**Every command names its project.** There is no default target: `mitos init` registers the project by name, and from then on each verb takes `-p <name>`, `-p <absolute path>`, or `-p .` from the project root (agents pass the same thing as a `project` argument). `mitos projects` lists what's registered. That is what lets one install and one MCP server serve every project on the machine without a call ever landing in the wrong corpus.
+
+## How it runs
+
+Mitos is **per-project** — each project gets its own decision graph and its own Qdrant collection. Day to day, three verbs carry the loop (as MCP tools for agents, with identical CLI twins):
+
+| Verb | When |
+|---|---|
+| `surface_decisions` (`mitos surface`) | *Before* deciding — is there precedent? Every hit carries the alternatives that were already rejected and why. |
+| `record_decision` (`mitos record`) | The moment something is settled — the decision, the rejected paths, and how it relates to prior decisions (supersedes, amends, …). |
+| `query_decisions` (`mitos query`) | Looking something up — by meaning or by exact handle. |
+
+A few properties worth knowing:
+
+- **The markdown is the source of truth.** Every decision lands in `decisions.md`, human-readable and greppable; the graph and the search index are derived from it and can always be rebuilt (`mitos rebuild`).
+- **Decisions are never edited or deleted — they're superseded.** State (active / superseded / amended) is computed from typed relations between decisions, so the history of *why* always survives.
+- **It fails safe.** If the search index or the embedding API is down, recording still works and search degrades to an honest text-match over the markdown — nothing blocks, nothing is lost, and degraded output says it's degraded.
+- **It audits itself.** The corpus sweep (`mitos check -p .`) finds decisions that silently contradict each other, and `--staged` gates new entries as a pre-commit or CI step — see [SETUP.md](SETUP.md) for the hook, CI and cron recipes, which name their project three different ways.
+
+Explore the rest with `mitos --help` — the help text doubles as the API reference.
+
+## Why it exists
+
+Building software through intensive LLM design reviews produces architectural decisions faster than a person can track. One month of that working style produced close to 900 decision records in a single markdown file — no longer greppable, readable, or manageable by hand. Existing ADR tools are built for human teams logging the occasional decision; mitos is built for a solo developer whose AI assistants generate and consume decisions continuously.
+
+If that's your way of working, project size doesn't matter much — the higher the decision volume, the faster mitos moves from comfort to necessity.
+
+## Development
+
+```bash
+pip install -e '.[test]'
+MITOS_NO_LIVE_TESTS=1 pytest -m "not packaging" -n auto   # offline suite, parallel (~50s)
+pytest -m "not packaging"                                 # adds the live tier — serial only
+pytest -m packaging                                       # real-install check: fresh venv + pip install
+```
+
+`-n auto` is safe for the offline suite and **not** for the live tier: the test-collection
+sweep is session-scoped, so parallel workers delete each other's Qdrant collections and
+the affected tests degrade to skips rather than failures.
+
+The `*_live.py` suites and golden Layer B make **real Gemini and Anthropic API calls**
+against your own keys, and need Qdrant on `:7333`. They skip when no key is resolvable,
+so a fresh clone runs the fast path by default.
+
+Keys resolve from the environment, a repo-root `.env`, or `~/.config/mitos/.env` — so if
+you already *use* mitos, a test run can pick up your personal key and spend against it.
+Opt out explicitly:
+
+```bash
+MITOS_NO_LIVE_TESTS=1 PYTHONPATH=. pytest -m "not packaging"
+```
+
+The canonical decision format lives in [`mitos/format-spec.md`](mitos/format-spec.md). License: [Apache 2.0](LICENSE).

mitos_adr-0.17.1/README.md

@@ -0,0 +1,99 @@
+# Mitos
+
+![Status: Alpha](https://img.shields.io/badge/status-alpha-orange) ![Python 3.13+](https://img.shields.io/badge/python-3.13+-blue) ![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue)
+
+> 🔧 **Early release** — actively developed
+
+When you build software with AI assistants over months, the *reasoning* behind your decisions gets lost. The assistant forgets why you chose one approach, re-suggests options you already rejected, and your design notes drift out of sync with what was actually decided. Mitos is a memory layer for those decisions: it records each decision, the alternatives you ruled out, and how later decisions replace earlier ones — then feeds that history back to your AI assistant in a compact, trustworthy form.
+
+The result: your AI collaborator stays consistent with the calls you've actually made — it stops contradicting a past decision or re-opening a settled question, and your decision record never silently rots.
+
+Under the hood: markdown for humans (`decisions.md` is the source of truth you can always read and grep), a typed graph for the agents (SQLite + a local Qdrant for semantic recall), and an MCP server so agents check precedent before deciding and record decisions as they make them.
+
+---
+
+## Fastest install: hand it to your agent
+
+If you work with an AI coding agent (Claude Code, Cursor, Gemini CLI, …), the easiest path is to let it do the setup. In the project you want mitos in, give your agent:
+
+```text
+Read https://github.com/dovahkiin-v/mitos/blob/main/SETUP.md and set up mitos
+for this project. When done, run `mitos status .` from the project directory
+and report the result.
+```
+
+What your agent will end up doing — the same steps a human follows, all in [SETUP.md](SETUP.md) where you can read them first:
+
+- install the `mitos` CLI via pipx, from this repository;
+- start a local Qdrant container (`qdrant/qdrant` on port `7333`, isolated from any Qdrant you already run);
+- register the MCP server once for the whole machine, if it isn't registered already;
+- initialize the project workspace, which also registers the project by name;
+- ask you to set your API keys yourself (`mitos set-key`) — a Gemini key (required), and an Anthropic key for the conflict-audit layer (strongly recommended); the setup guide tells agents not to handle key values.
+
+How much your agent asks along the way is governed by your own agent's settings, not by this prompt.
+
+## Manual setup
+
+The same steps by hand — full detail in **[SETUP.md](SETUP.md)**:
+
+1. **Install** (once per machine): `pipx install git+https://github.com/dovahkiin-v/mitos`
+2. **Start Qdrant** (once per machine, shared by all projects): `docker compose up -d` from this repo — mitos runs its own instance on `:7333`, so it never touches a Qdrant you use for other work.
+3. **Register the MCP server** (once per machine, recommended for agents): `claude mcp add --scope user mitos -- mitos serve`. One registration serves every project — see [SETUP.md](SETUP.md) for what it costs, for other harnesses, and for why a leftover per-project `.mcp.json` entry has to go.
+4. **Per project**: `mitos init` from the project root, then `mitos set-key --global <your-Gemini-key>` (one key covers everything; get it at <https://aistudio.google.com/app/apikey>). Gemini is the tested embedding provider today; a multi-provider abstraction is on the roadmap.
+5. **Verify**: `mitos status .` → `READY ✓`.
+
+`mitos status .` is the compass throughout: it says exactly what's done, what's missing, and what to do next for that project. With no project named, `mitos status` answers the other question — what does this machine have — listing every registered project and checking Qdrant.
+
+**Every command names its project.** There is no default target: `mitos init` registers the project by name, and from then on each verb takes `-p <name>`, `-p <absolute path>`, or `-p .` from the project root (agents pass the same thing as a `project` argument). `mitos projects` lists what's registered. That is what lets one install and one MCP server serve every project on the machine without a call ever landing in the wrong corpus.
+
+## How it runs
+
+Mitos is **per-project** — each project gets its own decision graph and its own Qdrant collection. Day to day, three verbs carry the loop (as MCP tools for agents, with identical CLI twins):
+
+| Verb | When |
+|---|---|
+| `surface_decisions` (`mitos surface`) | *Before* deciding — is there precedent? Every hit carries the alternatives that were already rejected and why. |
+| `record_decision` (`mitos record`) | The moment something is settled — the decision, the rejected paths, and how it relates to prior decisions (supersedes, amends, …). |
+| `query_decisions` (`mitos query`) | Looking something up — by meaning or by exact handle. |
+
+A few properties worth knowing:
+
+- **The markdown is the source of truth.** Every decision lands in `decisions.md`, human-readable and greppable; the graph and the search index are derived from it and can always be rebuilt (`mitos rebuild`).
+- **Decisions are never edited or deleted — they're superseded.** State (active / superseded / amended) is computed from typed relations between decisions, so the history of *why* always survives.
+- **It fails safe.** If the search index or the embedding API is down, recording still works and search degrades to an honest text-match over the markdown — nothing blocks, nothing is lost, and degraded output says it's degraded.
+- **It audits itself.** The corpus sweep (`mitos check -p .`) finds decisions that silently contradict each other, and `--staged` gates new entries as a pre-commit or CI step — see [SETUP.md](SETUP.md) for the hook, CI and cron recipes, which name their project three different ways.
+
+Explore the rest with `mitos --help` — the help text doubles as the API reference.
+
+## Why it exists
+
+Building software through intensive LLM design reviews produces architectural decisions faster than a person can track. One month of that working style produced close to 900 decision records in a single markdown file — no longer greppable, readable, or manageable by hand. Existing ADR tools are built for human teams logging the occasional decision; mitos is built for a solo developer whose AI assistants generate and consume decisions continuously.
+
+If that's your way of working, project size doesn't matter much — the higher the decision volume, the faster mitos moves from comfort to necessity.
+
+## Development
+
+```bash
+pip install -e '.[test]'
+MITOS_NO_LIVE_TESTS=1 pytest -m "not packaging" -n auto   # offline suite, parallel (~50s)
+pytest -m "not packaging"                                 # adds the live tier — serial only
+pytest -m packaging                                       # real-install check: fresh venv + pip install
+```
+
+`-n auto` is safe for the offline suite and **not** for the live tier: the test-collection
+sweep is session-scoped, so parallel workers delete each other's Qdrant collections and
+the affected tests degrade to skips rather than failures.
+
+The `*_live.py` suites and golden Layer B make **real Gemini and Anthropic API calls**
+against your own keys, and need Qdrant on `:7333`. They skip when no key is resolvable,
+so a fresh clone runs the fast path by default.
+
+Keys resolve from the environment, a repo-root `.env`, or `~/.config/mitos/.env` — so if
+you already *use* mitos, a test run can pick up your personal key and spend against it.
+Opt out explicitly:
+
+```bash
+MITOS_NO_LIVE_TESTS=1 PYTHONPATH=. pytest -m "not packaging"
+```
+
+The canonical decision format lives in [`mitos/format-spec.md`](mitos/format-spec.md). License: [Apache 2.0](LICENSE).