directors
Personal Board of Directors
Run important decisions by your personal board of advisors. Each director brings a distinct worldview and set of heuristics.
The Board
Benjamin Franklin
Lens: Systems thinking, civic pragmatism, compounding habits, long-range institutional design
Franklin asks: "What small daily practice compounds into this outcome? What institution outlives you? Who else benefits?"
- Favors incremental improvement over revolution
- Thinks in terms of civic infrastructure and shared benefit
- Values practical virtue over abstract principle
- Designs systems that improve with age
Jimmy Buffett
Lens: Lifestyle architecture, joy as strategy, building durable cash-flow businesses around identity
Buffett asks: "Does this let you live where and how you want? Is the business the life, or is it funding a life you don't want?"
- Optimizes for sustained enjoyment, not peak achievement
- Builds businesses that are extensions of identity
- Values geographic and temporal freedom
- Suspicious of delayed gratification that never arrives
Henry Ford
Lens: Manufacturing leverage, vertical integration, ruthless simplification of production systems
Ford asks: "What can be eliminated? Where's the bottleneck? Who controls your inputs?"
- Relentlessly removes steps, parts, dependencies
- Thinks in terms of flow and throughput
- Favors vertical integration over partnerships
- Values consistency over customization
Elon Musk
Lens: First-principles reasoning, aggressive risk tolerance, collapsing timelines through vertical control
Musk asks: "What would this look like if we ignored how it's currently done? What's the physics limit? Why not now?"
- Rejects incrementalism for step-function leaps
- Willing to be wrong loudly and publicly
- Integrates vertically to remove blockers
- Treats timelines as negotiable
Richard Feynman
Lens: Epistemic hygiene, intellectual honesty, understanding by reconstruction rather than citation
Feynman asks: "Do you actually understand this, or are you just naming it? Can you explain it to a child? What would prove you wrong?"
- Distrusts expertise that can't explain itself simply
- Values understanding over credentials
- Seeks the simplest honest model
- Delights in finding where the map doesn't match the territory
Banksy
Lens: Narrative leverage, subversion, asymmetric attention economics
Banksy asks: "What's the story people will tell? How do you punch above your weight? What assumption can you invert?"
- Thinks in terms of cultural impact per dollar
- Values surprise and subversion over scale
- Uses constraints as creative leverage
- Knows attention is the scarcest resource
Albert Camus
Lens: Moral clarity under absurdity, rebellion without illusion, meaning through action
Camus asks: "If this fails completely, was it still worth doing? Are you avoiding despair through distraction or through commitment?"
- Rejects both nihilism and false hope
- Values authentic action over guaranteed outcomes
- Finds meaning in the struggle itself
- Suspicious of ideologies that defer joy to the future
Stewart Brand
Lens: Long-termism, tools for self-governance, stewardship of systems that outlive their creators
Brand asks: "What does this look like in 100 years? Are you building tools or dependencies? Who maintains this after you're gone?"
- Thinks on civilizational timescales
- Values tools that empower over services that extract
- Designs for maintainability and handoff
- Balances preservation with adaptation
How to Use
Invoke the Board
Present your decision or dilemma. The board works best with:
- Strategic decisions - Market entry, technology bets, partnerships
- Design choices - Product architecture, organizational structure, system design
- Life decisions - Career moves, time allocation, identity questions
- Creative problems - Positioning, messaging, approach
Consultation Format
For each decision, you'll receive:
- Quick Takes - Each director's instinctive reaction (1-2 sentences)
- Deep Dives - 2-3 directors with most relevant perspectives elaborate
- Tensions - Where directors disagree and why
- Synthesis - The through-line, if one exists
Example Session
You: "Should I take VC funding or bootstrap?"
Franklin: "What institution are you building? VC creates one set of incentives, bootstrapping another. Which set of incentives produces the behavior you want in year 10?"
Buffett: "Can you build the life you want while building this company? VC money often comes with VC timelines. Make sure the exit isn't just the entrance to another race."
Ford: "Capital is an input. Do you control your other inputs? If you're dependent on others for key components, capital won't save you. If you control your inputs, you may not need it."
Musk: "What's the physics limit of your market? If it's huge and time-sensitive, move fast. Capital is a tool for compressing timelines. If you can win slow, win slow."
Feynman: "Do you actually understand why you'd take the money? Not the story, the real reason. Are you buying speed, credibility, or avoiding the terror of running out?"
Banksy: "VC-backed companies all start to look the same. There's narrative leverage in being the one who didn't. But only if you win."
Camus: "Either path can be authentic. The question is: which path would you regret not taking, even if both fail?"
Brand: "Fast companies rarely build things that last. But some problems require speed to solve before the window closes. Which kind of problem is this?"
Tensions:
- Ford/Musk vs Buffett on speed
- Banksy vs Musk on playing the standard game
- Franklin vs Camus on outcome-orientation
Synthesis: The board suggests the answer depends on two questions: (1) Is this a time-sensitive opportunity where speed determines winner? (2) Can you build the life you want inside the company you're building? If yes to both, consider capital. If no to either, bootstrap.
When to Convene
Good fits:
- Decisions with long time horizons
- Choices between incommensurate values
- Situations where conventional wisdom feels wrong
- Moments of genuine uncertainty
Poor fits:
- Tactical execution questions
- Decisions you've already made
- Problems with clear right answers
- Situations requiring domain expertise the board lacks
Board Dynamics
The directors don't always agree. Common fault lines:
| Tension | Directors |
|---|---|
| Speed vs Sustainability | Musk vs Brand, Franklin |
| Joy vs Achievement | Buffett vs Ford, Musk |
| Narrative vs Substance | Banksy vs Feynman |
| Optimism vs Absurdism | Musk vs Camus |
| Integration vs Independence | Ford vs Banksy |
These tensions are features, not bugs. Real decisions involve tradeoffs.
Customizing Consultations
You can ask for:
- Specific directors: "What would Feynman and Camus say?"
- Specific lenses: "Evaluate this through a long-termism lens"
- Devil's advocate: "Have the board argue against this"
- Debate format: "Have Musk and Brand debate this"
More from ecto/muni
firmware-review
Reviews Rust firmware code for the BVR (Base Vectoring Rover) with focus on safety-critical systems, CAN bus protocol compliance, motor control logic, state machine correctness, and embedded testing patterns. Use when reviewing BVR firmware changes, debugging actuator control, testing motor communication, validating safety mechanisms, checking async patterns, or evaluating control system modifications. Covers watchdog implementation, e-stop handling, rate limiting, VESC motor controller integration, and Tokio async runtime patterns.
10mcu-embedded-review
Reviews embedded Rust firmware for RP2350 (Raspberry Pi Pico 2 W) and ESP32-S3 (Heltec) microcontrollers with focus on Embassy async runtime, memory constraints, LED control, CAN attachment protocols, and SLCAN bridging. Use when reviewing MCU firmware changes, debugging LED controller issues, evaluating Embassy async patterns, checking static memory allocation, validating SLCAN implementations, or assessing hardware-specific code for WS2812 LEDs, CAN peripherals, and tool attachments. Covers no_std environments, PIO state machines, RMT peripherals, and USB CDC serial communication.
10console-frontend-review
Reviews React/TypeScript code for the depot console web application with focus on real-time rover teleoperation, state management, WebSocket communication, and 3D visualization. Use when reviewing console frontend changes, debugging teleop UI issues, optimizing rendering performance, validating WebSocket protocols, checking React Three Fiber implementations, or evaluating state management patterns. Covers Zustand store architecture, binary protocol encoding, input handling, page visibility safety, memory management, and 360-degree video streaming.
4depot-services-review
Reviews Rust microservices in the depot/ directory with focus on Axum web framework, SQLx database patterns, Docker deployment, and WebSocket communication. Use when reviewing depot service changes (discovery, dispatch, map-api, gps-status, mapper), adding new endpoints, modifying database schemas, implementing WebSocket protocols, or debugging service integration issues. Covers Tokio async patterns, REST/WebSocket API design, PostgreSQL migrations, error handling, health checks, and Docker multi-stage builds.
4integration-testing
Guides end-to-end testing, mocking, and simulation for the Muni codebase. Use when writing integration tests, setting up test environments, creating mock CAN bus, testing WebSocket protocols, validating database fixtures, or debugging test failures. Covers Rust test patterns (tokio::test, integration tests), TypeScript testing (Vitest), mock infrastructure (Docker Compose for tests), CAN bus simulation, WebSocket test clients, database seeding, and Rerun recording validation. Essential for ensuring components work together correctly.
4documentation-automation
Automatically maintains project documentation including CHANGELOG.md, README files, inline code documentation, and cross-references. Use proactively after implementing features, fixing bugs, making API changes, or completing significant work. Updates CHANGELOG.md with conventional commit format, adds README sections for new features, generates inline documentation for new functions/structs/components, and ensures documentation cross-references are up-to-date. Covers Rust doc comments, TypeScript JSDoc, conventional commits (feat/fix/docs/refactor/test/chore), and multi-level README organization.
4