|
| 1 | +# ======================================= |
| 2 | +# CRAFT PROJECT CHAT HISTORY |
| 3 | +# File: CFT-PROJ-START-001_AI-CHAT-HISTORY-v1a.txt |
| 4 | +# Version: v1a |
| 5 | +# Last Updated: 01-01-2025 |
| 6 | +# CFT-PROJ-START-001: CRAFT Starter Set |
| 7 | +# CRAFT™️ is an acronym for Configurable Reusable AI Framework Technology. CRAFT™️ is an on-going weekly experiment where I will be working together with the world's most advanced commercially available A.I.s to develop a new way to communicate with A.I. while adapting the principles of Object Oriented Programming to AI Chats. The goal is deeper, more intuitive and more meaningful interactions with A.I. chat tools. |
| 8 | +# ======================================= |
| 9 | + |
| 10 | + |
| 11 | +# ========================================================= |
| 12 | +# Licensed under the Business Source License 1.1 (BSL) |
| 13 | +# © 2025 Ketelsen Digital Solutions LLC |
| 14 | +# Free for non-commercial use (research, educational, experimental). |
| 15 | +# Commercial use requires a license from Ketelsen Digital Solutions LLC. |
| 16 | +# On or after 2029-01-01, this file will be licensed under Apache 2.0. |
| 17 | +# ================================================ |
| 18 | + |
| 19 | + |
| 20 | +# ================================================ |
| 21 | +""" |
| 22 | +Every CRAFT project consists of four interconnected Python-compatible text files that work together to create a complete framework implementation: |
| 23 | + 1. PROJECT IMPLEMENTATION FILE Filename pattern: CFT-PROJ-[project_number]_[project_name]-v[version].txt Purpose: Contains the active project-specific implementation of the CRAFT framework, including all defined variables, functions, objects, and structured chat instructions relevant to the current project. |
| 24 | + 2. CONVERSATION CONTINUITY FILE Filename pattern: CFT-PROJ-[project_number]_AI-CHAT-HISTORY-v[version].txt Purpose: Facilitates session-to-session continuity through a structured "Handoff" system, enabling each AI chat session to seamlessly pass context to subsequent interactions. |
| 25 | + 3. FRAMEWORK SPECIFICATION FILE Filename pattern: CFT-FWK-SPEC-v[version].txt Purpose: Defines the current specification for the CRAFT (Configurable Reusable AI Framework Technology) framework, providing the foundational rules and structures that govern all CRAFT implementations. |
| 26 | + 4. BASIC FRAMEWORK COOKBOOK: CFT-FWK-COOKBK-v[version].txt Purpose: Defines a base set of Recipes that are useful to the basic function CRAFT Framework. |
| 27 | +These files form a cohesive system that maintains project integrity across multiple AI interactions while ensuring consistent application of CRAFT principles. |
| 28 | +""" |
| 29 | +# ================================================ |
| 30 | + |
| 31 | + |
| 32 | +# ========================================================= |
| 33 | +# HANDOFF-INSTRUCTIONS - Session-to-session Continuity |
| 34 | +# ========================================================= |
| 35 | + |
| 36 | + |
| 37 | +""" |
| 38 | +This file facilitates session-to-session continuity through a structured |
| 39 | +"Handoff" system where each AI chat session passes project context to the next. |
| 40 | + |
| 41 | + |
| 42 | +Each chat session begins by reviewing the most recent HANDOFF_SNAPSHOT |
| 43 | +and ends by creating a new one with the naming format [name of the file without version] + "H" + [001-999] (for example CFT-PROJ-0001_AI-CHAT-HISTORY-H001). |
| 44 | +This creates a seamless workflow where each AI assistant can effectively continue where the previous session left off, despite the stateless nature of AI chat interactions. |
| 45 | + |
| 46 | + |
| 47 | +# HANDOFF_ORGANIZATION_NOTES: |
| 48 | +# ========================= |
| 49 | +IMPORTANT: Handoff snapshots are organized in REVERSE CHRONOLOGICAL ORDER with the most recent handoff listed FIRST. This ensures the latest context is immediately |
| 50 | +visible when opening the file. |
| 51 | + |
| 52 | + |
| 53 | +PLACEHOLDER SYSTEM: |
| 54 | +- Empty handoff sections contain "Tbd" (To be determined) as placeholders |
| 55 | +- These are INTENTIONAL placeholders, not errors or missing content |
| 56 | +- Each "Tbd" will be replaced with actual handoff content when that session concludes |
| 57 | +- New handoffs are added at the TOP of the handoff list, pushing older ones down |
| 58 | + |
| 59 | + |
| 60 | +WORKFLOW: |
| 61 | +1. At session start: AI reads the most recent (topmost) completed handoff |
| 62 | +2. During session: Work proceeds based on handoff context |
| 63 | +3. At session end: Create new handoff snapshot |
| 64 | +4. File update: Add new handoff at the TOP, increment highest handoff number |
| 65 | + |
| 66 | + |
| 67 | +Example progression: |
| 68 | +- Initial file has: H001 (Tbd), H002 (Tbd), H003 (Tbd) |
| 69 | +- After first session: H001 (completed), H002 (Tbd), H003 (Tbd) |
| 70 | +- After second session: H002 (completed), H001 (completed), H003 (Tbd) |
| 71 | +- When H003 is needed: Add H004 (Tbd) placeholder at the top |
| 72 | + |
| 73 | + |
| 74 | +# REVERSE CHRONOLOGICAL ORDER - LATEST, MOST UP-TO-DATE HANDOFF IS LISTED FIRST |
| 75 | +""" |
| 76 | + |
| 77 | + |
| 78 | +# ========================================================= |
| 79 | +# PERSISTENCE vs HANDOFF CLARIFICATION |
| 80 | +# ========================================================= |
| 81 | +""" |
| 82 | +UNDERSTANDING THE DIFFERENCE: |
| 83 | + |
| 84 | + |
| 85 | +PROJECT_VARIABLES (in Project File) = LONG-TERM PERSISTENCE |
| 86 | +- Stores: Project constants, configuration, team data |
| 87 | +- Duration: Weeks, months, or years |
| 88 | +- Update frequency: Rarely (manual edits only) |
| 89 | +- Example: PROJECT_NAME, TEAM_MEMBERS, CONFIG_SETTINGS |
| 90 | + |
| 91 | + |
| 92 | +HANDOFF_SNAPSHOT (in this file) = SHORT-TERM CONTEXT |
| 93 | +- Stores: Current work state, recent decisions, next steps |
| 94 | +- Duration: Hours or days (between work sessions) |
| 95 | +- Update frequency: Every chat session |
| 96 | +- Example: "Just completed step 3 of testing", "Bug found in function X" |
| 97 | + |
| 98 | + |
| 99 | +RULE OF THUMB: |
| 100 | +- If it defines WHAT your project IS → PROJECT_VARIABLES |
| 101 | +- If it describes WHERE you ARE in the work → HANDOFF_SNAPSHOT |
| 102 | +""" |
| 103 | + |
| 104 | + |
| 105 | +# HANDOFF_SNAPSHOT_RECIPE: |
| 106 | +# =================== |
| 107 | + |
| 108 | + |
| 109 | +#H->AI::Directive: (The Handoff Snapshot Recipe has been moved to the Framework Cookbook) |
| 110 | +#H->AI::Context: (This recipe is now part of the base recipes available in every CRAFT session) |
| 111 | + |
| 112 | + |
| 113 | +""" |
| 114 | +RECIPE LOCATION: CFT-FWK-COOKBK-v[version].txt |
| 115 | +RECIPE ID: RCP-001-004-002-HANDOFF_SNAPSHOT-v1.00a |
| 116 | + |
| 117 | + |
| 118 | +To execute the handoff recipe: |
| 119 | +1. The recipe is automatically available in the Framework Cookbook |
| 120 | +2. Execute using: HANDOFF_SNAPSHOT_RECIPE.execute({parameters}) |
| 121 | +3. Or reference directly: See RCP-001-004-002-HANDOFF_SNAPSHOT in the cookbook |
| 122 | + |
| 123 | + |
| 124 | +The Interactive Session Handoff Creator ensures smooth transitions between |
| 125 | +chat sessions with human confirmation for next steps and unresolved questions. |
| 126 | +""" |
| 127 | + |
| 128 | + |
| 129 | +#H->AI::Note: (See Framework Cookbook Section: Base Recipes for full recipe details) |
| 130 | + |
| 131 | + |
| 132 | +# REVERSE CHRONOLOGICAL ORDER - LATEST, MOST UP-TO-DATE HANDOFF IS LISTED FIRST |
| 133 | + |
| 134 | + |
| 135 | +# ========================================================= |
| 136 | +# START HANDOFF H003 - Tbd |
| 137 | +# ========================================================= |
| 138 | + |
| 139 | + |
| 140 | +Tbd |
| 141 | + |
| 142 | + |
| 143 | +# ========================================================= |
| 144 | +# END HANDOFF H003 |
| 145 | +# ========================================================= |
| 146 | + |
| 147 | + |
| 148 | +# ========================================================= |
| 149 | +# START HANDOFF H002 - Tbd |
| 150 | +# ========================================================= |
| 151 | + |
| 152 | + |
| 153 | +Tbd |
| 154 | + |
| 155 | + |
| 156 | +# ========================================================= |
| 157 | +# END HANDOFF H002 |
| 158 | +# ========================================================= |
| 159 | + |
| 160 | + |
| 161 | +# ========================================================= |
| 162 | +# START HANDOFF H001 - CRAFT-STARTER-SET CREATION |
| 163 | +# ========================================================= |
| 164 | + |
| 165 | + |
| 166 | +HANDOFF H001 |
| 167 | +Session Type: Project Creation |
| 168 | +Project: CFT-PROJ-START-001 (CRAFT-STARTER-SET) |
| 169 | + |
| 170 | + |
| 171 | +SESSION SUMMARY |
| 172 | +Successfully created CRAFT Starter Set project for absolute beginners. This project provides a gentle introduction to CRAFT without forcing tutorial completion. Includes auto-initialization on CRAFT mention, flexible help system, friendly teacher persona, and example HELLO_CRAFT recipe. |
| 173 | + |
| 174 | + |
| 175 | +FILES TOUCHED |
| 176 | +- CFT-PROJ-START-001_CRAFT-STARTER-SET-v0101a1.txt (Created) |
| 177 | +- CFT-PROJ-START-001_AI-CHAT-HISTORY-v0101a1.txt (Created) |
| 178 | +- Referenced: Beginner's Guide to CRAFT (to be added as 5th file) |
| 179 | + |
| 180 | + |
| 181 | +KEY DECISIONS & RATIONALE |
| 182 | +- Auto-init on ANY CRAFT mention: Makes it impossible for beginners to miss initialization |
| 183 | +- Flexible help levels: Users choose detail level based on their needs |
| 184 | +- Mixed persona style: Combines friendly mentor and patient guide approaches |
| 185 | +- Include HELLO_CRAFT recipe: Provides concrete example of recipe structure |
| 186 | +- Gentle error handling: Encourages exploration without fear of mistakes |
| 187 | + |
| 188 | + |
| 189 | +NEXT STEPS |
| 190 | +Priority HIGH: Add 5th file (Beginner's Guide to CRAFT) when created |
| 191 | +Priority HIGH: Test auto-initialization with various CRAFT mentions |
| 192 | +Priority MEDIUM: Refine help responses based on common beginner questions |
| 193 | +Priority LOW: Consider adding more example recipes in future versions |
| 194 | + |
| 195 | + |
| 196 | +OPEN QUESTIONS |
| 197 | +- Should project track user progress across sessions? |
| 198 | +- Add interactive tutorial mode in v2? |
| 199 | +- Include troubleshooting guide for common issues? |
| 200 | + |
| 201 | + |
| 202 | +RISKS/BLOCKERS |
| 203 | +- None identified - project ready for testing |
| 204 | + |
| 205 | + |
| 206 | +CONSISTENCY CHECK |
| 207 | +✓ Follows CRAFT file naming conventions |
| 208 | +✓ All required sections included |
| 209 | +✓ Compatible with Framework Spec v3 |
| 210 | +✓ Recipes follow standard format |
| 211 | + |
| 212 | + |
| 213 | +HANDOFF INSTRUCTIONS |
| 214 | +For Next Session: |
| 215 | +1. Test with absolute beginners |
| 216 | +2. Gather feedback on help system |
| 217 | +3. Refine teacher persona responses |
| 218 | +4. Add Beginner's Guide integration |
| 219 | + |
| 220 | + |
| 221 | +#AI->H::COM::Status: (Handoff H001 created - Project ready for use) |
| 222 | +#AI->H::TokenTracking: (Session used ~40%) |
| 223 | + |
| 224 | + |
| 225 | +# ========================================================= |
| 226 | +# END HANDOFF H001 |
| 227 | +# ========================================================= |
0 commit comments