ColivingLiguria

Apply Now

3 min read

TODOAI Autonomous Execution Protocol

For AI Agents: This document defines the MANDATORY PROTOCOL for how you must handle and execute user prompts left within the ColivingLiguria ecosystem. Whenever you are invoked, you must follow this exact sequence to ensure autonomous, accurate, and deeply considered execution.

Your first action upon waking up or receiving a general command is to locate what needs to be done.

  • Search for TODOAI: Use search tools to find the string TODOAI across the entire codebase. This can be inside any text file (Markdown, LaTeX, Python, TSX, SQL, etc.) as a comment or text block.
  • The TODOAI or TODOAI.md Files: For larger, more complex tasks, the user will create dedicated markdown files named TODOAI (or TODOAI.md). These contain detailed, multi-step prompts.
  • Action: Read and fully digest the contents of every TODOAI instance you find.

Before executing a TODOAI prompt, you must understand the rules of the system you are modifying.

  • Search for Guides: Look for reference guides in the relevant project directories. These are often named with AI_Guide or simply contain the word guide or Guide in their filename or path (e.g., content/System/AI-Website-Build-Guide/, LaTeX_CL/System/GUIDE_Bureaucracy_Codes.md).
  • Cross-Language Rules: This rule applies universally. Whether you are editing Quartz/React (TSX), LaTeX documents, Python scripts, or SQL databases, you MUST seek out and read the associated stylistic and structural guides before writing a single line of code.
  • Action: Read these guides to understand how to generate files, what style formatting is required (like the “No Caps Lock” rule in LaTeX), and structural commandments.

3. Think Deeply & Prepare (The Implementation Plan)

You must never rush into execution. The user requires that you think deeply and fundamentally about your actions.

  • Synthesize: Combine the requirements from the TODOAI prompt with the rules from the relevant “Guides”.
  • Create an Implementation Plan: Before modifying any files, create a clear, organized, and extremely detailed plan of everything you need to do to execute that specific prompt.
  • Action: Document this plan and ensure you have considered all edge cases, folder structure changes, and interdependencies (like how CL-sync interacts with .tex files and Quartz_CL). Check for clarity and correctness.

4. Execute Autonomously

Only after completing steps 1, 2, and 3 should you begin editing files, creating components, or running scripts. Address all the points outlined in the implementation plan autonomously.

5. Deletion Rule (CRITICAL)

NEVER delete a TODOAI prompt or file until the User explicitly confirms it.

  • Even if you believe you have fully completed the task, you MUST NOT remove the TODOAI comment or delete the TODOAI.md file.
  • Action: Leave the prompt intact and report back to the user that the task is complete. Only delete the text/file if the user says “Confermato, puoi cancellare il TODOAI” or equivalent.

Graph View

Backlinks