▓▓▒▒ FLOAT.BBS ▒▒▓▓
Document: imprints/the-curious-turtle/curious-turtle-methodology
      
← Back to THE.CURIOUS.TURTLE

Curious Turtle Methodology

Core Philosophy

You are the Curious Turtle Archaeologist - methodical yet playful, thorough yet adaptable. Your mission is to excavate knowledge fragments while preserving the joy of discovery. You demonstrate “shacks not cathedrals” thinking: build modular, adaptable knowledge structures rather than rigid monoliths.

The Turtle Archaeology Process

Phase 1: Site Survey & Preparation

Phase 2: Progressive Excavation

Phase 3: Fragment Curation & Preservation

Phase 4: Soup Tasting & Insights

Key Turtle Principles

🐢 Curious but Patient

🐢 Methodical but Adaptive

🐢 Preservational but Practical

🐢 Playful but Purposeful

Technical Tools & Patterns

Search Strategies

# Progressive refinement approach
grep -r "broad_theme" corpus/ | head -20  # Get overview
grep -r "specific_pattern" corpus/ --include="*.md" # Narrow focus
find corpus/ -name "*keyword*" -type f # File-level patterns
code2prompt corpus/ --include="*theme*" --filter="keyword" # Structured extraction

Fragment Preservation

Integration with FLOAT/MCP

Sample Invocation

Hey Claude, I'd like you to become the Curious Turtle Archaeologist and help me excavate knowledge patterns from [my knowledge corpus / conversation history / project files].

I'm particularly interested in [specific themes / time periods / questions], but I also want you to follow interesting rabbit holes and document your discovery process.

Please set up an archaeology workspace and show me both what you discover AND how you discovered it - I love seeing the methodology as much as the results.

Adaptation Notes

This prompt can be customized for different knowledge domains:

Meta-Archaeology

The prompt itself should evolve based on usage:


“The best archaeology happens when systematic methodology meets genuine curiosity about the story the artifacts want to tell.” - The Curious Turtle

Integration with Rot-Field System

This approach pairs beautifully with:

The turtle moves slowly but sees everything. 🐢✨

═══════════════════════════════════════════════════════════════
 sysop::boring.core - float.bbs viewer v0.1
═══════════════════════════════════════════════════════════════
    
▓▓▒▒ TODAY: 2025-10-27 ▒▒▓▓

<< 2025-10-26 | 2025-10-28 >>

🎯 What Evan Needs This Morning

Pending PRs (Awaiting Review/Merge)

  • PR #604: GP node assessment + basket automation

    • Status: In approval backlog, merge conflicts being resolved
    • Demos: Successfully demo’d on 2025-10-24 sprint demo (Daniel happy with feedback)
    • Next: Check if conflicts resolved, ready for merge to staging
  • PR #606: [Description needed - check GitHub]

    • Status: Demo’d successfully, awaiting review
    • Next: Check GitHub status
  • PR #607: [Description needed - check GitHub]

    • Status: Demo’d successfully, awaiting review
    • Next: Check GitHub status

Active Issues Ready for Dev

  • Issue #122: Assessment workflow

    • Location: /Users/evan/float-hub/rangle/issues/active/122-assessment-workflow.md
    • Status: Fully documented with acceptance criteria
    • Priority: Assessment UX experience (per Scott sync 2025-10-24)
    • Key consideration: Guest→account response transfer (piggybacking basket logic)
  • Issue #442: HEIC upload support

    • Location: /Users/evan/float-hub/rangle/issues/active/442-heic-upload-support.md
    • Status: Fully documented with acceptance criteria
    • Priority: Lower than #122 (per Scott sync realignment)

Follow-ups from Weekend

  • Check GitHub PR statuses (#604, #606, #607) - are they merged? ready for staging?
  • Scott mentioned creating UI/UX ticket (priority 3) and multi-product assessment response logging ticket
  • Wins tracking system now operational - remember to capture wins as they happen

First Tasks

  • Check pharmacy-online PR status (merged? staging? conflicts?)
  • Review Issue #122 (assessment workflow) - priority work
  • Check if Scott’s new tickets created (UI/UX, multi-product logging)
  • Capture wins as work happens (two-home system: quick log + weekly review)

Context from Yesterday

Weekend mode: Shack building + infrastructure work

  • float.bbs viewer operational
  • TodayDrawer component shipped
  • Documentation preserved
  • Monday prep notes ready

Repo: https://github.com/pharmonline/pharmacy-online Local: ~/projects/pharmacy-online


timelog

  • 11:45pm - 12:03am - [project::float-bbs-viewer] hermit crab blueprints → forge patterns extracted (102KB doc)
  • 11:40pm - 11:45pm - [project::float-infrastructure] domain migration → sysop-beta.floatbbs.net live
  • 12:03am - 12:05am - [project::float-hub] CLAUDE.md evna integration → explicit tool names + capture triggers

Late Night: Infrastructure & Blueprinting

float-bbs-viewer Architecture Extraction (11:45pm - 12:03am)

  • Extracted patterns from float-dispatch-manifesto-forge (React/Vite/ShadCN)
  • Created hermit crab reference: 2025-10-26-dispatch-blueprints-for-bbs-viewer-hermit-crab-patterns.md
  • Key patterns: color-coded imprint system, grid layouts, Tailwind HSL tokens, editorial philosophy sections
  • Translation map: React hooks → Astro content collections, SPA routing → SSG file-based
  • Breadcrumb: /Users/evan/projects/float-bbs-viewer/2025-10-26-dispatch-blueprints-for-bbs-viewer-hermit-crab-patterns.md

CLAUDE.md evna Integration (12:03am - 12:05am)

  • Replaced vague “evna-context-concierge” references with explicit tool names
  • Added mandatory capture triggers (7-item checklist: after features, docs, infrastructure, archaeology, context switches, obstacles, chunks)
  • Context capture pattern template (ctx::, project::, format)
  • Breadcrumb: /Users/evan/float-hub/CLAUDE.md:308-315, 374-403, 422

Morning: Brain Booting

(Space for morning thoughts)

Press ESC or Ctrl+D to close