From 7b69dd3c1c578d46733ea40cc1742405dc6dda2d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Eduardo=20Javier=20Garc=C3=ADa=20L=C3=B3pez?=
 <6173685+LaloLalo1999@users.noreply.github.com>
Date: Sun, 21 Jun 2026 07:12:59 -0600
Subject: [PATCH] docs: clarify memswe reference-only usage

Tested: docs-only reference disclaimer changes; no runtime validation run.

Confidence: high
---
 framework.md                                       | 5 +++++
 skills/memorybench/references/benchmarks.md        | 4 ++++
 skills/memorybench/references/data-formats.md      | 4 ++++
 skills/memorybench/references/debugging.md         | 4 ++++
 skills/memorybench/references/provider-template.md | 5 +++++
 skills/memorybench/skill.md                        | 4 ++++
 6 files changed, 26 insertions(+)

diff --git a/framework.md b/framework.md
index 99deb79f..42cf1b23 100644
--- a/framework.md
+++ b/framework.md
@@ -1,5 +1,10 @@
 # MemoryBench Framework
 
+> **MemSWE/PAP note:** This framework diagram is reference-only for MemSWE work.
+> Use it to study provider boundaries, checkpointing, phase orchestration, and report aggregation patterns.
+> Do not treat it as canonical MemSWE architecture, task schema, condition taxonomy, verifier/scoring model, or run-record schema.
+> Do not introduce a direct `pi-memswe` dependency on this repo unless Eduardo explicitly approves.
+
 ## Architecture Flow
 
 ```
diff --git a/skills/memorybench/references/benchmarks.md b/skills/memorybench/references/benchmarks.md
index cba51972..4cb18b04 100644
--- a/skills/memorybench/references/benchmarks.md
+++ b/skills/memorybench/references/benchmarks.md
@@ -1,5 +1,9 @@
 # Benchmark Datasets Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+
 MemoryBench supports multiple benchmark datasets, each designed to test different aspects of memory systems.
 
 ## Available Benchmarks
diff --git a/skills/memorybench/references/data-formats.md b/skills/memorybench/references/data-formats.md
index 9b80c116..a5fc4ea8 100644
--- a/skills/memorybench/references/data-formats.md
+++ b/skills/memorybench/references/data-formats.md
@@ -1,5 +1,9 @@
 # Data Formats Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+
 This document explains the data structures used in MemoryBench and how to transform them for your memory system.
 
 ## UnifiedSession Format
diff --git a/skills/memorybench/references/debugging.md b/skills/memorybench/references/debugging.md
index 5b597299..a55c5626 100644
--- a/skills/memorybench/references/debugging.md
+++ b/skills/memorybench/references/debugging.md
@@ -1,5 +1,9 @@
 # Debugging and Troubleshooting Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+
 Common issues when integrating a custom provider into MemoryBench and how to resolve them.
 
 ## Quick Diagnostics
diff --git a/skills/memorybench/references/provider-template.md b/skills/memorybench/references/provider-template.md
index 169b1496..89655b42 100644
--- a/skills/memorybench/references/provider-template.md
+++ b/skills/memorybench/references/provider-template.md
@@ -1,5 +1,10 @@
 # Provider Template Reference
 
+> **MemSWE/PAP note:** Reference-only for MemSWE work.
+> These MemoryBench interfaces, formats, commands, and troubleshooting steps are examples/patterns, not canonical `pi-memswe` runtime contracts.
+> Do not copy them as MemSWE task schema, condition definitions, verifier inputs, scoring rules, or run-record schema.
+> Provider templates may inform adapter boundaries only; avoid direct dependency or generated-code coupling unless Eduardo explicitly approves.
+
 This document contains the code templates used to generate provider adapters for MemoryBench.
 
 ## Provider Interface
diff --git a/skills/memorybench/skill.md b/skills/memorybench/skill.md
index 57c21f84..d7390cb9 100644
--- a/skills/memorybench/skill.md
+++ b/skills/memorybench/skill.md
@@ -5,6 +5,10 @@ description: "Automatically benchmark your custom memory implementation against
 
 # MemoryBench Integration Skill
 
+> **MemSWE/PAP note:** This skill is retained as MemoryBench reference material only.
+> For `pi-memswe`, do not run it as an integration workflow, do not clone/couple MemoryBench into the harness, and do not treat its generated provider/benchmark/judge shapes as canonical.
+> Use only as conceptual reference for provider adapters, filesystem/RAG baselines, checkpointing, and normalized reports unless Eduardo explicitly approves otherwise.
+
 Automatically benchmark your custom memory implementation against established systems like Supermemory, Mem0, and Zep.
 
 ## What This Skill Does