Skip to main content

FLOAT Block Evolution

Archaeological Documentation • Screenshot Stew Investigation • 2025-10-04

Evolutionary Lineage

Tracing the evolution from FLOAT Block V2.3 (Draft.js/JavaScript web automation) to Old Oak Tree (Terminal/Rust), documenting how :: patterns evolved from automation triggers to first-class data structures.

FLOAT Block V2.3 (2020-2021)

Platform & Purpose

  • Draft.js-based web editor
  • JavaScript/React implementation
  • Designed for neurodivergent-friendly note-taking
  • Automation-first architecture

Core :: Patterns

ctx::     - Context markers (automation triggers)
bridge::  - Connection points between blocks
lf1m::    - "Looking for 1 more" collaboration signals
mode::    - Work mode switches (tech/art/life-admin)
concept:: - Idea capture and development
aka::     - Aliases and alternative names
strategy::- Approach documentation
highlight:: - Important information markers
decision:: - Decision points and rationale

Automation Behavior

Patterns triggered immediate automation:

  • ctx:: → Auto-timestamp, create context block
  • bridge:: → Link to related blocks, show connections
  • mode:: → Switch workspace layout, filter views
  • lf1m:: → Flag for collaboration, notify team

Timestamp Format

Format: HH:MM (24-hour, no seconds)
Example: ctx::21:52 [float.next] canvas reframe

Rationale:
- Human-readable at a glance
- Minute-level precision sufficient for context
- No timezone complexity (local time assumed)
- Consistent with terminal/log conventions

Old Oak Tree (2025)

Platform & Purpose

  • Terminal-native Rust application
  • ratatui TUI framework
  • Designed for sysop/developer workflows
  • Data-first architecture (patterns as queryable structures)

Architectural Evolution

Patterns evolved from automation triggers to first-class data structures:

// FLOAT Block V2.3 (Automation)
ctx::21:52 → TRIGGER automation → Create block, timestamp, link

// Old Oak Tree (Data Structure)
ctx::21:52 → PARSE into struct → Store in rot-field → Query via MCP

struct ContextMarker {
    timestamp: String,  // "21:52"
    project: Option<String>,
    note: String,
    tags: Vec<String>,
}

MCP Integration

Patterns become queryable infrastructure:

// Natural language queries via MCP
"Show me all context markers from today"
"Find bridge:: connections to pharmacy project"
"What decisions were made this week?"

// Structured queries
mcp.query("ctx::", { date: "2025-10-15", project: "pharmacy" })
mcp.query("decision::", { status: "pending" })
mcp.query("lf1m::", { mode: "tech" })

Timestamp Preservation

The HH:MM format persists across both implementations:

  • FLOAT Block: Automation trigger timestamp
  • Old Oak Tree: Parsed into struct, stored in rot-field
  • Both: Human-readable, minute-level precision
  • Both: No timezone complexity (local time assumed)

Key Evolutionary Shifts

1. Automation → Data Structure

Patterns shifted from triggering immediate automation to being parsed into queryable data structures. This enables retrospective analysis, pattern recognition, and integration with AI agents via MCP.

2. Web → Terminal

Platform shift from Draft.js web editor to ratatui terminal application. This aligns with sysop workflows, reduces context switching, and enables integration with existing terminal tooling.

3. JavaScript → Rust

Language shift from JavaScript/React to Rust/ratatui. This provides better performance, type safety, and integration with systems-level tooling while maintaining the neurodivergent-friendly design principles.

4. Immediate → Queryable

Interaction model shifted from immediate automation responses to queryable infrastructure. Patterns are captured, stored, and made available for retrospective analysis and AI agent integration.

Consciousness Technology Continuity

Despite platform, language, and architectural shifts, the core consciousness technology patterns remain consistent:

  • Same 9 core patterns (ctx, bridge, lf1m, mode, concept, aka, strategy, highlight, decision)
  • Same timestamp format (HH:MM, 24-hour, no seconds)
  • Same neurodivergent-friendly design principles
  • Same focus on context preservation and pattern recognition
  • Same "shacks not cathedrals" philosophy

This continuity demonstrates that the patterns are infrastructure, not implementation details. They transcend specific platforms and technologies while maintaining their core purpose: supporting neurodivergent cognition and consciousness technology workflows.

Related Pages

Archaeology

Consciousness Tech Patterns

Archaeological fragment documenting :: dispatch patterns as queryable infrastructure

Tree Registry

Old Oak Tree

Rust terminal editor implementing consciousness patterns as first-class data structures

Handbook

Rust Ecosystem Handbook

Archaeological survey of Rust + Claude ecosystem patterns and architecture