context-engineering-core 0.12.0__tar.gz

context_engineering_core-0.12.0/.gitignore

@@ -0,0 +1,21 @@
+.DS_Store
+.env
+.env.*
+!.env.example
+.venv/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.hypothesis/
+*.egg-info/
+build/
+dist/
+output/*.sqlite*
+output/*.log
+output/private/
+**/output/*.sqlite*
+**/output/*.log
+**/output/private/
+brain/index.json

context_engineering_core-0.12.0/CHANGELOG.md

@@ -0,0 +1,81 @@
+# Changelog
+
+Earlier versions (0.1.0–0.9.6) are documented in `docs/C01_REPORT.md` through
+`docs/C10_STORAGE_ACL_REPORT.md` and preserved as wheels under `archives/`.
+
+## 0.12.0 — 2026-10-31 (unreleased)
+
+### Added
+- `context_engine.adapters`: `openai_chat`, `anthropic_messages`,
+  `langchain_messages` and `turns_from_openai`. No new core dependencies; optional
+  `[langchain]` extra (`langchain-core>=1.0,<2`).
+- Inception (Mercury) provider: `InceptionGenerationConfig` (mercury-3/2.5/2,
+  temperature 0.5–1, reasoning instant–high) and `InceptionTransport`, reusing the
+  bounded client, ledger and metered spend cap. `scripts/inception_smoke.py` makes
+  one capped call only with `--allow-live`; live smoke passed (D111).
+- `context-engine-mcp`: prototype MCP server over `MemoryStore` (stdio JSON-RPC,
+  standard library only) with `add_message`, `pin_fact`, `get_context`, `forget`.
+  See `docs/MCP.md`.
+
+### Changed (performance)
+- Bounded process-wide token-count cache (32,768 entries, texts up to 4,096
+  characters). Counts and assembly output are identical; benchmark gates unchanged.
+  All-layers assembly on the 100-turn benchmark (same history, new questions):
+  median 247 → 95 ms at 900 tokens, 481 → 208 ms at 3000 tokens.
+
+### Changed
+- Provider transports carry their own endpoint/adapter identity (Groq request keys
+  are unchanged). HTTP 402 now maps to `billing_or_quota`.
+
+### Unchanged
+- Assembly output and defaults. 0.11.0 wheel/freeze archived in
+  `archives/c12-adapters-0120/`.
+
+## 0.11.0 — 2026-10-31 (TestPyPI)
+
+### Changed (behavior)
+- `RetrievalConfig.recover_capped_window` now defaults to `True` (owner decision
+  D109). RETRIEVE can restore original evidence that CAP removed from recent
+  WINDOW turns. Offline retention on the frozen corpus: 31/31 at 900 and 3000
+  tokens (was 29/31 and 19/31), for about 5–15% more assembly latency. Pass
+  `RetrievalConfig(recover_capped_window=False)` for the old behavior.
+- Existing `MemoryStore` chunk indexes are rebuilt once after upgrading, because
+  the index profile hashes the full retrieval configuration.
+- `strategy-eval`: `combined` now uses the new defaults; `combined_recover` is
+  replaced by `combined_no_recover` (the 0.10.0 defaults).
+
+### Added
+- Apache-2.0 `LICENSE`; license, classifiers and project URLs in package metadata.
+- Newcomer README with a tested quick example (`tests/test_readme_example.py`).
+
+### Unchanged
+- The frozen benchmark harness pins `recover_capped_window=False`, so A0–A5 and
+  historical gates reproduce. 0.10.0 wheel/freeze archived in
+  `archives/c11-recover-default-0110/`.
+
+## 0.10.0 — 2026-10-31 (unreleased)
+
+### Added
+- `context_engine.summaries`: `update_summary` for explicit, amortized summary
+  refresh; `ExtractiveSummarizer` (deterministic, model-free); `PromptSummarizer`
+  (wraps any `complete(messages) -> str` function; no provider SDK imported).
+- `PrefixSummaryPolicy` and `SummarySnapshot.covers_prefix`: opt-in reuse of a
+  summary that covers the oldest omitted turns. New diagnostic reason
+  `summary_reused_prefix`.
+- `MemoryStore.assemble(..., summary_prefix=True)`.
+- `context-engine strategy-eval`: offline comparison of full history, WINDOW,
+  WINDOW+summary, WINDOW+retrieval, all layers, and all layers with
+  `recover_capped_window`, with retention, chunk precision, turn recall, token
+  reduction and latency.
+- `examples/rolling_summary.py`.
+
+### Changed
+- `MemoryStore` keeps a stored summary when the appended, updated or deleted turn
+  is not covered by it. Changing or deleting a covered turn still removes it, and
+  lineage is still re-verified on every read.
+- `pytest` now works without `python -m` (`pythonpath = ["."]`).
+
+### Unchanged
+- Default `assemble_context` output, `FrozenSummaryPolicy` exact matching, and
+  `recover_capped_window=False` default.
+- Historical experiments: 0.9.6 wheel/freeze archived in `archives/c11-summaries-0100/`.

context_engineering_core-0.12.0/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.

context_engineering_core-0.12.0/PKG-INFO

@@ -0,0 +1,203 @@
+Metadata-Version: 2.5
+Name: context-engineering-core
+Version: 0.12.0
+Summary: Provider-independent context layers, source contracts, and token budget accounting
+Project-URL: Homepage, https://github.com/Nandu1729/Context-Engine
+Project-URL: Repository, https://github.com/Nandu1729/Context-Engine
+Project-URL: Issues, https://github.com/Nandu1729/Context-Engine/issues
+Project-URL: Changelog, https://github.com/Nandu1729/Context-Engine/blob/main/CHANGELOG.md
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: context-window,llm,memory,retrieval,summarization,token-budget
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.12
+Requires-Dist: pywin32==311; sys_platform == 'win32'
+Requires-Dist: rank-bm25<0.3,>=0.2.2
+Requires-Dist: tiktoken<0.15,>=0.14
+Provides-Extra: langchain
+Requires-Dist: langchain-core<2,>=1.0; extra == 'langchain'
+Provides-Extra: provider
+Requires-Dist: httpx<0.29,>=0.28; extra == 'provider'
+Provides-Extra: reports
+Requires-Dist: matplotlib<3.12,>=3.11; extra == 'reports'
+Provides-Extra: service
+Requires-Dist: fastapi<0.136,>=0.135; extra == 'service'
+Requires-Dist: httpx<0.29,>=0.28; extra == 'service'
+Requires-Dist: pyjwt[crypto]<3,>=2.12; extra == 'service'
+Requires-Dist: uvicorn<0.42,>=0.41; extra == 'service'
+Description-Content-Type: text/markdown
+
+# Context Engine
+
+Fit long conversations into a fixed token budget for any LLM, and know exactly
+where every piece of context came from.
+
+`context-engineering-core` is a small Python library. You give it the full chat
+history, the new question and a token budget. It returns a list of chat messages
+that fits the budget. Those messages keep the recent turns, the facts you pinned,
+and the older evidence that matches the question. It never calls a model by
+itself, so you send the messages to any provider you like.
+
+> **Status: alpha (0.12.0).** Good for developers to try locally. It is not yet
+> proven on real-world data, and there is no hosted service. See
+> [What is not proven yet](#what-is-not-proven-yet).
+
+## Install
+
+Requires Python 3.12+.
+
+```sh
+pip install context-engineering-core        # after the first PyPI release
+```
+
+From source:
+
+```sh
+git clone https://github.com/Nandu1729/Context-Engine.git
+cd Context-Engine
+uv sync --locked
+uv run context-engine check                  # prints "deps ok"
+```
+
+The first run downloads the tokenizer vocabulary (tiktoken `o200k_harmony`) once.
+After that, everything works offline.
+
+## Quick example
+
+```python
+from context_engine import assemble_context
+from context_engine.config import BudgetConfig
+from context_engine.models import KeyedPins, Message, Role, Scope, Turn
+
+scope = Scope("my-app", "chat-1")
+notes = [f"Note {i}: shipment {i} left from dock D-{i}." for i in range(300)]
+history = [Turn(f"t{i}", scope, (Message(f"m{i}", Role.USER, text),)) for i, text in enumerate(notes)]
+
+result = assemble_context(history, "Which dock did shipment 42 leave from?", KeyedPins(scope),
+                          BudgetConfig(input_cap=900), system="Answer only from the context.")
+print(result.diagnostics.estimate.estimated_tokens, "of", result.diagnostics.input_allowance)
+print("evidence from turns:", result.diagnostics.retrieved_turn_ids)
+messages = result.messages  # ready for any chat-completions API
+```
+
+The 300 notes are far over the 900-token budget. The result fits (about 716 of
+900 tokens), and turn `t42`, the one with the answer, is among the retrieved
+evidence. Then send `messages` to OpenAI, Anthropic, Groq or a local model.
+
+## Use it with your provider
+
+`context_engine.adapters` reshapes the result for common clients. None of them is
+a dependency of the engine:
+
+```python
+from context_engine.adapters import anthropic_messages, langchain_messages, openai_chat, turns_from_openai
+
+openai_client.chat.completions.create(model="...", **openai_chat(result))             # OpenAI, Groq, local servers
+anthropic_client.messages.create(model="...", max_tokens=512, **anthropic_messages(result))
+chat_model.invoke(langchain_messages(result))  # pip install 'context-engineering-core[langchain]'
+
+history = turns_from_openai(existing_openai_messages, scope)  # reuse a chat history you already have
+```
+
+### Use it from an MCP client
+
+`context-engine-mcp --data-dir ./context-memory` runs a local MCP server (stdio) with
+`add_message`, `pin_fact`, `get_context` and `forget` tools. Prototype; see the
+[MCP guide](https://github.com/Nandu1729/Context-Engine/blob/main/docs/MCP.md).
+
+## How it works
+
+Every call runs five steps, in this order:
+
+| Step | What it does |
+|---|---|
+| CAP | Shortens very long messages (keeps the start and end). |
+| PIN | Always includes facts you pinned with `KeyedPins`. |
+| RETRIEVE | Finds older text that matches the question (BM25), including text that CAP cut from recent turns. |
+| WINDOW | Keeps as many recent turns as fit. |
+| SUMMARIZE | Adds a summary of older turns, if you supply one. |
+
+You can turn each step on or off with `AssemblyOptions`. For a chat that keeps
+growing, `MemoryStore` saves turns, pins and summaries in SQLite. The
+[rolling summary example](https://github.com/Nandu1729/Context-Engine/blob/main/examples/rolling_summary.py) shows a full loop.
+
+## What the engine guarantees
+
+These are enforced in code and covered by about 1,400 tests:
+
+- **Within budget, or a clear error.** The result never exceeds your input
+  budget as counted by the local tokenizer. If the required parts (system
+  prompt, question, pins) cannot fit, you get a typed error, not a silently
+  cut prompt.
+- **Provenance.** Every recent-turn and retrieved block carries source
+  references: turn, message, revision, character range and a content hash.
+  A summary records which turns it covers and their hashes, and is rejected if
+  any of them changed. `result.diagnostics` lists which turns were kept,
+  retrieved or dropped, and why.
+- **No hidden model calls.** Assembly is local and deterministic. Summaries are
+  made only when you call `update_summary()`, with a summarizer you choose.
+- **History is data, not instructions.** Older turns, retrieved text and
+  summaries are labelled as data blocks inside user content, never as system
+  instructions.
+- **Your originals are never changed.** CAP and retrieval work on copies.
+  Retrieval can bring back the original text of a capped message.
+
+## What is not proven yet
+
+- **Answer quality.** Tests measure whether the needed facts *reach* the model's
+  context, not whether the model then answers correctly. On the built-in
+  benchmark, the default settings keep 31 of 31 planted facts at 900 and 3000
+  tokens. But that benchmark is one synthetic conversation written alongside
+  the engine.
+- **Real-world data.** There are no results yet on real user conversations or
+  on questions phrased differently from the source text. Retrieval is
+  keyword-based (BM25), so heavily reworded questions may miss evidence.
+- **Exact provider token counts.** Budgets use a local tokenizer estimate.
+  Providers may count differently. On small requests, provider counts were up
+  to 1.78× the local estimate in past tests, so leave headroom or calibrate.
+- **Speed.** With all five steps on, assembly takes about 250–350 ms on the
+  benchmark (about 17–35 ms without CAP). Faster CAP is on the roadmap.
+- **Production use.** The local HTTP service is for development. It has not
+  been load-tested or security-qualified for production.
+
+## Try it
+
+```sh
+uv run context-engine demo-layers                         # the five steps on sample data
+uv run --offline context-engine strategy-eval --budget 900   # compare strategies, no model calls
+uv run --offline python examples/rolling_summary.py       # memory + rolling summaries
+```
+
+## Documentation
+
+- [SDK and CLI guide](https://github.com/Nandu1729/Context-Engine/blob/main/docs/PIPELINE.md): inputs, options, diagnostics, summaries.
+- [Benchmark report](https://github.com/Nandu1729/Context-Engine/blob/main/docs/BENCHMARK_REPORT.md): strategy comparison and its limits.
+- [Security audit](https://github.com/Nandu1729/Context-Engine/blob/main/docs/SECURITY_AUDIT.md): trust boundaries and known gaps.
+- [Architecture](https://github.com/Nandu1729/Context-Engine/blob/main/docs/ARCHITECTURE.md) and [current status](https://github.com/Nandu1729/Context-Engine/blob/main/docs/CURRENT_STATUS.md).
+- [Changelog](https://github.com/Nandu1729/Context-Engine/blob/main/CHANGELOG.md).
+
+## For contributors
+
+```sh
+uv sync --locked
+uv run --locked --offline pytest -q
+uv run ruff check src
+```
+
+The repository also holds frozen historical benchmarks under `archives/` and
+`output/`, and a project log under `brain/` (start at `brain/INDEX.md`; check it
+with `python3 scripts/brain.py check`). Historical experiments only run with their
+archived wheels, on purpose. The [local quickstart](https://github.com/Nandu1729/Context-Engine/blob/main/docs/LOCAL_QUICKSTART.md)
+and [checkpoints](https://github.com/Nandu1729/Context-Engine/blob/main/docs/CHECKPOINTS.md)
+cover the full project history.
+
+## License
+
+[Apache-2.0](https://github.com/Nandu1729/Context-Engine/blob/main/LICENSE).

context_engineering_core-0.12.0/README.md

@@ -0,0 +1,167 @@
+# Context Engine
+
+Fit long conversations into a fixed token budget for any LLM, and know exactly
+where every piece of context came from.
+
+`context-engineering-core` is a small Python library. You give it the full chat
+history, the new question and a token budget. It returns a list of chat messages
+that fits the budget. Those messages keep the recent turns, the facts you pinned,
+and the older evidence that matches the question. It never calls a model by
+itself, so you send the messages to any provider you like.
+
+> **Status: alpha (0.12.0).** Good for developers to try locally. It is not yet
+> proven on real-world data, and there is no hosted service. See
+> [What is not proven yet](#what-is-not-proven-yet).
+
+## Install
+
+Requires Python 3.12+.
+
+```sh
+pip install context-engineering-core        # after the first PyPI release
+```
+
+From source:
+
+```sh
+git clone https://github.com/Nandu1729/Context-Engine.git
+cd Context-Engine
+uv sync --locked
+uv run context-engine check                  # prints "deps ok"
+```
+
+The first run downloads the tokenizer vocabulary (tiktoken `o200k_harmony`) once.
+After that, everything works offline.
+
+## Quick example
+
+```python
+from context_engine import assemble_context
+from context_engine.config import BudgetConfig
+from context_engine.models import KeyedPins, Message, Role, Scope, Turn
+
+scope = Scope("my-app", "chat-1")
+notes = [f"Note {i}: shipment {i} left from dock D-{i}." for i in range(300)]
+history = [Turn(f"t{i}", scope, (Message(f"m{i}", Role.USER, text),)) for i, text in enumerate(notes)]
+
+result = assemble_context(history, "Which dock did shipment 42 leave from?", KeyedPins(scope),
+                          BudgetConfig(input_cap=900), system="Answer only from the context.")
+print(result.diagnostics.estimate.estimated_tokens, "of", result.diagnostics.input_allowance)
+print("evidence from turns:", result.diagnostics.retrieved_turn_ids)
+messages = result.messages  # ready for any chat-completions API
+```
+
+The 300 notes are far over the 900-token budget. The result fits (about 716 of
+900 tokens), and turn `t42`, the one with the answer, is among the retrieved
+evidence. Then send `messages` to OpenAI, Anthropic, Groq or a local model.
+
+## Use it with your provider
+
+`context_engine.adapters` reshapes the result for common clients. None of them is
+a dependency of the engine:
+
+```python
+from context_engine.adapters import anthropic_messages, langchain_messages, openai_chat, turns_from_openai
+
+openai_client.chat.completions.create(model="...", **openai_chat(result))             # OpenAI, Groq, local servers
+anthropic_client.messages.create(model="...", max_tokens=512, **anthropic_messages(result))
+chat_model.invoke(langchain_messages(result))  # pip install 'context-engineering-core[langchain]'
+
+history = turns_from_openai(existing_openai_messages, scope)  # reuse a chat history you already have
+```
+
+### Use it from an MCP client
+
+`context-engine-mcp --data-dir ./context-memory` runs a local MCP server (stdio) with
+`add_message`, `pin_fact`, `get_context` and `forget` tools. Prototype; see the
+[MCP guide](https://github.com/Nandu1729/Context-Engine/blob/main/docs/MCP.md).
+
+## How it works
+
+Every call runs five steps, in this order:
+
+| Step | What it does |
+|---|---|
+| CAP | Shortens very long messages (keeps the start and end). |
+| PIN | Always includes facts you pinned with `KeyedPins`. |
+| RETRIEVE | Finds older text that matches the question (BM25), including text that CAP cut from recent turns. |
+| WINDOW | Keeps as many recent turns as fit. |
+| SUMMARIZE | Adds a summary of older turns, if you supply one. |
+
+You can turn each step on or off with `AssemblyOptions`. For a chat that keeps
+growing, `MemoryStore` saves turns, pins and summaries in SQLite. The
+[rolling summary example](https://github.com/Nandu1729/Context-Engine/blob/main/examples/rolling_summary.py) shows a full loop.
+
+## What the engine guarantees
+
+These are enforced in code and covered by about 1,400 tests:
+
+- **Within budget, or a clear error.** The result never exceeds your input
+  budget as counted by the local tokenizer. If the required parts (system
+  prompt, question, pins) cannot fit, you get a typed error, not a silently
+  cut prompt.
+- **Provenance.** Every recent-turn and retrieved block carries source
+  references: turn, message, revision, character range and a content hash.
+  A summary records which turns it covers and their hashes, and is rejected if
+  any of them changed. `result.diagnostics` lists which turns were kept,
+  retrieved or dropped, and why.
+- **No hidden model calls.** Assembly is local and deterministic. Summaries are
+  made only when you call `update_summary()`, with a summarizer you choose.
+- **History is data, not instructions.** Older turns, retrieved text and
+  summaries are labelled as data blocks inside user content, never as system
+  instructions.
+- **Your originals are never changed.** CAP and retrieval work on copies.
+  Retrieval can bring back the original text of a capped message.
+
+## What is not proven yet
+
+- **Answer quality.** Tests measure whether the needed facts *reach* the model's
+  context, not whether the model then answers correctly. On the built-in
+  benchmark, the default settings keep 31 of 31 planted facts at 900 and 3000
+  tokens. But that benchmark is one synthetic conversation written alongside
+  the engine.
+- **Real-world data.** There are no results yet on real user conversations or
+  on questions phrased differently from the source text. Retrieval is
+  keyword-based (BM25), so heavily reworded questions may miss evidence.
+- **Exact provider token counts.** Budgets use a local tokenizer estimate.
+  Providers may count differently. On small requests, provider counts were up
+  to 1.78× the local estimate in past tests, so leave headroom or calibrate.
+- **Speed.** With all five steps on, assembly takes about 250–350 ms on the
+  benchmark (about 17–35 ms without CAP). Faster CAP is on the roadmap.
+- **Production use.** The local HTTP service is for development. It has not
+  been load-tested or security-qualified for production.
+
+## Try it
+
+```sh
+uv run context-engine demo-layers                         # the five steps on sample data
+uv run --offline context-engine strategy-eval --budget 900   # compare strategies, no model calls
+uv run --offline python examples/rolling_summary.py       # memory + rolling summaries
+```
+
+## Documentation
+
+- [SDK and CLI guide](https://github.com/Nandu1729/Context-Engine/blob/main/docs/PIPELINE.md): inputs, options, diagnostics, summaries.
+- [Benchmark report](https://github.com/Nandu1729/Context-Engine/blob/main/docs/BENCHMARK_REPORT.md): strategy comparison and its limits.
+- [Security audit](https://github.com/Nandu1729/Context-Engine/blob/main/docs/SECURITY_AUDIT.md): trust boundaries and known gaps.
+- [Architecture](https://github.com/Nandu1729/Context-Engine/blob/main/docs/ARCHITECTURE.md) and [current status](https://github.com/Nandu1729/Context-Engine/blob/main/docs/CURRENT_STATUS.md).
+- [Changelog](https://github.com/Nandu1729/Context-Engine/blob/main/CHANGELOG.md).
+
+## For contributors
+
+```sh
+uv sync --locked
+uv run --locked --offline pytest -q
+uv run ruff check src
+```
+
+The repository also holds frozen historical benchmarks under `archives/` and
+`output/`, and a project log under `brain/` (start at `brain/INDEX.md`; check it
+with `python3 scripts/brain.py check`). Historical experiments only run with their
+archived wheels, on purpose. The [local quickstart](https://github.com/Nandu1729/Context-Engine/blob/main/docs/LOCAL_QUICKSTART.md)
+and [checkpoints](https://github.com/Nandu1729/Context-Engine/blob/main/docs/CHECKPOINTS.md)
+cover the full project history.
+
+## License
+
+[Apache-2.0](https://github.com/Nandu1729/Context-Engine/blob/main/LICENSE).