From 906bba427bb2cc3a7c9dab08a642af5be3473c99 Mon Sep 17 00:00:00 2001
From: John Lancaster <32917998+jsl12@users.noreply.github.com>
Date: Sat, 20 Jun 2026 18:20:43 -0500
Subject: [PATCH] step 6 update

---
 .github/prompts/plan-step6.prompt.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/.github/prompts/plan-step6.prompt.md b/.github/prompts/plan-step6.prompt.md
index c991635..effe93a 100644
--- a/.github/prompts/plan-step6.prompt.md
+++ b/.github/prompts/plan-step6.prompt.md
@@ -23,6 +23,21 @@ Normative conclusions from those sources:
 3. Resources and tools must resolve to the same canonical authored markdown.
 4. Fallback behavior should keep context bounded and deterministic.
 
+### FastMCP Source Baseline (Authoritative References)
+
+Step 6 fallback behavior and compatibility-layer expectations align with:
+
+1. [FastMCP server concepts](https://gofastmcp.com/servers/server)
+2. [FastMCP resources and resource templates](https://gofastmcp.com/servers/resources)
+3. [FastMCP resources-as-tools transform](https://gofastmcp.com/servers/transforms/resources-as-tools)
+4. [MCP specification: resources](https://modelcontextprotocol.io/specification/latest/server/resources)
+
+Applied conclusions for this step:
+
+1. Resource contracts remain canonical and should be surfaced directly when clients support resource attachment.
+2. Tool-first compatibility layers should wrap canonical resource reads rather than creating alternate authored-content stores.
+3. URI-template-backed resource identity remains stable across direct-resource and tool-compatibility access paths.
+
 ### Discovery Priority Contract (Normative)
 
 Preferred sequence for skill discovery and loading: