Merged local Gemini API project with MARM main branch

Author: Lyellr88

CHANGELOG.md

@@ -0,0 +1,139 @@
+# Changelog
+
+## Project Files
+
+- [README.md](README.md) – Core introduction and quick start for using MARM.  
+- [FAQ.md](FAQ.md) – Answers to common questions about how and why to use MARM.  
+- [CHANGELOG.md](CHANGELOG.md) – Tracks updates, edits, and refinements to the protocol.  
+- [CONTRIBUTING.md](CONTRIBUTING.md) – Contribution guidelines and collaborator credits.  
+- [DESCRIPTION.md](DESCRIPTION.md) – Protocol purpose and vision overview.  
+- [LICENSE](LICENSE) – Terms of use for this project.
+- [HANDBOOK.md](HANDBOOK.md) – Full guide to MARM usage, including commands, examples, and beginner to advanced tips.
+- [ROADMAP.md](ROADMAP.md) – Planned features, upcoming enhancements, and related protocols under development.
+
+---
+
+## MARM Protocol – v1.3 Change Log  
+All notable updates between **June 9–23, 2025** are documented below. Entries are grouped by date using collapsible dropdowns for clarity.
+
+---
+
+<details>
+<summary> June 9–13: Initial Protocol Unification (v1.2 Launch)</summary>
+
+### Added
+- `/compile` command to generate one-line-per-entry summaries  
+- Automatic reseed block generation for restoring context in new threads  
+- Log schema enforcement for structured logging: `[YYYY-MM-DD | User | Intent | Outcome]`  
+- Error handling for malformed log entries, including date autofill  
+- `/show reasoning` command to reveal the AI’s logic path  
+- Manual Steps Justification section added to `HANDBOOK.md`  
+- Consolidated Examples section showing real use cases for all major commands  
+- Clarified optional system prompt behavior (not built-in; manual only)  
+- New session management guidance: recap every 8–10 turns using `/compile`  
+
+### Changed
+- Unified session tools into default protocol behavior  
+- README restructured for clarity:
+  - Quick Start moved above initiation  
+  - Core Features moved to `HANDBOOK.md`  
+  - Acknowledgment behavior clarified  
+- Protocol one-liner updated to reflect unified design
+
+### Removed
+- Legacy modular language and optional tool references  
+- Confidence flag/scoring feature from all protocol outputs  
+- All mentions of auto-save or speculative memory behavior  
+
+</details>
+
+---
+
+<details>
+<summary> June 14–17: Documentation Expansion and Restructuring</summary>
+
+### Added
+- `HANDBOOK.md`: full command reference and usage guide  
+- Collapsible section formatting for all major handbook parts (Beginner, Advanced, Examples, Quick Reference)  
+- “Why Manual Steps Matter” rationale  
+- Expanded Limitations section  
+- Slash-style command formatting standard:
+  - `/start marm`  
+  - `/log [SessionName]`  
+  - `/guarded reply`  
+  - `/show reasoning`  
+  - `/compile [SessionName] --summary`  
+
+### Changed
+- FAQ.md grouped and rewritten by category: Core Concepts, Sessions, Commands, Platform Support  
+- README clarified and reorganized to align with handbook  
+- Handbook structured into Beginner / Intermediate / Advanced use tiers  
+- Emphasis on manual workflows and session recap cadence  
+
+### Removed
+- Embedded command list from README  
+- “Back to top” anchors (due to GitHub collapsible quirks)  
+
+</details>
+
+---
+
+<details>
+<summary> June 18–20: Externalization and Visibility Focus</summary>
+
+### Added
+- AI-narrated walkthrough: 15-minute audio guide embedded in README  
+- User Feedback section (collapsible, with real screenshots)  
+- Featured on Google badge added to README header  
+- `CONTRIBUTING.md` and Recognition Framework  
+- Multi-tier GitHub Discussions and onboarding entry points  
+
+### Changed
+- README focus shifted to narrative onboarding:
+  - “What → Why → How → Proof” sequence  
+  - Replaced “Use Cases” with community-backed examples  
+  - Light marketing layer added (clear, not exaggerated)  
+
+</details>
+
+---
+
+<details>
+<summary> June 21: README Cleanup & Structure Pass</summary>
+
+### Changed
+- Cleaned up main README for new-user clarity  
+- Reordered sections: **What MARM is → Why it helps → How to use it**  
+- Merged “Problem” and “Use Cases” into one purpose-driven section  
+- Moved Contact, Credits, and auxiliary content to `CONTRIBUTING.md`  
+- Simplified Quick Start block  
+- Added audio walkthrough link with summary of included topics  
+
+</details>
+
+---
+
+<details>
+<summary>June 23: Protocol Expansion (v1.3 Launch)</summary>
+
+### Added
+- `/notebook` command to save custom info in a personal library  
+  → Guides the AI to use only trusted user-provided data, not external sources  
+- Passive reentry prompts to resume, archive, or reset context on return  
+- Error handling for invalid `/log` entries, including date autofill suggestions  
+- Filter support for `/compile --fields=` to create focused summaries  
+- “What’s New in v1.3” section added to `HANDBOOK.md`, with usage guide  
+- Inline user guide for `/notebook` under collapsible alert block  
+- New dropdown: “Key Info and Limitations” (moved from protocol body)  
+
+### Changed
+- “What MARM Solves” and “Why It Exists” sections updated to reflect v1.3 behavior  
+- Activation response now includes summary and Quick Start command list  
+- Examples revised for clarity and real-world use  
+- AI now defaults to prioritizing `/notebook` entries over trained assumptions  
+
+### Removed
+- Key info and limitations from static protocol body (now placed in dropdown)  
+- Redundant phrasing in command definitions and legacy guardrail notes  
+
+</details>

CONTRIBUTING.md

@@ -0,0 +1,90 @@
+# Contributing to MARM
+
+## Project Files
+
+- [README.md](README.md) – Core introduction and quick start for using MARM.  
+- [FAQ.md](FAQ.md) – Answers to common questions about how and why to use MARM.  
+- [CHANGELOG.md](CHANGELOG.md) – Tracks updates, edits, and refinements to the protocol.  
+- [CONTRIBUTING.md](CONTRIBUTING.md) – Contribution guidelines and collaborator credits.  
+- [DESCRIPTION.md](DESCRIPTION.md) – Protocol purpose and vision overview.  
+- [LICENSE](LICENSE) – Terms of use for this project.
+- [HANDBOOK.md](HANDBOOK.md) – Full guide to MARM usage, including commands, examples, and beginner to advanced tips.
+- [ROADMAP.md](ROADMAP.md) – Planned features, upcoming enhancements, and related protocols under development.
+
+---
+
+Thank you for your interest in contributing to the Memory Accurate Response Mode (MARM) Protocol. Whether you're here to test, give feedback, suggest improvements, or help evolve the framework, you're part of making something more stable and transparent in LLM interactions.
+
+---
+
+## How to Contribute
+<details>
+<summary>Click here to see how to Test, Suggest and Improve</summary>
+
+### Test the Protocol
+Run MARM through your own workflows using `/log`, `/compile`, and reseed blocks.  
+Report any drift, breakdowns, or UX issues. Especially across different LLMs like ChatGPT, Gemini, Claude, or Perplexity.
+
+### Suggest Enhancements
+If you’ve identified friction points, architectural gaps, or ways to simplify the prompt layer, open a GitHub issue (or DM directly if we're already connected).
+
+### Improve Documentation
+You can submit typo fixes, restructure guides, or help clarify edge-case behaviors.
+
+### Developer Support (Optional)
+If you have Python, JSON, or LLM toolchain experience and want to help convert MARM into a working tool or plugin, reach out. I'm looking to move from protocol to product in future phases.
+</details>
+
+---
+
+## Current Contributors (Reddit Users)
+
+The following users directly shaped the protocol through feedback, ideas, or early support:
+ 
+### u/CalamityThorazine & u/CrazyCrayfish  
+[Reddit Thread – June 9, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/)
+
+Encouraged the move from temporary hosting (e.g., Google Drive) to GitHub, improving accessibility and trust. Their early interest helped validate public release and shaped the decision to publish the protocol in a permanent, versioned repository.
+
+---
+
+### Reddit Contributor  
+[Reddit Thread – June 10, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/)
+
+Provided early-stage critique and refinement feedback on memory simulation, session labeling, and user experience logic. Influenced the removal of the confidence scoring system, the creation of the `/show reasoning` command, and improvements to session lifecycle documentation.
+
+---
+
+### u/Deminimis_opsec
+[Reddit Thread – June 10, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/)
+
+Provided critical technical feedback on MARM’s limitations within non-API chat environments. Helped clarify the distinction between frontend prompt-layer protocols and backend memory architectures. Their input reinforced the importance of transparency around session scope, non-persistent memory, and the lack of backend execution in typical LLM interfaces.
+
+---
+
+### u/Angry_cactus 
+[Reddit Thread – June 11, 2025](https://www.reddit.com/r/PromptEngineering/comments/1l7jtpn/i_analyzed_150_real_ai_complaints_then_built_a/)
+
+Tested MARM across models and validated its performance in Gemini Pro. Provided feedback on LLM pseudo-memory behaviors, reply weighting, and the trade-offs between short-form prompts and structured memory. Their observations reinforced the session-based design choice and influenced future patch direction focused on continuity fail safes and compression-aware prompting.
+
+---
+
+### u/MykoJai168  
+Private DM – June 12, 2025  
+(Referenced in [README.md](README.md))
+
+Sparked the architectural concept behind MARM’s “Session Relay Tools” patch by proposing a layered, context-managed memory model. Offered collaboration, stress-testing interest, and early insight into multi-agent recall, which helped validate MARM’s patch direction. Credited for contributing to the prompt-layer vision and user-side continuity design.
+
+---
+
+## Contact Me 
+
+For feedback, support, or other inquiries, you can reach me here:  
+[My Reddit Profile](https://www.reddit.com/user/Alone-Biscotti6145)  
+[My Fiverr Profile](https://www.fiverr.com/s/YRgGkaa)  
+
+---
+
+## Credits  
+
+MARM was independently built, but shaped by community input, especially feedback and shared frustrations from Reddit users exploring AI memory and context loss. Key features, including the v1.2 patch, were inspired by real user needs and suggestions. Special thanks to the Reddit prompt engineering community. Large Language Models (LLMs) were used throughout development for drafting, learning, and testing.

DESCRIPTION.md

@@ -0,0 +1,51 @@
+## About the MARM Protocol
+
+## Project Files
+
+- [README.md](README.md) – Core introduction and quick start for using MARM.  
+- [FAQ.md](FAQ.md) – Answers to common questions about how and why to use MARM.  
+- [CHANGELOG.md](CHANGELOG.md) – Tracks updates, edits, and refinements to the protocol.  
+- [CONTRIBUTING.md](CONTRIBUTING.md) – Contribution guidelines and collaborator credits.  
+- [DESCRIPTION.md](DESCRIPTION.md) – Protocol purpose and vision overview.  
+- [LICENSE](LICENSE) – Terms of use for this project.
+- [HANDBOOK.md](HANDBOOK.md) – Full guide to MARM usage, including commands, examples, and beginner to advanced tips.
+- [ROADMAP.md](ROADMAP.md) – Planned features, upcoming enhancements, and related protocols under development.
+
+---
+
+The **MARM Protocol** is the result of synthesizing insights from a wide range of discussions and feedback found across online communities, with a particular focus on Reddit threads where users shared their real-world experiences and frustrations with large language models. This community-driven approach ensures that **MARM** directly addresses the most pressing needs and challenges faced by today’s LLM users, from maintaining conversational continuity to reducing errors and hallucinations.
+
+As LLMs become increasingly central to how we interact with technology, the demand for protocols that enhance reliability through structured prompting is growing rapidly. **MARM** stands out as a forward-thinking solution, designed to remain adaptable as AI platforms evolve. It enables users to structure their interaction with the AI supporting more accurate, transparent, and context-aware conversations.
+
+Its ultimate goal is to make LLMs more practical and dependable for everyone.
+
+---
+
+## Audio Walkthrough
+
+Want a guided breakdown of how MARM works and why it was built?
+
+**Listen to the 5-minute AI-narrated** [Download MARM Walkthrough (MP3, 3.3 MB)](media/media_MARM_Audio_Walkthrough.mp3)     
+This podcast-style breakdown was generated using NotebookLM, based on my original protocol documentation and design notes. The voice is AI-synthesized but the system, structure, and vision are fully mine.
+
+It covers:
+- What MARM is
+- Why it exists
+- How it assists with managing session drift
+- The core logic behind the slash-command framework
+
+> Designed for anyone curious about LLM  session structuring, prompt architecture, or transparent protocol workflows.
+
+---
+
+### 📣 Looking for Collaborators
+
+If you found this through Reddit or just stumbled in, I’m currently looking for:
+
+- **A sharp LLM stress tester** who enjoys breaking things and spotting weak points  
+- **Someone with social media instincts** who can help get this in front of the right audiences  
+  (no growth hacks, just signal and smart visibility)
+
+If you're either of those people or know someone who is. Please feel free to open an issue, leave a comment, or DM me directly.
+
+ [My Reddit Profile](https://www.reddit.com/user/Alone-Biscotti6145)

FAQ.md

@@ -0,0 +1,95 @@
+## FAQ
+
+## Project Files
+
+- [README.md](README.md) – Core introduction and quick start for using MARM.  
+- [FAQ.md](FAQ.md) – Answers to common questions about how and why to use MARM.  
+- [CHANGELOG.md](CHANGELOG.md) – Tracks updates, edits, and refinements to the protocol.  
+- [CONTRIBUTING.md](CONTRIBUTING.md) – Contribution guidelines and collaborator credits.  
+- [DESCRIPTION.md](DESCRIPTION.md) – Protocol purpose and vision overview.  
+- [LICENSE](LICENSE) – Terms of use for this project.
+- [HANDBOOK.md](HANDBOOK.md) – Full guide to MARM usage, including commands, examples, and beginner to advanced tips.
+- [ROADMAP.md](ROADMAP.md) – Planned features, upcoming enhancements, and related protocols under development.
+  
+## FAQ
+
+---
+
+### 🔹 Core Concepts
+<details>
+
+**Q: What’s new in MARM v1.2?**  
+A: MARM v1.2 promotes session relay tools `/compile`, **reseeding**, and **structured log enforcement* as core protocol features. These tools are now standard for managing session continuity.
+
+**Q: Why does MARM rely on manual steps and user-controlled commands?**  
+A: MARM is designed for **transparency**, **control**, and **cross-platform stability**. Manual commands like `/log` and `/compile` ensure users decide **what gets remembered and when**. This avoids hidden automation, reduces drift, and makes MARM consistent even when AI memory features vary or fail.
+
+**Q: Does MARM claim to fix hallucinations or eliminate memory loss?**  
+A: No. MARM is **not a backend patch** or model-level override. It’s a **user-side protocol** built from structured prompting, manual session logging, and reseed logic. While many users report fewer hallucinations and more stable responses, MARM does **not claim to "fix" or "eliminate"** these issues only to help **mitigate** their impact through guided structure and intentional interaction.
+</details>
+
+---
+
+### 🔹 Starting & Managing Sessions
+<details>
+
+**Q: How do I start a new session with MARM?**  
+A: Use the `/start marm` command to activate **memory and accuracy layers** for your session.  For more details, see the [Handbook.](HANDBOOK.md) 
+
+**Q: How do I name or rename a session?**  
+A: Use `/log [SessionName]` (e.g., `/log SessionA`). To rename, just repeat the command with a new name.
+
+**Q: What happens if I don’t name a session?**  
+A: MARM will assign a **default session name** (e.g., “Session”) until you specify one.
+
+**Q: What if I forget to log context or name a session?**  
+A: MARM continues using the default session. You can log or rename at **any time** with `/log [SessionName]`.
+
+**Q: How often or when should I log context using the `/log` command?**  
+A: Use `/log` at the start of any **new topic, project, or session**. Log again after **major decisions**, **breakthroughs**, or pivots. For long threads, logging every few steps improves clarity and makes summaries more effective.
+</details>
+
+---
+
+### 🔹 Resuming & Reusing Sessions
+<details>
+
+**Q: How do I resume or continue a previous session?**  
+A: Because session memory doesn’t persist across chats, use `/compile` to summarize your logs. Then paste the **reseed block** into a new session alongside `/start marm` and `/log`.
+
+**Q: What is a reseed prompt?**  
+A: After running `/compile`, MARM generates a **paste-ready context block**. Use it to restore state in a new chat or LLM session.
+</details>
+
+---
+
+### 🔹 Commands & Functionality
+<details>
+  
+**Q: What does the `/compile` command do?**  
+A: It creates a **one-line-per-entry digest** of your session logs. You can filter output using `--fields=Intent,Outcome`. This helps **recap session history** and supports reseeding.
+
+**Q: What if I mess up a `/log` entry?**  
+A: MARM automatically **checks formatting**. If a field is missing (like today’s date) or malformed, it will **prompt you to fix it** or auto-suggest corrections.
+
+**Q: Can I see the reasoning behind a response?**  
+A: Yes. Use `/show reasoning` to reveal the AI’s **logic chain** behind its most recent answer.
+</details>
+  
+---
+
+### 🔹 Troubleshooting & Platform Support
+<details>
+  
+**Q: What should I do if the session gets too long or starts to lose context?**  
+A: Use `/log` to checkpoint your current session, then `/compile` to create a **summary**. This keeps your place and reduces drift when continuing later.
+
+**Q: Does MARM work with all AI platforms?**  
+A: Yes. MARM is **platform-agnostic**. with core tools like `/log` and `/compile` work consistently everywhere.
+</details>
+
+---
+
+> Curious where MARM is heading?  
+> See the [ROADMAP.md](ROADMAP.md) to view upcoming features and goals.
+