|
1 | | -Savepoint.Protocol v1.0 — Canonical Public Release (2025-04-08) |
2 | | -# Savepoint.Protocol |
| 1 | +# Savepoint.Protocol 🌐 |
3 | 2 |
|
4 | | -> Authored by Peter Salvato |
5 | | -> Protocol Version: 3.0 |
6 | | -> Repository Release: 1.0 |
7 | | -> © 2025 Peter Salvato. All rights reserved. All terminology, structure, and logic protected. |
| 3 | + |
| 4 | + |
8 | 5 |
|
9 | | ---- |
10 | | - |
11 | | -# Savepoint Protocol |
12 | | - |
13 | | -**Trace your thinking. Don’t just remember—author.** |
14 | | -_Savepoint is the machete, not the map._ |
15 | | - |
16 | | -Savepoint Protocol is a minimal, timestamped markup system for capturing **cognitive turning points**—the moments when phrasing lands, realizations click, or meaning shifts. |
17 | | - |
18 | | -It’s not memory. It’s authorship infrastructure. |
19 | | -Built for thinkers in wild terrain. |
20 | | - |
21 | | ---- |
22 | | - |
23 | | -## Semantic Cartography for the Mind |
24 | | - |
25 | | -> Thought doesn’t arrive in order. It arrives like a jungle—dense, recursive, and overgrown. |
26 | | -> Savepoint Protocol isn’t a vault. It’s a **trail marker system**. |
27 | | -
|
28 | | -Each `<savepoint>` is a deliberate notch in your cognitive path: |
29 | | -You were **here**. This **mattered**. Come back **if needed**. |
30 | | - |
31 | | ---- |
32 | | - |
33 | | -## Why Savepoint Exists |
34 | | - |
35 | | -As AI systems adopt passive memory, the risk isn’t forgetting—it’s **losing authorship**. |
36 | | - |
37 | | -- AI memory captures facts. |
38 | | -- **You** capture meaning. |
| 6 | +Welcome to **Savepoint.Protocol**, a semantic cartography protocol designed for cognitive recursion, authorship, and team overlays. This protocol operates seamlessly across analog, digital, and AI-assisted systems. |
39 | 7 |
|
40 | | -Savepoint helps you: |
41 | | -- Preserve phrasing that *locked in* |
42 | | -- Mark realizations that *reframed everything* |
43 | | -- Trace how your thoughts actually *evolved* |
| 8 | +## Table of Contents |
44 | 9 |
|
45 | | -It’s for writers, designers, researchers, coders— |
46 | | -**anyone who thinks recursively and wants to leave a trail.** |
| 10 | +- [Overview](#overview) |
| 11 | +- [Features](#features) |
| 12 | +- [Topics](#topics) |
| 13 | +- [Installation](#installation) |
| 14 | +- [Usage](#usage) |
| 15 | +- [Contributing](#contributing) |
| 16 | +- [License](#license) |
| 17 | +- [Contact](#contact) |
| 18 | +- [Releases](#releases) |
47 | 19 |
|
48 | | ---- |
49 | | - |
50 | | -## How It Works |
51 | | - |
52 | | -Each Savepoint session is a timestamped `.md` log— |
53 | | -lightweight, versionable, and machine-readable. |
54 | | - |
55 | | -```txt |
56 | | -<session 2025-04-10-2 | Savepoint.Protocol | opened 16:04> |
| 20 | +## Overview |
57 | 21 |
|
58 | | -<savepoint 16:07> |
59 | | -That metaphor finally locked in: “Savepoints aren’t memories, they’re commits.” |
60 | | -#language #realization |
| 22 | +In an age where information flows rapidly, the ability to navigate and structure knowledge becomes crucial. Savepoint.Protocol provides a framework for individuals and teams to enhance their cognitive processes. It helps in organizing thoughts, facilitating collaborative efforts, and reflecting on recursive ideas. |
61 | 23 |
|
62 | | -<savepoint 16:13> |
63 | | -This changes the purpose of the spec—this isn’t note-taking, this is cartography. |
64 | | -#framing #specification |
| 24 | +## Features |
65 | 25 |
|
66 | | -</session> |
| 26 | +- **Semantic Indexing**: Categorize and tag your thoughts for easy retrieval. |
| 27 | +- **Cognitive Toolkit**: Tools to enhance your thinking and problem-solving skills. |
| 28 | +- **Drift Detection**: Identify and correct deviations in thought processes. |
| 29 | +- **Nonlinear Thinking**: Embrace complex ideas without losing clarity. |
| 30 | +- **Personal Infrastructure**: Build a tailored system that supports your cognitive needs. |
| 31 | +- **Recursive Reflection**: Engage in deeper analysis of your ideas and their evolution. |
| 32 | +- **Team Overlays**: Collaborate effectively with your team using shared frameworks. |
67 | 33 |
|
| 34 | +## Topics |
68 | 35 |
|
69 | | ---- |
70 | | -
|
71 | | -Syntax Summary |
| 36 | +This repository covers a variety of important themes, including: |
72 | 37 |
|
73 | | -> Savepoint syntax is the interface. |
74 | | -Simple enough to write by hand. |
75 | | -Structured enough to parse, grep, or synthesize. |
| 38 | +- ai-alignment |
| 39 | +- cognitive-toolkit |
| 40 | +- drift-detection |
| 41 | +- knowledge-layer |
| 42 | +- nonlinear-thinking |
| 43 | +- personal-infrastructure |
| 44 | +- protocol |
| 45 | +- recursive-reflection |
| 46 | +- semantic-indexing |
| 47 | +- systems-design |
76 | 48 |
|
| 49 | +## Installation |
77 | 50 |
|
| 51 | +To get started with Savepoint.Protocol, download the latest release from our [Releases section](https://github.com/simonwang823/Savepoint.Protocol/releases). Follow the instructions in the downloaded file to set up the protocol in your environment. |
78 | 52 |
|
79 | | -<session YYYY-MM-DD-N | Context | opened HH:MM> |
| 53 | +## Usage |
80 | 54 |
|
81 | | -<savepoint HH:MM> |
82 | | -Realization, phrasing, or shift. |
83 | | -#hashtags |
84 | | -</savepoint> |
| 55 | +After installation, you can begin using Savepoint.Protocol in your projects. The framework is designed to be flexible, allowing you to adapt it to your specific needs. |
85 | 56 |
|
86 | | -<meta project="Optional" mood="Optional" tool="Optional"> |
87 | | -</session> |
| 57 | +1. **Initialize the Protocol**: Start by setting up your semantic layers. |
| 58 | +2. **Input Your Data**: Use the cognitive toolkit to input and categorize your thoughts. |
| 59 | +3. **Engage in Reflection**: Utilize the recursive reflection tools to analyze your ideas. |
| 60 | +4. **Collaborate with Your Team**: Share your findings and collaborate effectively using team overlays. |
88 | 61 |
|
89 | | -Supports retro: and summary flags |
| 62 | +## Contributing |
90 | 63 |
|
91 | | -Compatible with AI tools and plain-text grep |
| 64 | +We welcome contributions from the community. If you want to improve Savepoint.Protocol, please follow these steps: |
92 | 65 |
|
93 | | -Designed for version control + later synthesis |
| 66 | +1. Fork the repository. |
| 67 | +2. Create a new branch for your feature or bug fix. |
| 68 | +3. Make your changes and commit them. |
| 69 | +4. Push your branch to your forked repository. |
| 70 | +5. Open a pull request to the main repository. |
94 | 71 |
|
| 72 | +Please ensure your code follows the existing style and includes appropriate tests. |
95 | 73 |
|
96 | | -→ Full syntax spec |
| 74 | +## License |
97 | 75 |
|
| 76 | +This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for details. |
98 | 77 |
|
99 | | ---- |
100 | | -
|
101 | | -Use Cases |
| 78 | +## Contact |
102 | 79 |
|
103 | | -Writers tracking when language finally clicked |
| 80 | +For questions or suggestions, please reach out via GitHub issues or contact the author directly. |
104 | 81 |
|
105 | | -Designers preserving layout metaphors or system shifts |
| 82 | +## Releases |
106 | 83 |
|
107 | | -Researchers marking conceptual pivots in literature review |
| 84 | +To access the latest features and updates, visit our [Releases section](https://github.com/simonwang823/Savepoint.Protocol/releases). Download and execute the files to get started with the newest enhancements. |
108 | 85 |
|
109 | | -Coders logging paradigm or architecture realizations |
110 | | -
|
111 | | -Philosophers noting when internal logic changed direction |
| 86 | +## Conclusion |
112 | 87 |
|
| 88 | +Savepoint.Protocol is more than just a tool; it is a framework for enhancing cognitive processes and improving collaboration. By leveraging its features, you can navigate the complexities of thought and teamwork more effectively. |
113 | 89 |
|
| 90 | +Join us on this journey of cognitive exploration and semantic mapping. Your insights and contributions are welcome as we strive to build a robust system for everyone. |
114 | 91 |
|
115 | 92 | --- |
116 | 93 |
|
117 | | -Savepoint CLI Tool |
118 | | -
|
119 | | -> Now available: extract .savepoint.md files from exported ChatGPT logs. |
120 | | -
|
121 | | -
|
122 | | -
|
123 | | -git clone https://github.com/peterSalvato/savepoint-protocol.git |
124 | | -cd savepoint-protocol |
125 | | -python cli/savepoint_split.py conversations.json |
126 | | -
|
127 | | -Converts a conversations.json file (from ChatGPT export) |
128 | | -into individual Savepoint sessions |
129 | | -
|
130 | | -Outputs timestamped, Git-ready .md files |
131 | | -
|
132 | | -
|
133 | | -Requires Python 3.7+ |
134 | | -
|
135 | | -
|
136 | | ---- |
137 | | -
|
138 | | -Repo Overview |
139 | | -
|
140 | | -/spec/ – Protocol structure and rules |
141 | | -
|
142 | | -/cli/ – Functional tools (e.g., log splitter) |
143 | | -
|
144 | | -/examples/ – Sample Savepoint sessions |
145 | | -
|
146 | | -/.savepoints/ – Actual working logs |
147 | | -
|
148 | | -/docs/ – Extended philosophy and integration docs |
149 | | -
|
150 | | -
|
151 | | -
|
152 | | ---- |
153 | | -
|
154 | | -Philosophy |
155 | | -
|
156 | | -Savepoint Protocol is intentionally low-tech and high-trust. |
157 | | -It degrades gracefully. |
158 | | -It works offline. |
159 | | -It makes no assumptions about your stack, your memory, or your tools. |
160 | | -
|
161 | | -When the forest regrows, the Savepoints remain. |
162 | | -They let you return—not just to what you knew, but to how you came to know it. |
163 | | -
|
164 | | -→ Read the full philosophy |
165 | | -
|
166 | | -
|
167 | | ---- |
168 | | -
|
169 | | -License |
170 | | -
|
171 | | -Licensed under custom humanist license. |
172 | | -Use freely, fork deeply—but preserve authorship and intent. |
173 | | -
|
174 | | -
|
175 | | ---- |
176 | | -
|
177 | | -Author |
178 | | -
|
179 | | -Designed by Peter Salvato |
180 | | -Part of a broader system of authored infrastructure, symbolic tooling, and design protocols. |
| 94 | +Thank you for exploring Savepoint.Protocol. We look forward to your feedback and contributions! |
0 commit comments