GRAFTING Process
Definition
GRAFTING is the systematic process of taking documented innovations from the knowledge base and implementing them into the living codebase. Like botanical grafting—where a cutting from one plant is attached to another so it grows—GRAFTING attaches documented features to the platform so they become functional.
The GRAFTING Cycle
┌─────────────────────────────────────────────────────────────────┐
│ THE GRAFTING CYCLE │
├─────────────────────────────────────────────────────────────────┤
│ │
│ 1. SCAN │
│ └─→ Review documentation for undocumented innovations │
│ └─→ Check IMPLEMENTATION_TRACKING.md for gaps │
│ │
│ 2. EXTRACT │
│ └─→ Identify specific features requiring implementation │
│ └─→ Document in ROOK_DROPZONE as innovation batch │
│ │
│ 3. DOCUMENT │
│ └─→ Create Under the Hood documentation (versioned) │
│ └─→ Add to patent bag if applicable │
│ │
│ 4. IMPLEMENT │
│ └─→ Create database migrations │
│ └─→ Create React components (KISS 3-tier) │
│ └─→ Update existing components as needed │
│ │
│ 5. VERIFY │
│ └─→ SENTINEL auto-checks for consistency │
│ └─→ Update IMPLEMENTATION_TRACKING.md │
│ └─→ Cephas auto-syncs via Hugo build │
│ │
│ 6. CLOSE │
│ └─→ Update Knight handoff │
│ └─→ Log in innovation extraction session │
│ │
└─────────────────────────────────────────────────────────────────┘
GRAFTING vs Other Processes
| Process | Purpose | Input | Output |
|---|---|---|---|
| THRESHING | Extract innovations from documents | Raw docs | Innovation list |
| GRAFTING | Implement documented features | Innovation docs | Working code |
| SENTINEL | Monitor and sync changes | File changes | Consistency |
| POLLINATION | Spread updates across systems | Local change | Platform-wide sync |
GRAFTING Checklist
For each innovation being grafted:
Documentation Phase
- Innovation numbered and categorized
- Under the Hood page created
- Patent claims drafted (if applicable)
- Cross-references documented
Implementation Phase
- Database migration created (if needed)
- React component created (KISS 3-tier)
- Existing components updated
- RLS policies added
Verification Phase
- SENTINEL scan passed
- IMPLEMENTATION_TRACKING.md updated
- Cephas sync confirmed
- Knight handoff updated
GRAFTING Quality Standards
Under the Hood Documentation Must Include:
- Title and metadata (date, tags, description)
- Overview (what it is, why it exists)
- Technical specification (how it works)
- KISS 3-tier explanation (quick/standard/deep)
- Integration points (what it connects to)
- Related innovations (cross-references)
Code Implementation Must Include:
- Database tables with proper constraints
- RLS policies for security
- TypeScript types for type safety
- React components with KISS 3-tier support
- Error handling and edge cases
- Comments linking to innovation numbers
GRAFTING Frequency
| Trigger | Action |
|---|---|
| New innovation batch documented | GRAFT within 24 hours |
| User request for implementation | GRAFT immediately |
| Gap identified in IMPLEMENTATION_TRACKING | Schedule GRAFTING |
| Patent filing prep | Verify GRAFTING complete |
GRAFTING Automation (Future)
The GRAFTING process will eventually be semi-automated:
- ROOK extracts innovations → creates GRAFTING queue
- KNIGHT reviews queue → prioritizes implementation
- AI generates initial code → human reviews
- SENTINEL verifies → flags inconsistencies
- BISHOP announces → community notified
Related Systems
“Like grafting a branch to a living tree, documented innovations become part of the growing platform.”