From 197376650e07f299a9e08673a8a906728d36b9c9 Mon Sep 17 00:00:00 2001
From: Lumi AI Workspace <hong@cloudjetkpi.com>
Date: Tue, 7 Jul 2026 00:40:47 +0700
Subject: [PATCH] docs: add evidence boundary guide

---
 docs/evidence/EVIDENCE_BOUNDARY_GUIDE.md | 35 ++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 docs/evidence/EVIDENCE_BOUNDARY_GUIDE.md

diff --git a/docs/evidence/EVIDENCE_BOUNDARY_GUIDE.md b/docs/evidence/EVIDENCE_BOUNDARY_GUIDE.md
new file mode 100644
index 00000000..b63a75b2
--- /dev/null
+++ b/docs/evidence/EVIDENCE_BOUNDARY_GUIDE.md
@@ -0,0 +1,35 @@
+# Evidence Boundary Guide
+
+OpenAMP Foundry should state what each evidence artifact can and cannot support.
+
+This guide prevents a dry-lab result from being read as stronger than its review level.
+
+## Boundary note
+
+```markdown
+## Evidence boundary
+
+**Artifact:** Evidence certificate, benchmark report, shortlist, review packet, or model note.
+
+**Supports:** What the artifact can support.
+
+**Does not support:** What must not be inferred from it.
+
+**Required next review:** maintainer | evidence | quantitative | external.
+
+**Overread risk:** The most likely way someone could overread this artifact.
+
+**Status:** exploratory | reviewable | bounded | handoff-ready | returned evidence.
+```
+
+## Reviewer guidance
+
+Reviewers should ask for this note whenever an artifact could be read as stronger than it is.
+
+## Contributor guidance
+
+Contributors should write the boundary before writing the headline.
+
+## Acceptance test
+
+A boundary note is adequate when a reader can tell exactly what the artifact supports and what it does not support.