Juan Castro

Juan Castro / Engineering notebook

Juan Castro

Builder / Engineer / Creator

I build useful software and the systems behind it, from product experiences and developer tools to dependable infrastructure.

Field study 00 / RevvySimulator-led telemetry is normalized, modeled into state, then composed for display; vehicle input remains future work.

Diagram routes and groups

Current simulator path

  1. Simulator telemetry
  2. Normalize
  3. State
  4. Compose
  5. Interface and display

Future source

  • Vehicle input (future integration)
Explore selected workAbout Juan

System study / 01

Hayabusa

SECURITY · DATA FLOW

Windows event data, carried through an inspectable local pipeline.

  1. Windows Event Logs
  2. PowerShell Exporter
  3. Vector
  4. NATS
  5. Go Ingestor
  6. ClickHouse
Queryable history

ClickHouse keeps event history close to SQL-driven detection work.

  1. ClickHouse
  2. SQL Rules
  3. Detections
  4. Alerts
Collection → transport → ClickHouse → SQL detectionRead the Hayabusa study

01 / Selected work

Systems made useful.

All projects
  1. 01 / FIELD NOTE

    Collectiv v2

    Collaborative music platform supporting sessions, contributions, notifications, profiles, royalty workflows, and mixer experiences.

    Read the study
    Study 01 / Collectiv v2Separate session workflow and media delivery paths, from contribution review to mixer handoff.

    Diagram routes and groups

    Session workflow

    1. Creator
    2. Session
    3. Contributions
    4. Review
    5. Finalize

    Media flow

    1. Upload
    2. Cloudflare R2
    3. Metadata
    4. Playback
    5. Mixer

    Ownership flow

    1. Contributors
    2. Split allocation
    3. Approval
    4. Final release
  2. 02 / FIELD NOTE

    Binder

    A local-first desktop control surface for understanding a collection of development projects.

    Read the study
    Study 02 / BinderLocal repository evidence feeds a curated control surface; GitHub remains optional enrichment.

    Diagram routes and groups

    Observed local state

    • Local repositories
    • Git, project metadata and roadmaps

    Binder-owned overrides

    • Authored project curation
    • Binder control surface

    Optional external enrichment

    • Public GitHub signals
    • Binder control surface

    Secondary observability

    • Project activity
    • Agent telemetry
  3. 03 / FIELD NOTE

    Conduit

    A small provider-neutral AI driver layer for TypeScript, Python, and Rust applications.

    Read the study
    Study 03 / ConduitOne provider contract branches to replaceable drivers and shared language bindings.

    Diagram routes and groups

    Provider-neutral request

    1. Application
    2. Conduit contract
    3. Provider driver

    Replaceable provider drivers

    • OpenAI-compatible
    • Ollama
    • Anthropic
    • Gemini

    Shared language bindings

    • TypeScript
    • Python
    • Rust
  4. 04 / FIELD NOTE

    Harpoon

    A Docker-compatible macOS runtime that runs Linux workloads without requiring Docker Desktop.

    Read the study
    Study 04 / HarpoonDocker context and host virtualization connect macOS to Linux and Docker Engine.

    Diagram routes and groups

    Host-to-guest boundary

    1. Docker CLI
    2. Host socket/API
    3. macOS runtime
    4. Virtualization.framework
    5. Linux VM
    6. Docker Engine
Employed · Full-Time

02 / Current state

On the workbench

Recent project activity is ordered by GitHub recency; private repositories may contribute without exposing their URLs.

Recently Active

  • ConduitA small provider-neutral AI driver layer for TypeScript, Python, and Rust applications.
  • BinderA local-first desktop control surface for understanding a collection of development projects.
  • LoomA local-first long-form writing environment where the manuscript remains sovereign while structure and context gather around it.

Learning Local-first architectures · Provider-neutral AI interfaces · Native virtualization on macOS

Recent public activity

More about now
Collectiv v2 / Session Workflow
  1. Creator
  2. Session
  3. Contributions
  4. Review
  5. Finalize
Hayabusa / Event Pipeline
  1. Windows Event Logs
  2. PowerShell Exporter
  3. Vector
  4. NATS
  5. Go Ingestor
  6. ClickHouse

03 / From the notebook

Writing

AI · 3 minBuilding Loom: The Manuscript Should Stay SovereignHow a repetitive writing workflow turned into Loom: a local-first writing environment built around manuscript sovereignty, structured context, and AI as a creative sounding board rather than an author.Read article