Skip to main content

GaryInParadise Knowledge Repository

This repository documents my experiences, knowledge, and connections as I explore different domains, pursue flow states, and engage with interesting people and ideas across various contexts.

Structure​

  • /docs/artifacts - Written works and documentation
    • /content-summaries (90 files) - Summaries and analyses of external content (interviews, videos, sermons)
    • /written-artifacts (343 files) - Original written works
      • /journal-entries (144 files) - Personal reflections, spiritual writings, letters
      • /strategic-documents (199 files) - Business proposals, event planning, strategic communications
  • /docs/relationships - Network of people I've met and our connections
  • /docs/transcripts - Raw transcripts of daily activities and conversations

CRITICAL: Relationships ↔ Transcripts System​

AI agents MUST read both /docs/relationships/README.md and review /docs/transcripts/ to understand the bidirectional linking system:

  1. Relationship files contain a ## Transcripts section that indexes all conversations with that person by transcript ID
  2. Transcript files contain related_people frontmatter that links back to relationship files
  3. When processing new transcripts → update the relevant relationship file's Transcripts table
  4. When reviewing a person → use their Transcripts table to find all relevant conversation context

This bidirectional connection ensures no conversation context is lost and all relationship history is discoverable from either direction.

  • /docs/one-liners.md - Collection of memorable quotes organized by themes

Mission​

To document my journey as I explore different domains, connect with interesting people, and pursue ideas that fascinate me. This repository serves as a personal knowledge base that helps me synthesize insights, track relationships, and develop concepts that could lead to meaningful impact.

Getting Started​

  1. Repository setup: Clone this repository to your local machine
  2. Templates: Review templates in each directory's README before creating new entries
  3. First transcript: Start by creating a simple transcript in /transcripts
  4. Process it: Follow the workflow below to convert the transcript into structured knowledge
  5. Review: Check all created/updated files for consistency and cross-references

Transcript Processing Workflow​

Communication Style​

When writing responses (texts, feedback, messages):

  • Formal grammar: Proper capitalization and punctuation, even in casual contexts
  • Economical language: Every word counts, no redundancy, shorter is usually better
  • Conversational but confident: Direct feedback with supportive undertones
  • Strategic emphasis: Use capitals for key words (THE, DEEPER, PLUS)
  • Casual elements: Use "rn" for "right now", contractions, arrows (→) for sequences
  • Service-oriented: Write with sense of service to the reader
  • No repetition: Each sentence should be unique and build forward

Notes:

  • It's "Christofuturist" - not "Christ-futurist" or "Christo-futurist"