← Back to Chronicle

Development Philosophy

WHY LOCAL-FIRST // CARBYNE.EXE

Do It Once, Do It Right

This phrase drives every architectural decision. It emerged from pain—specifically, the pain of configuring .NET MCP servers for the fifth time after they broke on a new machine.

"If I have to fix this again, I'm rewriting it in Rust."
— The moment before everything changed

The .NET ecosystem is powerful. It's also dependency hell. Runtime versions, SDK mismatches, NuGet package conflicts, logging configuration pollution. Every deployment was a fresh debugging session.

Rust compiles to a single binary. No runtime. No dependencies. Copy the exe, run it. That's the philosophy: zero friction deployment.

Why Local-First?

The Practical Reason

Cloud services fail. APIs go down. Rate limits hit at the worst times. Local tools work offline, on planes, in basements, during outages. Reliability isn't a feature—it's the foundation.

The Strategic Reason

AI providers are tightening restrictions yearly. What's permitted today gets locked down tomorrow. Building on cloud-only infrastructure means building on sand.

Local-first means:

The Philosophical Reason

Digital sovereignty. The principle that you should control your own computing environment. Not rent it. Not request access. Own it.

Why Rust?

Consideration .NET Rust
Deployment Runtime required, SDK versions matter Single binary, copy and run
Memory GC pauses, higher baseline Zero-cost abstractions, minimal footprint
Startup JIT compilation, 2-3 second cold starts Native code, sub-second startup
Binary size 100MB+ with dependencies Sub-10MB typical
Learning curve Familiar, fast development Steep, but compounds over time

The learning curve is real. Rust's borrow checker is unforgiving. But once code compiles, it tends to just work. No null reference exceptions at runtime. No mystery crashes in production.

The investment pays dividends: Everything MCP went from 100MB+ .NET to 819KB Rust. Same functionality, 99% smaller.

The Bricklayer's Methodology

Borrowed from construction: systematic execution, no wasted motion. Each brick placed deliberately. Each tool serves a purpose.

Principles

Anti-Patterns

Portability as Feature

The 1TB VHDX isn't just storage. It's a complete environment:

VHDX Contents:
├── Tools/           # Compiled binaries, ready to run
├── PhiSHRI/         # Knowledge base, 600+ doors
├── Configs/         # MCP server configurations
├── Projects/        # Active development
├── Agents/          # Agent boot files, brain regions
└── Runtimes/        # Anything else needed
        

Plug this into any Windows machine. Mount. Run. Full capability restored in seconds.

No "setting up the development environment." No "installing prerequisites." The environment travels with you.

The Compound Effect

Every optimization compounds:

Small efficiencies don't add. They multiply. A 10% improvement across 10 tools isn't 100% better—it's compounding gains in every task that touches those tools.

"Premature optimization is the root of all evil. But mature optimization is the root of all speed."
— Adapted from Knuth
Local-First Rust Zero Dependencies Portability