GM-RKB Protocol
A GM-RKB Protocol is a behavioral contract that defines a standardized operational procedure within the GM-RKB content enhancement system, ensuring consistency and repeatability across work sessions.
- AKA: RKB Operational Protocol, GM-RKB Standard Procedure, RKB Workflow Protocol.
- Context:
- It can specify multi-step workflows with defined trigger conditions and completion criteria.
- It can be documented in `config/PROTOCOLS.md` and executed by the AI assistant.
- It can include session protocols like "wake", "wind down", and "sign off" for session management.
- It can define error handling procedures and fallback mechanisms for robust operation.
- It can establish quality gates and validation checkpoints throughout the workflow.
- ...
- Example(s):
- Stub Enhancement Queue Protocol with three phases: check status, populate if needed, present candidates.
- Session Start Protocol executing `git pull`, `git status`, and `doc_sweep.py` in sequence.
- ZIP File Approval Protocol requiring explicit user confirmation before bulk processing.
- Level Up Documentation Protocol for systematic documentation improvements.
- Spring Clean Protocol for removing temporary files and cache cleanup.
- ...
- Counter-Example(s):
- An ad-hoc manual process without standardized steps.
- A code function that executes without human interaction.
- A configuration file that defines settings rather than procedures.
- See: Behavioral Contract, Operational Protocol, GM-RKB, GM-RKB Skill, GM-RKB Conceptual Commitment, Workflow Standardization.