@dzhechkov/keysarium 1.3.0 → 1.5.0

package/templates/lib/dream-engine.md

@@ -118,7 +118,7 @@ Location: `.keysarium/insights/trigger-state.json`
 4. Scan all `*.json` files recursively under `.keysarium/memory/` (excluding `config.json`, `reward-summary.json`, `domain-patterns.json`).
 5. Parse each as a RewardRecord (schema defined in `lib/memory-protocol.md`).
 6. Exclude records where `expires_at < current_date`.
-7. Sort by `reward` DESC, then `timestamp` DESC.
+7. Sort by `reward` DESC, then `usage_count` DESC, then `timestamp` DESC. Records with higher usage_count carry more weight in concept graph construction.
 8. Take top 200 records.
 9. If fewer than 5 valid records, exit with status `insufficient_data`.
 

package/templates/lib/memory-protocol.md

@@ -83,6 +83,7 @@ The index provides a compact catalog of all records, enabling targeted reads ins
       "reward": 0.7,
       "skill": "goap-research-ed25519",
       "tier": "hot",
+      "usage_count": 0,
       "file": "banking/bank_kc_automation/phase-2_2026-03-01T12-30-00.json",
       "expires_at": "2026-08-28T12:30:00Z"
     }
@@ -128,7 +129,7 @@ Call at the **start** of each pipeline phase to load relevant historical pattern
    - Update `index.json`: set `tier` to `"cold"`, update `file` path
    - Log: "Archived {count} records to cold storage in {domain}"
 6. **Purge ancient records (v1.1):** Delete records from `_archive/` older than `tier_cold_days`. In v1.0 mode, delete records where `expires_at < current_date`. Update `index.json`. Log: "Purged {count} expired records from {domain}"
-7. **Sort:** By `reward` DESC, then `timestamp` DESC. HOT and WARM records first; COLD records included only if result count < `max_results_per_query`.
+7. **Sort:** By `reward` DESC, then `usage_count` DESC, then `timestamp` DESC. HOT and WARM records first; COLD records included only if result count < `max_results_per_query`. Records with higher usage_count are more battle-tested and should be preferred when rewards are equal.
 8. **Limit:** Return top `max_results_per_query` records (default 10).
 9. **Enrich:** Also load `.keysarium/memory/_patterns/domain-patterns.json` for matching domain patterns.
 
@@ -167,6 +168,7 @@ After calling `memory_query()`, the agent should:
 2. If `records` is non-empty, review the top 3 records for relevant approaches
 3. If `patterns` is non-empty, apply actionable advice to current phase execution
 4. If both are empty (first run), proceed normally
+5. **Increment usage_count:** For each record actually applied (top 3), increment `usage_count` in both the record file and the index entry. Records with higher usage_count are more proven — prioritize them in future queries.
 
 ## Protocol: memory_store(result, reward)
 
@@ -209,7 +211,7 @@ Call at each **checkpoint** after the user responds, to persist the phase outcom
 4. **Generate filename:** `{phase}_{ISO-timestamp}.json` (e.g., `phase-2_2026-03-01T12-30-00.json`).
 5. **Write file:** Write JSON to `.keysarium/memory/{domain}/{slug}/{filename}`.
 6. **Update index (v1.1):** Read `.keysarium/memory/index.json` (or create if absent and tier config is present):
-   - Add record entry to `records` map: key = record id, value = `{domain, phase, slug, reward, skill, tier: "hot", file, expires_at}`
+   - Add record entry to `records` map: key = record id, value = `{domain, phase, slug, reward, skill, tier: "hot", usage_count: 0, file, expires_at}`
    - Increment `record_count`
    - Update `by_domain` aggregate: increment count, add slug if new, recalculate `avg_reward`
    - Update `by_phase` aggregate: increment count, recalculate `avg_reward`
@@ -248,6 +250,7 @@ Call at each **checkpoint** after the user responds, to persist the phase outcom
     "promise_emitted": "RESEARCH_PARANOID_PASSED"
   },
   "promise_tag": "RESEARCH_PARANOID_PASSED",
+  "usage_count": 0,
   "expires_at": "2026-08-28T12:30:00Z"
 }
 ```
@@ -277,6 +280,7 @@ Tier thresholds are configurable via `config.json` fields: `tier_hot_days`, `tie
   "reward_label": "good",
   "skill_used": "goap-research-ed25519",
   "promise_tag": "RESEARCH_PARANOID_PASSED",
+  "usage_count": 3,
   "summary": "User requested minor edits to competitor analysis section. ok, but expand the FinTech competitor section",
   "archived_at": "2026-03-02T14:00:00Z",
   "original_timestamp": "2026-01-01T12:00:00Z"

package/templates/lib/reward-tracker.md

@@ -86,12 +86,14 @@ Group records by `skill_used` and cross-reference with domain:
   "goap-research-ed25519": {
     "overall_avg": 0.74,
     "total_runs": 15,
+    "total_usage_count": 42,
     "by_domain": {
-      "banking": { "avg": 0.65, "runs": 8 },
-      "retail": { "avg": 0.85, "runs": 7 }
+      "banking": { "avg": 0.65, "runs": 8, "usage_count": 18 },
+      "retail": { "avg": 0.85, "runs": 7, "usage_count": 24 }
     },
     "best_domain": "retail",
-    "worst_domain": "banking"
+    "worst_domain": "banking",
+    "most_reused_domain": "retail"
   }
 }
 ```
@@ -110,6 +112,7 @@ Analyze accumulated data to detect actionable patterns. Each pattern has a confi
 | Improving Trend | Trend = "improving" for phase in domain | "{phase} quality is improving in {domain} domain" |
 | Degrading Trend | Trend = "degrading" for phase in domain | "{phase} quality is degrading in {domain} -- investigate" |
 | Time Overhead | Phase avg iterations > 2.0 in domain | "{domain} cases require more iterations in {phase}" |
+| High Reuse | Record usage_count >= 5 | "Pattern from {slug}/{phase} is highly reused ({count} times) — consider promoting to a rule" |
 
 **Confidence Calculation:**
 ```