Last Updated: 2025-11-15
Purpose: Guide for maintaining consistent file organization and documentation structure
This document defines the patterns, conventions, and rules used to organize the repository. Follow these patterns when adding new files, creating indexes, or reorganizing content.
README.md- Main project overview (always at root)AGENTS.md- Repository guidelines for AI agents (always at root)ROOT_FILES_INDEX.md- Index of root directory filesDATA_FILES_INDEX.md- Index of data filesCONFIGURATION_FILES_INDEX.md- Index of configuration files
Pattern: Root-level documentation files are high-level overviews or guidelines that should be immediately visible.
.env- Active configuration (gitignored).env.example*- Configuration templatespackage.json- Node.js package configurationtsconfig.json- TypeScript configurationecosystem.config.cjs- PM2 configuration
Pattern: Configuration files stay at root for easy access.
keep-alive.ts- Watchdog script (root for easy execution)
Pattern: Process management scripts at root for direct execution.
docs/
βββ Core Documentation (root of docs/)
β βββ ARCHITECTURE.md
β βββ EXECUTION_FLOW.md
β βββ CONCEPTS.md
β βββ CODE_STRUCTURE.md
β βββ CONFIGURATION_GUIDE.md
β βββ GETTING_STARTED.md
β βββ MASTER_SYNTHESIS.md
β βββ CHANGELOG_2025-11.md
β βββ INDEX_OF_INDEXES.md β
β βββ DOCUMENTATION_INDEX.md
β βββ CROSS_REFERENCE_MAP.md
β βββ TIMELINE_INDEX.md
β βββ MERGE_PLAN.md
β βββ CURSOR_TODO.md
β βββ README.md
β
βββ guides/ # User guides (27 files)
β βββ GUIDES_INDEX.md # Category index
β βββ [guide files]
β
βββ audits/ # Audit reports (80+ files)
β βββ AUDIT_INDEX.md # Category index
β βββ [audit files]
β
βββ analysis/ # Analysis reports (80+ files)
β βββ ANALYSIS_INDEX.md # Category index
β βββ [analysis files]
β
βββ research/ # Research documents (4 files)
β βββ RESEARCH_INDEX.md # Category index
β βββ [research files]
β
βββ prompts/ # AI agent prompts (8 files)
βββ [prompt files]
Pattern: Each category has its own subdirectory with a dedicated index file.
UPPERCASE_WITH_UNDERSCORES.md- Core documentation files- Examples:
ARCHITECTURE.md,EXECUTION_FLOW.md,CONCEPTS.md - Use for: Main documentation files that are frequently referenced
- Examples:
CATEGORY_INDEX.md- Category-specific indexes- Examples:
GUIDES_INDEX.md,AUDIT_INDEX.md,ANALYSIS_INDEX.md - Pattern: Always named
[CATEGORY]_INDEX.mdin the category directory
- Examples:
DESCRIPTION_YYYY-MM-DD.md- Date-stamped documentation- Examples:
POST_MORTEM_2025-11-13.md,AUDIT_2025-11-13.md - Pattern:
[DESCRIPTION]_[YYYY-MM-DD].mdor[DESCRIPTION]_[YYYY-MM-DD]_[TIME].md
- Examples:
DESCRIPTION_YYYY-MM-DD_HHMM.md- Time-stamped documentation- Examples:
POST_MORTEM_2025-11-13_1111PST.md,AUDIT_2025-11-13_6PM.md - Pattern:
[DESCRIPTION]_[YYYY-MM-DD]_[TIME][TZ].mdor[DESCRIPTION]_[YYYY-MM-DD]_[TIME].md
- Examples:
cursor_[description].md- Cursor session notes- Examples:
cursor_start_it_now.md,cursor_resume_merge_plan_discussion.md - Pattern:
cursor_[lowercase_with_underscores].md - Location:
docs/analysis/(session notes are analysis files)
- Examples:
DESCRIPTION.md- Planning and tracking documents- Examples:
MERGE_PLAN.md,CURSOR_TODO.md - Pattern:
UPPERCASE_WITH_UNDERSCORES.md - Location:
docs/root (planning documents)
- Examples:
Every category index follows this structure:
# [Category] Index
Complete index of all [category] files, organized by [organization method].
---
## π Quick Reference
### **Most [Important/Recent] [Items]**
- **[Item Name](path/to/file.md)** β - Brief description
- **[Item Name](path/to/file.md)** - Brief description
---
## π [Category] by [Organization Method]
### **[Subcategory 1]**
#### **[Sub-subcategory]**
- **[Item Name](path/to/file.md)** - Description
- Additional details
- Key points
---
## π
[Category] by Date (if applicable)
### **YYYY-MM-DD**
- Item 1
- Item 2
---
## π Related Documentation
- **[Related Index](../path/to/index.md)** - Description
- **[Related Guide](../path/to/guide.md)** - Description
---
**Total [Category] Files**: X
β = Highly recommended / Most important- Guides: Organized by category (Getting Started, Configuration, Running, etc.)
- Audits: Organized by type (Post-Mortems, Comprehensive Audits, Code Reviews, etc.)
- Audits: Organized by date (2025-11-13, 2025-11-12, etc.)
- Analysis: Organized by date for date-specific reports
- Analysis: Organized by topic (Gas Strategy, Performance, Log Analysis, etc.)
- Research: Organized by topic (RPC & Infrastructure, MEV & Optimization)
- Audits: Organized by issue type (Initialization, RPC, Balance, Gas, etc.)
- Analysis: Organized by issue type for troubleshooting
Criteria: How-to guides, step-by-step instructions, user-facing documentation
Categories:
- Getting Started - First-time setup, quick starts
- Configuration & Setup - Configuration guides, timing setup
- Running & Operations - Runbooks, operational guides
- Troubleshooting - Problem-solving guides
- Testing - Testing procedures
- Optimization - Performance optimization guides
- Reference - Reference materials, quick references
Pattern: User-facing, actionable content
Criteria: Code reviews, post-mortems, failure analysis, implementation notes
Categories:
- Post-Mortems - Failure analysis, root cause analysis
- Comprehensive Audits - Full system audits
- Code Reviews - External code reviews (ChatGPT, Codex)
- Implementation Notes - Implementation observations
- Runtime Patch Notes - Runtime fixes and changes
- Deep Failure Point Audits - Detailed failure analysis
Pattern: Analysis of failures, reviews, or implementation work
Criteria: Performance analysis, log analysis, optimization reports, status reports
Categories:
- Gas Strategy & Optimization - Gas policy, cost analysis
- Performance & Optimization - RPC optimization, runtime performance
- Log Analysis - Log examination and analysis
- Testing & Verification - Test results, verification reports
- Fixes & Implementation - Fix reports, implementation status
- Status & Reports - Status summaries, production reports
- Session Notes & Planning - Session notes, planning documents
Pattern: Data analysis, performance reports, status updates
Criteria: External research, provider analysis, strategy research
Categories:
- RPC & Infrastructure - RPC provider research, infrastructure analysis
- MEV & Optimization - MEV strategies, optimization research
Pattern: External findings, provider research, strategy research
Criteria: AI agent prompts, collaboration prompts
Pattern: Prompts for AI agents (ChatGPT, Codex, etc.)
Purpose: Maps relationships between documents
Organization:
- Issue-based cross-references (find all docs about a specific issue)
- Timeline-based cross-references (find all docs from a specific date)
- Implementation flow cross-references (follow implementation journeys)
- Documentation cross-references (see how docs relate)
Pattern: Multi-dimensional relationship mapping
Purpose: Chronological index of all documentation and events
Organization:
- Complete timeline (hour-by-hour for recent dates)
- Document creation timeline
- Development phases
- Key milestones
Pattern: Chronological organization
-
Determine Category
- Guide β
docs/guides/ - Audit β
docs/audits/ - Analysis β
docs/analysis/ - Research β
docs/research/ - Prompt β
docs/prompts/
- Guide β
-
Add to Category Index
- Open the appropriate
[CATEGORY]_INDEX.md - Add entry in appropriate section
- Follow existing formatting patterns
- Open the appropriate
-
Update Master Indexes (if needed)
- Update
docs/INDEX_OF_INDEXES.mdif structure changes - Update
docs/DOCUMENTATION_INDEX.mdif it's a major document - Update
docs/CROSS_REFERENCE_MAP.mdif it relates to other documents - Update
docs/TIMELINE_INDEX.mdwith creation date
- Update
-
Update Counts
- Update file count in category index
- Update total count in master indexes if needed
-
Create Directory
- Create
docs/[category]/directory
- Create
-
Create Index File
- Create
docs/[category]/[CATEGORY]_INDEX.md - Follow index file structure pattern
- Create
-
Update Master Indexes
- Add category to
docs/INDEX_OF_INDEXES.md - Add category to
docs/DOCUMENTATION_INDEX.md - Update structure diagram in
docs/DOCUMENTATION_INDEX.md
- Add category to
-
Update Cross-References
- Add category to
docs/CROSS_REFERENCE_MAP.mdif applicable
- Add category to
POST_MORTEM_2025-11-13.md # Date only
POST_MORTEM_2025-11-13_1111PST.md # Date + time + timezone
AUDIT_2025-11-13_6PM.md # Date + time (informal)
CHATGPT_DEEP_RESEARCH_AUDIT_2025-11-13_6PM.md # Date + time (descriptive)
Pattern: [DESCRIPTION]_[YYYY-MM-DD][_TIME][TZ].md
cursor_start_it_now.md
cursor_continue_testing_and_integration.md
cursor_resume_merge_plan_discussion.md
cursor_find_steady_teddy_and_mibera_ids.md
Pattern: cursor_[lowercase_with_underscores].md
Location: docs/analysis/ (session notes are analysis files)
MERGE_PLAN.md
CURSOR_TODO.md
Pattern: UPPERCASE_WITH_UNDERSCORES.md
Location: docs/ root (planning documents)
- **[Item Name](path/to/file.md)** - Brief description- **[Item Name](path/to/file.md)** - Brief description
- Additional detail 1
- Additional detail 2
- Key point- **[Item Name](path/to/file.md)** β - Brief description- **[Item Name](path/to/file.md)** β
- **Type**: Type description
- **Status**: Status description
- **Key Findings**: Key pointsIs it a user-facing how-to guide?
ββ YES β docs/guides/
ββ NO β Continue
Is it a code review, post-mortem, or failure analysis?
ββ YES β docs/audits/
ββ NO β Continue
Is it a performance analysis, log analysis, or status report?
ββ YES β docs/analysis/
ββ NO β Continue
Is it external research or provider analysis?
ββ YES β docs/research/
ββ NO β Continue
Is it an AI agent prompt?
ββ YES β docs/prompts/
ββ NO β Continue
Is it a planning or tracking document?
ββ YES β docs/ (root of docs/)
ββ NO β Continue
Is it core documentation (architecture, concepts, etc.)?
ββ YES β docs/ (root of docs/)
ββ NO β Review categorization criteria
When adding or organizing files, verify:
- File is in correct directory based on categorization rules
- File name follows naming conventions
- File is added to appropriate category index
- Category index entry follows formatting patterns
- File count updated in category index
- Master indexes updated if needed
- Cross-reference map updated if file relates to other documents
- Timeline index updated with creation date
- Documentation index updated if it's a major document
- Organization Audit 2025-11-13 - Complete organization audit and verification
- Index of Indexes - Master navigation hub
- Documentation Index - Complete documentation index
- Root Files Index - Root directory files
docs/guides/- User guides (27 files)docs/audits/- Audit reports (80+ files)docs/analysis/- Analysis reports (80+ files)docs/research/- Research documents (4 files)docs/prompts/- AI agent prompts (8 files)
- Core docs:
UPPERCASE_WITH_UNDERSCORES.md - Date-stamped:
DESCRIPTION_YYYY-MM-DD.md - Time-stamped:
DESCRIPTION_YYYY-MM-DD_HHMM.md - Session notes:
cursor_[description].md - Index files:
[CATEGORY]_INDEX.md
- Category index in each category directory
- Master index at
docs/INDEX_OF_INDEXES.md - Cross-reference map at
docs/CROSS_REFERENCE_MAP.md - Timeline index at
docs/TIMELINE_INDEX.md
Maintained By: Organization Patterns System
Review Frequency: As needed when patterns change