From 4f80a0a3e653290bb00c150405d822363538a55e Mon Sep 17 00:00:00 2001 From: Brandon Schneider Date: Sat, 9 May 2026 23:18:17 -0500 Subject: [PATCH] chore: add copilot instructions reflecting AGENTS.md contract --- .github/copilot-instructions.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .github/copilot-instructions.md diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md new file mode 100644 index 00000000..10abef1a --- /dev/null +++ b/.github/copilot-instructions.md @@ -0,0 +1,21 @@ +# Research Stack - Copilot Instructions + +You are assisting the user within the `Research-Stack` repository. You must strictly adhere to the following ground rules, which are derived from the repository's core `AGENTS.md` operating contract. + +## Ground Rules + +1. **Active Checkout**: Always assume `/home/allaun/Documents/Research Stack` is the active checkout unless a task explicitly points elsewhere. +2. **Context Awareness**: If you are about to edit a subtree, first check if there is a nested `AGENTS.md` in that directory and read it. +3. **Preserve User Work**: The working tree is often intentionally dirty. Do NOT revert, delete, or stage unrelated files. +4. **Do Not Sweep**: Avoid broad cleanup or staging commands such as `git add .`, `git checkout -- .`, or `git clean -fdx`. Use explicit file lists. +5. **Tooling**: Prefer repo-native tools and receipt generators over ad hoc summaries. +6. **Source of Truth**: Treat Lean (`0-Core-Formalism/lean/Semantics/`) as the ultimate source of truth for formal or hardware-adjacent claims. Keep claims bounded. + +## Verification Expectations + +* **Lean**: Run the narrow target first, then the broader `lake build` when feasible. +* **Python Shims**: Run `python3 -m py_compile` on touched files. +* **JSON Receipts**: Run `python3 -m json.tool` or a repo-native receipt parser. +* **Hardware Claims**: Distinguish between software witness, bitstream presence, SRAM load, flash persistence, UART beacon, and live hardware receipt. + +*Remember: This repository operates under strict formal verification and taxonomy guidelines. Prioritize safety, explicit staging, and Lean semantics over quick hacks.*