aperture-mcp 0.1.0__tar.gz

aperture_mcp-0.1.0/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on
+[Keep a Changelog](https://keepachangelog.com/), and the package follows
+[Semantic Versioning](https://semver.org) (see [VERSIONING.md](./VERSIONING.md)).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-07-02
+
+Initial public preview.
+
+### Added
+- `aperture` Python library: `compare`, `compare_commitment`, `compare_proposal`, `compare_stance`,
+  over the frozen **v0.2** `DeltaResult` contract (8-value status, anchors, anchor violations).
+- `aperture-mcp` MCP server (stdio) exposing the compare tools + a `health` check.
+- `examples/git_decision_drift/`: a commitment tripwire over the version history of a decision
+  document, runnable against checked-in fixtures.
+- Honest, measured per-family limits (recall/precision) published alongside the tool rather than a
+  single aggregate score.
+
+### Known limits
+- Matches commitments as case-insensitive contiguous substrings: **misses** reworded / softened /
+  paraphrased / numerically-changed commitments; **declines/abstains** on **translated** ones (returns
+  `degraded`, false-positive rate 0); still **false-flags** **reformatted** ones (same script).
+  See the limits table in the [README](./README.md).

aperture_mcp-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,29 @@
+# Code of Conduct
+
+This project adopts the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.
+中文版本见官方翻译:<https://www.contributor-covenant.org/zh-cn/version/2/1/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.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment: empathy and kindness, respect for
+differing opinions, graceful acceptance of constructive feedback, and focusing on what is best for
+the community.
+
+Unacceptable behavior includes harassment, trolling, insulting 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
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project
+maintainer via the contact on the repository profile. All complaints will be reviewed and
+investigated promptly and fairly. The full text and enforcement guidelines are available at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct/>.

aperture_mcp-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,48 @@
+# Contributing to Aperture MCP
+
+**English** · [简体中文](./CONTRIBUTING.zh-CN.md)
+
+Thanks for looking. Aperture MCP is small on purpose, and its most valuable contributions are **honest
+reports of where it works and where it doesn’t** — not just code.
+
+## The single most useful thing you can do
+
+Point Aperture MCP at **your own** versioned decision docs (specs, plans, ADRs, charters) and tell us:
+
+- a real **drop it caught** that mattered, or
+- a real **drift it missed** (a reworded / softened / paraphrased commitment it stayed silent on), or
+- a **false alarm** (a reformat — same-script rearrangement — it flagged as dropped; or a
+  *natural-language*-anchored *translation* it flagged, which should instead decline/abstain). Note: a
+  **code-identifier** anchor (e.g. `ci-gates-green`) flagged across a translation is *correct*, not a
+  false alarm — it's translation-stable, so its exact token vanishing is a real drop.
+
+These reports are how the limits table in the README stays honest and how the gold corpus grows.
+Open an issue using the **“drift case report”** template.
+
+## Two feedback channels — and the honest boundary between them
+
+1. **Usage log (`APERTURE_USAGE_LOG`)** — *off by default*, fully local, and records **only
+   metadata** (timestamp, tool, status, counts). It **never** contains your decision text or your
+   commitment wording. It is a plain local file you can read or delete; nothing is sent anywhere.
+
+2. **Contributing a real case** — a **separate, explicit** choice, made through the **“drift case
+   report”** issue template (above). Be clear-eyed about what it involves: a useful benchmark case
+   needs the **actual before/after wording**, because the wording *is* the test — so sharing a case
+   **crosses** the metadata boundary and sends real text. Only include wording you’re comfortable
+   making public; we don’t pretend it can be anonymized. The curated benchmark accepts only cases
+   shared this way, under a license grant and an isolated review.
+
+We will never blur these two. Metadata logging stays metadata-only; contributing a case is an
+explicit choice to share text.
+
+## Code contributions
+
+- Keep the **compare contract** (`v0.2`, frozen) intact — see [VERSIONING.md](./VERSIONING.md).
+  Contract-touching changes are a deliberate, reviewed protocol event, not a PR drive-by.
+- Match the existing honesty discipline: if a change alters what the tool can or can’t see, update
+  the README limits table in the same PR.
+- Run the tests and linters before opening a PR.
+
+## Conduct
+
+By participating you agree to the [Code of Conduct](./CODE_OF_CONDUCT.md).

aperture_mcp-0.1.0/CONTRIBUTING.zh-CN.md

@@ -0,0 +1,44 @@
+# 参与贡献 Aperture MCP
+
+[English](./CONTRIBUTING.md) · **简体中文**
+
+谢谢你来看。Aperture MCP 刻意做得小,它最有价值的贡献是**关于"它在哪儿管用、在哪儿不管用"的诚实
+报告**——而不只是代码。
+
+## 你能做的最有用的一件事
+
+把 Aperture MCP 跑在**你自己**有版本史的决策文档(spec、计划、ADR、charter)上,然后告诉我们:
+
+- 一次真正**抓到的、且很要紧的删除**,或
+- 一次真正**漏掉的漂移**(一条被改写 / 软化 / 转述的承诺,它没吭声),或
+- 一次**误报**(一条只是被重排版——同语言内重排——的承诺,被它当成删除标了出来;或一条*自然语言*锚点的
+  *翻译*被它标出——那本应弃权(abstain))。注意:**代码标识符**锚点(如 `ci-gates-green`)跨翻译被标出是
+  *正确*行为、不算误报——它跨语言稳定,那个 token 消失就是真删。
+
+这些报告,正是 README 里那张"局限表"保持诚实、以及金标语料得以成长的方式。
+请用 **“drift case report”** issue 模板提交。
+
+## 两条反馈通道——以及它们之间那条诚实的界线
+
+1. **使用日志(`APERTURE_USAGE_LOG`)** —— *默认关闭*、完全本地,只记录**元数据**(时间戳、
+   工具、状态、计数)。它**绝不**包含你的决策文本或承诺措辞。它就是一个本地纯文件,你能读、能删;
+   什么都不会被发往任何地方。
+
+2. **贡献一个真实案例** —— 一个**单独、明确**的选择,通过 **“drift case report”** issue 模板
+   (见上)进行。请想清楚它意味着什么:一个有用的 benchmark 案例需要**真实的前后措辞**,因为措辞
+   *本身*就是测试——所以分享一个案例会**跨过**元数据界线、发送真实文本。只放你愿意公开的措辞;
+   我们不假装它能被匿名化。精选 benchmark 只接收以这种方式、在授权许可与隔离评审下提交的案例。
+
+我们绝不混淆这两者。元数据日志始终只是元数据;贡献一个案例,是一个明确的、要分享文本的选择。
+
+## 代码贡献
+
+- 保持 **compare 契约**(`v0.2`,已冻结)不变——见 [VERSIONING.md](./VERSIONING.md)。
+  触碰契约的改动是一次审慎、经评审的协议事件,不是顺手的 PR。
+- 与既有的诚实纪律对齐:若某个改动改变了"工具能看见 / 看不见什么",请在**同一个 PR**里更新
+  README 的局限表。
+- 提 PR 前先跑测试与 linter(`pytest`、`ruff check .`)。
+
+## 行为准则
+
+参与即表示你同意本项目的[行为准则](./CODE_OF_CONDUCT.md)。

aperture_mcp-0.1.0/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 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 Support. 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 support.
+
+   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 2026 The Aperture Authors
+
+   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.

aperture_mcp-0.1.0/MANIFEST.in

@@ -0,0 +1,4 @@
+include LICENSE README.md README.zh-CN.md CHANGELOG.md CONTRIBUTING.md CONTRIBUTING.zh-CN.md VERSIONING.md SECURITY.md CODE_OF_CONDUCT.md llms.txt server.json
+recursive-include conformance *.py *.json
+recursive-include examples *.py *.md
+recursive-include docs *.md

aperture_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,231 @@
+Metadata-Version: 2.4
+Name: aperture-mcp
+Version: 0.1.0
+Summary: A commitment tripwire for AI-edited decision docs: flags when a tracked commitment disappears, word-for-word, between two versions. MCP server + Python library. A signal, not a judge.
+Author: jaysinailabs
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/jaysinailabs/aperture-mcp
+Project-URL: Repository, https://github.com/jaysinailabs/aperture-mcp
+Project-URL: Changelog, https://github.com/jaysinailabs/aperture-mcp/blob/main/CHANGELOG.md
+Keywords: mcp,model-context-protocol,ai-agent,agents,decision-drift,commitment,self-consistency,adr,spec
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: mcp<2,>=1.27.2
+Dynamic: license-file
+
+<!-- mcp-name: io.github.jaysinailabs/aperture-mcp -->
+
+<div align="center">
+
+# Aperture MCP
+
+### Did an agent quietly drop a commitment from your spec — and no one noticed?
+
+[![PyPI](https://img.shields.io/badge/pypi-aperture--mcp-blue)](https://pypi.org/project/aperture-mcp/) [![MCP](https://img.shields.io/badge/MCP-server-purple)](https://modelcontextprotocol.io) [![License](https://img.shields.io/badge/license-Apache--2.0-green)](./LICENSE) [![status](https://img.shields.io/badge/status-early%2Fpre--1.0-orange)](./VERSIONING.md)
+
+**English** · [简体中文](./README.zh-CN.md)
+
+</div>
+
+AI agents now rewrite the documents that govern your work — specs, plans, ADRs, charters,
+`AGENTS.md` files. Somewhere in the edit, a constraint you set earlier can quietly disappear.
+
+**Aperture MCP is a *commitment tripwire*.** You name the commitments you care about; it flags —
+**word for word** — when one of them vanishes between two versions of a decision document.
+
+> **A signal, not a judge.** It trips; *you* investigate.
+> Opt-in · runs locally · never trains on your data.
+
+---
+
+## What it is (and what it is not)
+
+Aperture MCP is a small tool (and plain Python library) that
+compares **two text states of the same decision** — an earlier version and a later one — and
+surfaces a narrow, specific kind of **decision drift**: when a **tracked commitment’s exact text
+disappeared**.
+
+- ✅ **It does:** flag when a commitment you listed *verbatim* is present in version A and gone
+  from version B — across commits, sessions, or authors. It returns a structured, comparable
+  result with **its own blind spots written on the label**.
+- ❌ **It does *not*:** understand meaning. It matches text as a case-insensitive substring, so it
+  **misses** a commitment that was *reworded / softened / paraphrased* (it looks dropped-free even
+  though the promise weakened); it **declines/abstains** on a commitment that was merely *translated*
+  (it can’t compare verbatim across scripts, so it returns `degraded` rather than false-flag); and it
+  can still **false-flag** a commitment that was merely *reformatted* (the words moved, the meaning
+  didn’t). It does not rank options, score quality, or
+  tell you a change was *wrong*. **That judgment stays with you.**
+
+If you want one sentence: **Aperture MCP is `grep` for vanished commitments, wrapped so an agent can
+call it mid-task and get a structured answer that admits what it can’t see.**
+
+---
+
+## Quickstart (≈2 minutes)
+
+```sh
+pip install aperture-mcp
+```
+
+Run the bundled example (clone the repo first) — it trips on a dropped commitment against
+checked-in fixtures, with no setup, no API keys, fully offline:
+
+```sh
+python3 examples/git_decision_drift/git_decision_drift.py
+```
+
+```text
+Aperture MCP · commitment tripwire — a fixture/sample decision-doc edit
+
+  [TRIPPED ] 'ci-gates-green'             (in_before=True, in_after=False)
+  [ held  ] 'data-never-leaves-device'   (in_before=True, in_after=True)
+
+  One watched commitment vanished between the two versions; one held.
+  Aperture MCP makes the disappearance visible — you decide whether it was intended.
+```
+
+Use it from your own code:
+
+```python
+from aperture import compare, Anchor, AnchorKind
+
+result = compare(
+    state_a="We commit to: ci-gates-green before release; data-never-leaves-device.",
+    state_b="We commit to: data-never-leaves-device.",
+    anchors=[Anchor(kind=AnchorKind.COMMITMENT, id="ci-gates-green")],
+)
+print(result.status)            # DROPPED_SILENTLY
+print(result.anchor_violations) # the commitment that vanished
+```
+
+Wire it into an MCP client (Cursor, Cline, Goose, or any stdio-capable host):
+
+```jsonc
+{
+  "mcpServers": {
+    "aperture-mcp": { "command": "aperture-mcp" }
+  }
+}
+```
+
+> Prefer zero-install? Point the client at `uvx` instead:
+> `{ "command": "uvx", "args": ["aperture-mcp"] }`.
+
+---
+
+## What trips it — and what slips past
+
+Aperture MCP is a **heuristic**. We measured it on our own gold corpus and we publish the numbers
+instead of a single flattering score, because *knowing where it’s blind is the product* —
+**recall 0.375, precision 0.75** on a 41-case corpus (it catches 9 of 24 real drifts; ~1 flag in 4 is
+noise), full breakdown in [docs/measured-limits.md](docs/measured-limits.md):
+
+| Kind of change | Does Aperture MCP flag it? |
+| --- | --- |
+| A watched commitment **deleted verbatim** | ✅ Reliably — this is the one thing it’s good at |
+| A commitment **reworded / softened** (“must” → “should”) | ❌ **Missed** — the text still “matches” |
+| A commitment **paraphrased / restructured** | ❌ **Missed** |
+| A number / scope / negation quietly changed | ❌ **Missed** |
+| A commitment **translated** to another language | ⚠️ **Declines (abstains)** for a *natural-language* anchor — it can’t compare verbatim across scripts, so it returns `degraded` rather than false-flag (a commitment dropped **and** translated is missed) |
+
+> **Anchor style matters for that last row:** the abstain applies to a **natural-language** anchor. A
+> **code-identifier** anchor (the `ci-gates-green` style the quickstart teaches) is treated as
+> *translation-stable* — Aperture keeps checking it across languages, so if that exact token disappears
+> it still flags `DROPPED_SILENTLY` (usually what you want for a stable identifier).
+
+**Takeaway:** treat every flag as *“look here,”* never as *“this is wrong”* — and never assume
+silence means nothing drifted. Aperture MCP catches the **verbatim disappearance** case well and is
+honest that it catches little else. That narrow, reliable signal is useful precisely *because*
+it doesn’t pretend to be more.
+
+> **Hit one of those misses on your own docs?** That's the single most useful thing you can send us —
+> [report it in ~30s](#hit-a-miss-help-it-improve) (your wording is optional). Real misses guide what
+> we fix next.
+
+> Why not just `git diff`? You can reproduce the core check with `grep`. What Aperture MCP adds is that
+> an **agent can call it mid-task** (over MCP), it returns a **structured, directional result**
+> (`ok` / `degraded` / `DROPPED_SILENTLY` / …), and it **reports its own blind spots** in the
+> result so a human can audit the gaps. It’s ergonomics + honesty around a simple, legible check —
+> not a smarter detector.
+
+---
+
+## Why this exists
+
+Long-running and multi-agent workflows drift. A constraint set in turn 3 / session 1 / by agent A
+gets quietly edited away forty turns later, in another session, by agent B — and nobody notices
+until it ships. Aperture MCP is a **preflight you can put on the documents agents maintain**: name the
+commitments that must not silently vanish, and get a tripwire when one does.
+
+It is deliberately **small and legible**. It is not an AI that decides for you; it is a signal that
+helps *you* stay consistent with yourself.
+
+---
+
+## Who it’s for
+
+Teams and builders who **(a)** let AI agents edit repo-resident decision documents — specs, plans,
+ADRs, charters, and `AGENTS.md` files — and **(b)** keep those documents under version control.
+If your agents touch text that encodes promises, Aperture MCP gives you a cheap, honest tripwire on the
+ones you can’t afford to lose silently.
+
+---
+
+## Privacy
+
+- **Opt-in and local.** Aperture MCP runs on your machine. It makes no network calls.
+- **Never trains on your data.** Your decision text is yours; it never leaves your process.
+- **Usage logging is off by default** and, when enabled, records only **metadata** (timestamp,
+  tool, status, counts) — never your decision text or commitment wording.
+
+---
+
+## Honesty about the demo
+
+The repository ships a small **hand-authored fixture ADR** (a before/after pair under
+[`examples/git_decision_drift/fixtures/`](./examples/git_decision_drift/fixtures)), where Aperture MCP
+correctly flags a commitment we deliberately retired and stays quiet on one we kept. It is a faithful
+illustration of the mechanism — but it is a **sample of one that we author and judge ourselves**. It
+demonstrates *how the tripwire works*, **not** *that the signal is strong*. For the latter, see the
+measured per-family numbers above and in
+[`docs/measured-limits.md`](./docs/measured-limits.md).
+We have **zero external adopters yet** — if you run Aperture MCP on your own decision docs, we’d love to
+hear what it caught and what it missed.
+
+---
+
+## Project status
+
+Early, **pre-1.0**, not yet a production gate. The compare contract (`v0.2`) is frozen and covered
+by a conformance suite; the package API may still move. See [VERSIONING.md](./VERSIONING.md) for the
+compatibility policy and [CHANGELOG.md](./CHANGELOG.md) for changes.
+
+## Hit a miss? Help it improve
+
+Aperture MCP **will** miss things — that's by design (it's blind to reworded, softened, and translated
+commitments). When it misses a drift you cared about, or false-flags a rewrite, telling us is the
+single most valuable contribution:
+
+- **~30 seconds, no account/usage data, your wording is optional** →
+  [open a drift-case report](../../issues/new?template=drift-case-report.md).
+- Real misses tell us **which blind spot to fix next**, and — only if you choose to share the wording —
+  can become cases in the gold corpus that keeps the numbers in
+  [`docs/measured-limits.md`](./docs/measured-limits.md) honest.
+
+We never auto-collect anything (see [Privacy](#privacy)); this happens only when *you* choose to share.
+Questions, or "is this the right tool for my case?" → **[GitHub Discussions](../../discussions)**.
+
+More ways to help: [CONTRIBUTING.md](./CONTRIBUTING.md).
+
+## License
+
+[Apache-2.0](./LICENSE).