awareness-memory-cloud 2.4.4__tar.gz → 2.5.0__tar.gz

{awareness_memory_cloud-2.4.4 → awareness_memory_cloud-2.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: awareness-memory-cloud
-Version: 2.4.4
+Version: 2.5.0
 Summary: Python SDK for Awareness Memory Cloud
 Author: Awareness Team
 License:                                  Apache License
@@ -638,3 +638,17 @@ export AWARENESS_OWNER_ID="your-owner-id"
 
 python examples/e2e_langchain_cloud.py
 ```
+
+---
+
+## What makes Awareness different
+
+Most memory systems pick one extraction strategy. Awareness combines them:
+
+- **Hybrid retrieval by default** — BM25 full-text + vector cosine + knowledge-graph 1-hop expansion, fused with Reciprocal Rank Fusion. 95.6% R@5 on LongMemEval, zero LLM calls on the retrieval side.
+- **Salience-aware extraction** — the client's own LLM self-scores every card on `novelty` / `durability` / `specificity`; cards below 0.4 on novelty or durability are dropped server-side. Framework metadata (`Sender (untrusted metadata)`, `turn_brief`) is filtered before extraction runs.
+- **Project isolation** — `X-Awareness-Project-Dir` header scopes memory per project.
+- **Zero-LLM backend** — all extraction runs on your LLM (Claude, GPT-4, Gemini, local Llama). The backend is a coordinator + storage layer; no inference costs pass through to you.
+- **One memory, many clients** — same data reachable via Claude Code, OpenClaw, npm / pip / ClawHub, MCP server.
+
+See [`docs/analysis/MEMPALACE_COMPARISON_2026-04-17.md`](https://github.com/edwin-hao-ai/Awareness/blob/main/docs/analysis/MEMPALACE_COMPARISON_2026-04-17.md) for the honest side-by-side against MemPalace.

{awareness_memory_cloud-2.4.4 → awareness_memory_cloud-2.5.0}/README.md

@@ -389,3 +389,17 @@ export AWARENESS_OWNER_ID="your-owner-id"
 
 python examples/e2e_langchain_cloud.py
 ```
+
+---
+
+## What makes Awareness different
+
+Most memory systems pick one extraction strategy. Awareness combines them:
+
+- **Hybrid retrieval by default** — BM25 full-text + vector cosine + knowledge-graph 1-hop expansion, fused with Reciprocal Rank Fusion. 95.6% R@5 on LongMemEval, zero LLM calls on the retrieval side.
+- **Salience-aware extraction** — the client's own LLM self-scores every card on `novelty` / `durability` / `specificity`; cards below 0.4 on novelty or durability are dropped server-side. Framework metadata (`Sender (untrusted metadata)`, `turn_brief`) is filtered before extraction runs.
+- **Project isolation** — `X-Awareness-Project-Dir` header scopes memory per project.
+- **Zero-LLM backend** — all extraction runs on your LLM (Claude, GPT-4, Gemini, local Llama). The backend is a coordinator + storage layer; no inference costs pass through to you.
+- **One memory, many clients** — same data reachable via Claude Code, OpenClaw, npm / pip / ClawHub, MCP server.
+
+See [`docs/analysis/MEMPALACE_COMPARISON_2026-04-17.md`](https://github.com/edwin-hao-ai/Awareness/blob/main/docs/analysis/MEMPALACE_COMPARISON_2026-04-17.md) for the honest side-by-side against MemPalace.

{awareness_memory_cloud-2.4.4 → awareness_memory_cloud-2.5.0}/awareness_memory_cloud.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: awareness-memory-cloud
-Version: 2.4.4
+Version: 2.5.0
 Summary: Python SDK for Awareness Memory Cloud
 Author: Awareness Team
 License:                                  Apache License
@@ -638,3 +638,17 @@ export AWARENESS_OWNER_ID="your-owner-id"
 
 python examples/e2e_langchain_cloud.py
 ```
+
+---
+
+## What makes Awareness different
+
+Most memory systems pick one extraction strategy. Awareness combines them:
+
+- **Hybrid retrieval by default** — BM25 full-text + vector cosine + knowledge-graph 1-hop expansion, fused with Reciprocal Rank Fusion. 95.6% R@5 on LongMemEval, zero LLM calls on the retrieval side.
+- **Salience-aware extraction** — the client's own LLM self-scores every card on `novelty` / `durability` / `specificity`; cards below 0.4 on novelty or durability are dropped server-side. Framework metadata (`Sender (untrusted metadata)`, `turn_brief`) is filtered before extraction runs.
+- **Project isolation** — `X-Awareness-Project-Dir` header scopes memory per project.
+- **Zero-LLM backend** — all extraction runs on your LLM (Claude, GPT-4, Gemini, local Llama). The backend is a coordinator + storage layer; no inference costs pass through to you.
+- **One memory, many clients** — same data reachable via Claude Code, OpenClaw, npm / pip / ClawHub, MCP server.
+
+See [`docs/analysis/MEMPALACE_COMPARISON_2026-04-17.md`](https://github.com/edwin-hao-ai/Awareness/blob/main/docs/analysis/MEMPALACE_COMPARISON_2026-04-17.md) for the honest side-by-side against MemPalace.

{awareness_memory_cloud-2.4.4 → awareness_memory_cloud-2.5.0}/memory_cloud/client.py

@@ -421,20 +421,34 @@ class MemoryCloudClient:
             body["ids"] = ids
 
         # Local daemon bridge: route through awareness_recall MCP tool.
+        # F-053 single-parameter surface — pass only `query` and let the daemon
+        # auto-route (query-type classifier + recency channel + budget-tier
+        # shaping). Legacy fields are still forwarded for backwards-compat with
+        # pre-F-053 daemons but marked explicitly so server-side deprecation
+        # logging can trace who's still sending them.
         if self._should_use_daemon():
             daemon_args: Dict[str, Any] = {
-                "semantic_query": query,
+                "query": query,
                 "limit": limit,
-                "detail": detail or "summary",
             }
-            if effective_keyword:
+            # Token budget drives bucket shaping (raw-heavy / mixed / card-only).
+            # Callers can override via custom_kwargs["token_budget"].
+            token_budget = (custom_kwargs or {}).get("token_budget")
+            if token_budget is not None:
+                daemon_args["token_budget"] = int(token_budget)
+            if agent_role:
+                daemon_args["agent_role"] = agent_role
+            # Legacy fields — only forwarded if caller explicitly passed them.
+            # Daemon will log [deprecated param used] for these.
+            if effective_keyword and keyword_query is not None:
                 daemon_args["keyword_query"] = effective_keyword
             if scope:
                 daemon_args["scope"] = scope
-            if recall_mode:
+            if recall_mode and recall_mode != "precise":
+                # "precise" is the SDK default — don't forward it as legacy.
                 daemon_args["recall_mode"] = recall_mode
-            if agent_role:
-                daemon_args["agent_role"] = agent_role
+            if detail is not None:
+                daemon_args["detail"] = detail
             if ids:
                 daemon_args["ids"] = ids
             daemon_result = self.call_local_daemon("awareness_recall", daemon_args)
@@ -1521,22 +1535,30 @@ class MemoryCloudClient:
         self,
         memory_id: str,
         skill_id: str,
+        outcome: Optional[str] = "success",
         trace_id: Optional[str] = None,
     ) -> Dict[str, Any]:
         """
-        Mark a skill as used, resetting its decay timer.
+        Mark a skill as used with outcome feedback.
 
         Args:
             memory_id: Target memory id.
             skill_id: The skill to mark as used.
+            outcome: "success" (default), "partial", or "failed".
+                     Failed outcomes decrease confidence; 3+ consecutive
+                     failures auto-flag the skill for review.
             trace_id: Optional trace id.
 
         Returns:
             Updated skill data.
         """
+        body = None
+        if outcome and outcome != "success":
+            body = {"outcome": outcome}
         data, resolved_trace = self._request(
             method="POST",
             path=f"/memories/{memory_id}/skills/{skill_id}/use",
+            json_payload=body,
             trace_id=trace_id,
         )
         return self._attach_trace(data, resolved_trace)

{awareness_memory_cloud-2.4.4 → awareness_memory_cloud-2.5.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "awareness-memory-cloud"
-version = "2.4.4"
+version = "2.5.0"
 description = "Python SDK for Awareness Memory Cloud"
 readme = "README.md"
 license = { file = "LICENSE" }