promptify-cmax 0.1.0__tar.gz

promptify_cmax-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+# Build / packaging
+dist/
+build/
+*.egg-info/
+
+# Python
+__pycache__/
+*.pyc
+*.pyo
+.pytest_cache/
+.benchmarks/
+.coverage
+.mypy_cache/
+.ruff_cache/
+
+# Virtual envs
+.venv/
+venv/
+env/
+
+# Index artifact (project-local)
+.promptify/
+.dca/
+
+# Internal — outreach playbook, design-partner tracking, never push public
+OUTREACH.md
+PARTNERS.md
+.private/
+
+# OS / editor
+.DS_Store
+.idea/
+.vscode/
+*.swp

promptify_cmax-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,56 @@
+# Contributing to promptify-cmax
+
+Thanks for your interest. This project is Apache-2.0 licensed and developed by [Promptify LLC](https://promptify.com).
+
+## Quick start
+
+```bash
+git clone https://github.com/promptify-com/promptify-cmax
+cd promptify-cmax
+uv sync
+uv run pytest
+```
+
+All 33 tests should pass.
+
+## Development workflow
+
+- **Tests-first.** Every behavior change ships with a failing test that turns green. Bug fixes ship with a regression test that captures the bug.
+- **Small PRs.** One concern per PR; rebase rather than merge-commit.
+- **Style.** No formatter is enforced yet; match what's already there. Type hints on public functions.
+- **Conventional Commits** for the subject line: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`.
+
+## DCO sign-off (after the first external PR)
+
+Once external contributions start landing, every commit will need a `Signed-off-by:` line per the [Developer Certificate of Origin](https://developercertificate.org/). Add it with:
+
+```bash
+git commit -s -m "your message"
+```
+
+Until then, this isn't required — sign-off enforcement will go on with the first external PR, not before.
+
+## Reporting issues
+
+Please include:
+- The query or task that produced the unexpected result
+- The relevant slice of `promptify-cmax query --top-k 10` output
+- Python version and OS
+- Project size (rough function count from `promptify-cmax index`)
+
+## What's in scope
+
+- Bug fixes in the call-graph builder, FQN resolution, query identifier extraction
+- New language support (Go, Rust, Java, C# are open ground; mention before starting)
+- Performance work on large repos (>10k files)
+- MCP protocol compliance fixes
+
+## What's not in scope (yet)
+
+- Hosted-tier features (multi-repo index, analytics, editor extensions) — those live in the Promptify SaaS layer, not this package
+- Vendoring tree-sitter grammars (we depend on the official PyPI bindings)
+- Telemetry of any kind
+
+## License
+
+By contributing, you agree your contributions are licensed under Apache-2.0, the same license as the project.

promptify_cmax-0.1.0/FEEDBACK.md

@@ -0,0 +1,68 @@
+# Design-partner feedback
+
+Thanks for trying `promptify-cmax` early. We're sending it to ~5 people before any public launch; you're one of them. Honest answers — including "this didn't help me" — are the most valuable thing you can give us.
+
+The bar for v0.1 is one binary question, asked at the end of two weeks of casual use:
+
+> **After two weeks, would you install promptify-cmax on every new repo by default?**
+
+That's the wedge-survives-or-doesn't question. Everything below helps us understand *why* your answer is yes or no.
+
+## How to send feedback
+
+Reply by email to **support@promptify.com** with the questionnaire below filled in. No call required. If you'd rather hop on a 30-minute Zoom to walk through it, mention that and we'll book one. Either path is fine; we want the answers either way.
+
+## When to send
+
+End of week 2 of trying it (or sooner if you bounce off it earlier — we want the bounce-off data too). Don't worry about polish; bullet points beat prose.
+
+---
+
+## Questionnaire (7 questions, 10 minutes)
+
+### 1. Setup friction
+
+How long did install + first successful query take? What broke, what was confusing, what did you have to look up that the QUICKSTART didn't cover?
+
+### 2. The binary question
+
+After ~two weeks of using it casually, would you install promptify-cmax on every new repo by default?
+
+- [ ] Yes — explain in one sentence what won you over
+- [ ] No — explain in one sentence what's missing or wrong
+- [ ] Maybe — explain in one sentence what would make it a clear yes
+
+### 3. Wins (concrete)
+
+Describe one specific case where the structural-context tool found the right file(s) and saved your AI agent a long detour. Include the task you asked, the files it returned, what you would have gotten with `grep` instead. Anything resembling a token count, latency feel, or "the agent got it on the first try" is gold.
+
+### 4. Losses (concrete)
+
+Describe one specific case where the tool failed — wrong files, missed the obvious file, was slow, hallucinated, didn't get installed in the agent at all. Same format: what you asked, what you got, what should have happened.
+
+### 5. The agent's behavior change
+
+Did your AI agent (Claude Code / Cursor / Continue) actually *use* the `structural_context` tool when it had access? How did you tell? If it didn't use it, why do you think — was the tool description wrong, did the agent prefer grep, were the result counts overwhelming?
+
+### 6. What would make this Pro-tier worth $X to you
+
+If this were a paid product with a hosted-indexing tier (no laptop indexing of monorepos, multi-repo BFS, editor extensions, analytics), what would the trigger be for you to upgrade? Team size? Repo size? A specific feature? A specific price point?
+
+### 7. Anything else
+
+Bugs, surprises, "I wish it did Y," people you think we should also send it to, vibes — whatever didn't fit above.
+
+---
+
+## What we won't do with your feedback
+
+- Quote you publicly without explicit permission
+- Add you to a marketing list
+- Auto-charge you when we eventually launch (this trial is free; no payment method required)
+
+## What we will do
+
+- Read every word
+- Reply within 48 hours with what we're going to fix and what we're not
+- Tell you which of your asks made it into v0.2 and which didn't
+- Send you a free Pro tier when we launch, as thanks

promptify_cmax-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 Promptify LLC
+
+   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.

promptify_cmax-0.1.0/NOTICE

@@ -0,0 +1,4 @@
+promptify-cmax
+Copyright 2026 Promptify LLC
+
+This product includes software developed at Promptify LLC (https://promptify.com).

promptify_cmax-0.1.0/PKG-INFO

@@ -0,0 +1,89 @@
+Metadata-Version: 2.4
+Name: promptify-cmax
+Version: 0.1.0
+Summary: Call-graph-aware code context retrieval for AI coding agents (MCP server + CLI)
+Project-URL: Homepage, https://promptify.com
+Project-URL: Repository, https://github.com/promptify-com/promptify-cmax
+Project-URL: Issues, https://github.com/promptify-com/promptify-cmax/issues
+Author-email: Promptify LLC <support@promptify.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai-agents,claude-code,code-context,mcp,structural-retrieval
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development
+Requires-Python: >=3.12
+Requires-Dist: mcp>=1.0
+Requires-Dist: tree-sitter-python>=0.23
+Requires-Dist: tree-sitter-typescript>=0.23
+Requires-Dist: tree-sitter>=0.23
+Requires-Dist: watchdog>=4.0
+Description-Content-Type: text/markdown
+
+# promptify-cmax
+
+**Call-graph-aware code context retrieval for AI coding agents.**
+
+When you ask Claude Code, Cursor, or any agent to fix a function, the agent typically searches the codebase with `grep` and pulls back every file that *mentions* the symbol — including specs, plans, ADRs, and unrelated definitions that happen to share a name. The model pays attention tax on all of it.
+
+`promptify-cmax` returns the files most likely to need editing, ranked by **distance in the call graph** rather than surface name match. It exposes both an [MCP](https://modelcontextprotocol.io/) server (drop-in for Claude Code, Cursor, etc.) and a CLI.
+
+## Why
+
+On a SWE-bench-derived smoke test (n=20), grep-based retrieval returned a median **142× more tokens** than the agent actually needed; structural retrieval returned the same target files at **49× lower token cost**. A reproducible benchmark at full scale (n≥200, SWE-bench-Verified) is in `bench/` — published numbers will live there.
+
+## Status
+
+**Beta** — Python and TypeScript indexing, FQN-aware call resolution, MCP server. License: Apache-2.0.
+
+## Install
+
+```bash
+pip install promptify-cmax
+```
+
+Then index your project and wire it into Claude Code / Cursor / Continue. Five-minute walkthrough with copy-pasteable MCP config snippets and troubleshooting: **[QUICKSTART.md](./QUICKSTART.md)**.
+
+## What it exposes
+
+CLI:
+- `promptify-cmax index --project-root <dir>` — build / incrementally update the structural index (one-time per repo, then automatic-on-change)
+- `promptify-cmax query --project-root <dir> "<task>"` — return ranked files for a task description
+- `promptify-cmax serve --project-root <dir>` — run as an MCP server over stdio
+
+MCP tools (when run as `serve`):
+- `structural_context(task, top_k=5)` — rank files by call-graph distance from the task's identifiers
+- `reindex()` — rebuild after large code changes
+
+## How it works
+
+1. **Index** (one-time per repo, then incremental on file change): tree-sitter walks every Python and TypeScript source file, extracts function definitions, intra-function call sites, and module-level imports; persists everything to a single SQLite file at `.promptify/code-index.db`.
+2. **Resolve** (query time): given a natural-language task, extract candidate identifiers (backtick / CamelCase / snake_case / dotted paths) and intersect with the symbols actually in the index.
+3. **BFS** (query time): walk the call graph two hops in both directions; resolve each call edge to a *specific* `(file, function)` tuple via the caller's import bindings and same-file scope, so two functions named `helper` in different files never collapse into one node.
+4. **Rank**: group reached nodes by file, sort by `(distance ASC, affected-function-count DESC)`, return the top-k.
+
+The discipline that makes this useful: **fully-qualified-name resolution**, not bare-name matching. A naive call graph treats every `def main(): ...` in the repo as the same node — typically 100+ collisions in any non-trivial Python project. We resolve through imports, so cross-file false positives don't enter the BFS frontier.
+
+## Roadmap
+
+- [x] Python + TypeScript indexing (v0.1)
+- [x] FQN-aware call resolution
+- [x] MCP server, CLI
+- [ ] Go, Rust, Java, C# (Pro)
+- [ ] Hosted multi-repo index (Pro)
+- [ ] PR-bot / CI integration (Team)
+- [ ] VSCode + JetBrains extensions
+
+## Pro / Team
+
+This package is the open-source core. [Promptify](https://promptify.com) sells a hosted layer for teams: multi-repo indexing that survives laptop churn, additional language support, token-savings analytics, editor extensions, SSO/SAML, and CI integration. Pricing and signup at [promptify.com/context](https://promptify.com/context).
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md). Issues and PRs welcome.
+
+## License
+
+Apache-2.0. Copyright © 2026 Promptify LLC. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).

promptify_cmax-0.1.0/QUICKSTART.md

@@ -0,0 +1,137 @@
+# Quickstart — promptify-cmax
+
+Five-minute install. The goal: in your next Claude Code / Cursor session, watch your AI agent stop wasting tokens on irrelevant files.
+
+## Prerequisites
+
+- Python 3.12 or newer (`python3 --version` to check)
+- An MCP-aware AI coding tool: [Claude Code](https://claude.com/claude-code), [Cursor](https://cursor.com), or [Continue](https://continue.dev)
+
+## 1. Install
+
+```bash
+pip install promptify-cmax
+```
+
+If you don't have `pip` for Python 3.12 specifically:
+
+```bash
+python3.12 -m pip install --user promptify-cmax
+```
+
+Verify:
+
+```bash
+promptify-cmax --help
+```
+
+You should see three subcommands: `index`, `query`, `serve`.
+
+## 2. Build the index for your project
+
+```bash
+cd /path/to/your/project
+promptify-cmax index --project-root .
+```
+
+Expected: a few seconds for a small project, ~10s per 1k files for larger ones. Index lands at `.promptify/code-index.db` (add to `.gitignore` — it's a build artefact).
+
+Try a query to confirm it works:
+
+```bash
+promptify-cmax query --project-root . "fix the <some_function_name> function" --top-k 5 --json-only
+```
+
+You should see five files ranked by call-graph distance, not by surface keyword match.
+
+## 3. Wire it into your AI tool
+
+### Claude Code
+
+Add to `.mcp.json` at the root of your project:
+
+```json
+{
+  "mcpServers": {
+    "promptify-cmax": {
+      "command": "promptify-cmax",
+      "args": ["serve", "--project-root", "."]
+    }
+  }
+}
+```
+
+Restart Claude Code (or run `/mcp` and reconnect). The agent now has access to two tools:
+- `structural_context(task, top_k)` — rank files by call-graph distance
+- `reindex()` — rebuild after large code changes
+
+### Cursor
+
+Cursor's MCP support is in beta. Add to `~/.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "promptify-cmax": {
+      "command": "promptify-cmax",
+      "args": ["serve", "--project-root", "/absolute/path/to/your/project"]
+    }
+  }
+}
+```
+
+Cursor needs an absolute path — `.` won't work the way it does in Claude Code.
+
+### Continue
+
+Add to `~/.continue/config.json` under `experimental.modelContextProtocolServers`:
+
+```json
+{
+  "experimental": {
+    "modelContextProtocolServers": [
+      {
+        "transport": {
+          "type": "stdio",
+          "command": "promptify-cmax",
+          "args": ["serve", "--project-root", "."]
+        }
+      }
+    ]
+  }
+}
+```
+
+## 4. Watch it work
+
+Open a coding session and ask the agent something like:
+
+> "Fix the `<some_function_name>` function — it's returning the wrong result on edge cases."
+
+Watch the agent's tool calls. With `promptify-cmax` available, it should call `structural_context` instead of (or before) `Grep`. The result is a short list of files the agent actually needs to read, instead of every file that mentions the symbol.
+
+## Re-indexing
+
+The MCP server includes a `reindex` tool the agent can call when it suspects the index is stale. You can also run it manually:
+
+```bash
+promptify-cmax index --project-root .
+```
+
+The index is incremental — files whose hash hasn't changed are skipped, so re-running is cheap.
+
+## Troubleshooting
+
+**"command not found: promptify-cmax"** — your `pip install` location isn't on `$PATH`. Try `python3.12 -m promptify_cmax.cli` directly, or check `pip show promptify-cmax` to see where the script went.
+
+**MCP server starts but tool calls return errors** — the index probably hasn't been built. Run `promptify-cmax index --project-root .` from the same directory the MCP server was started in.
+
+**Indexing takes too long** — the indexer skips `.venv/`, `node_modules/`, dotfile dirs, and `__pycache__/`. If you have a build directory or generated code dir we don't recognize, add it to a `.promptify-ignore` (planned for v0.2; in the meantime, run from a smaller project root).
+
+**Wrong files in results** — file an issue with: (1) the task you asked, (2) the result you got, (3) the result you expected. We tune the ranker on real cases, not synthetic ones.
+
+## What to expect
+
+This is v0.1.0 — Beta. Python and TypeScript are well-supported; Go / Rust / Java / C# are on the roadmap. Bugs will exist. We're treating early users as design partners, not customers; see [FEEDBACK.md](./FEEDBACK.md) if you'd like to share what you find.
+
+If you hit a wall, open a GitHub issue or email support@promptify.com.

promptify_cmax-0.1.0/README.md

@@ -0,0 +1,65 @@
+# promptify-cmax
+
+**Call-graph-aware code context retrieval for AI coding agents.**
+
+When you ask Claude Code, Cursor, or any agent to fix a function, the agent typically searches the codebase with `grep` and pulls back every file that *mentions* the symbol — including specs, plans, ADRs, and unrelated definitions that happen to share a name. The model pays attention tax on all of it.
+
+`promptify-cmax` returns the files most likely to need editing, ranked by **distance in the call graph** rather than surface name match. It exposes both an [MCP](https://modelcontextprotocol.io/) server (drop-in for Claude Code, Cursor, etc.) and a CLI.
+
+## Why
+
+On a SWE-bench-derived smoke test (n=20), grep-based retrieval returned a median **142× more tokens** than the agent actually needed; structural retrieval returned the same target files at **49× lower token cost**. A reproducible benchmark at full scale (n≥200, SWE-bench-Verified) is in `bench/` — published numbers will live there.
+
+## Status
+
+**Beta** — Python and TypeScript indexing, FQN-aware call resolution, MCP server. License: Apache-2.0.
+
+## Install
+
+```bash
+pip install promptify-cmax
+```
+
+Then index your project and wire it into Claude Code / Cursor / Continue. Five-minute walkthrough with copy-pasteable MCP config snippets and troubleshooting: **[QUICKSTART.md](./QUICKSTART.md)**.
+
+## What it exposes
+
+CLI:
+- `promptify-cmax index --project-root <dir>` — build / incrementally update the structural index (one-time per repo, then automatic-on-change)
+- `promptify-cmax query --project-root <dir> "<task>"` — return ranked files for a task description
+- `promptify-cmax serve --project-root <dir>` — run as an MCP server over stdio
+
+MCP tools (when run as `serve`):
+- `structural_context(task, top_k=5)` — rank files by call-graph distance from the task's identifiers
+- `reindex()` — rebuild after large code changes
+
+## How it works
+
+1. **Index** (one-time per repo, then incremental on file change): tree-sitter walks every Python and TypeScript source file, extracts function definitions, intra-function call sites, and module-level imports; persists everything to a single SQLite file at `.promptify/code-index.db`.
+2. **Resolve** (query time): given a natural-language task, extract candidate identifiers (backtick / CamelCase / snake_case / dotted paths) and intersect with the symbols actually in the index.
+3. **BFS** (query time): walk the call graph two hops in both directions; resolve each call edge to a *specific* `(file, function)` tuple via the caller's import bindings and same-file scope, so two functions named `helper` in different files never collapse into one node.
+4. **Rank**: group reached nodes by file, sort by `(distance ASC, affected-function-count DESC)`, return the top-k.
+
+The discipline that makes this useful: **fully-qualified-name resolution**, not bare-name matching. A naive call graph treats every `def main(): ...` in the repo as the same node — typically 100+ collisions in any non-trivial Python project. We resolve through imports, so cross-file false positives don't enter the BFS frontier.
+
+## Roadmap
+
+- [x] Python + TypeScript indexing (v0.1)
+- [x] FQN-aware call resolution
+- [x] MCP server, CLI
+- [ ] Go, Rust, Java, C# (Pro)
+- [ ] Hosted multi-repo index (Pro)
+- [ ] PR-bot / CI integration (Team)
+- [ ] VSCode + JetBrains extensions
+
+## Pro / Team
+
+This package is the open-source core. [Promptify](https://promptify.com) sells a hosted layer for teams: multi-repo indexing that survives laptop churn, additional language support, token-savings analytics, editor extensions, SSO/SAML, and CI integration. Pricing and signup at [promptify.com/context](https://promptify.com/context).
+
+## Contributing
+
+See [CONTRIBUTING.md](./CONTRIBUTING.md). Issues and PRs welcome.
+
+## License
+
+Apache-2.0. Copyright © 2026 Promptify LLC. See [LICENSE](./LICENSE) and [NOTICE](./NOTICE).