Week 1 – Project Management & Final Project Ideation
September 3, 2025 | Assignment: Set up Git workflow, document system, and define final project
Final Project: Orbis
A tactile instrument for multi-scale reflection, inspired by horological precision and embodied cognition.
Origins: Designing AI for Human Flourishing
Orbis emerged from parallel work in MIT Media Lab's "Designing AI for Human Flourishing" course. The question: how do we design tools that slow down autopilot thinking and reveal hidden assumptions in decision-making?
"Technology should serve as a compass for deliberate thought, not just an autopilot for efficiency."
The concept crystallized around three interconnected instruments:
- Dial: Regulates how we think (focus mode: Self → Pair → Team → Organization → World)
- Compass: Clarifies what we think with (cognitive framework selector)
- Horizon: Expands what we think for (temporal and spatial scope)
Design Research & Precedents
1. Microsoft Surface Dial
Form factor reference: 98mm diameter × 58mm height, 320g weight
- Whole-hand grip interaction (palm on top, fingers wrapped)
- Haptic feedback via indexed rotation
- Context-aware tool selection
What Orbis adapts: Physical detents, rotary input, but smaller scale (68mm diameter) for desktop instrument feel
2. Horological Design Language
Design inspirations (not literal replication):
- Vacheron Constantin Patrimony / Overseas: Thin-case elegance, exposed movements revealing mechanism (transparency as design principle)
- Artisans de Genève custom Rolex Daytona: Skeletonized dials showing functional beauty, precision machining
- Traditional mechanical movements: Visible gear trains, jewel bearings, hand-finished components
Why these references matter: Orbis is not a watch—it's a tabletop reflection instrument. But horological design principles inform the aesthetic: precision, craftsmanship, timelessness, honesty of materials. A tool for deliberate thinking should feel like a lifetime object, not disposable tech.
Design constraint: Orbis must telegraph its purpose through form. The dial's detents, the visible encoder mechanism, the brass accents—each element is functional first, decorative second. This is anti-"black box" design.
Conceptual Design Iterations
Generated early visualizations using Midjourney to explore form language before committing to CAD. These aren't blueprints—they're design intent explorations.
Key design decisions emerging from these explorations:
- Bronze/brass accents for warmth (not cold aluminum or black plastic)
- Exposed mechanism visible through acrylic window (transparency = trustworthiness)
- Crown-style knob for tactile rotation (familiar interaction from watches)
- Walnut or oak base board (natural material grounds the object)
Technical Scope (HTMAA Implementation)
For this course, Orbis focuses on the Dial component—a standalone rotary interface with 5 detent positions.
Core Features
- Rotary encoder: Tracks angular position (5 modes: Self, Pair, Team, Org, World)
- Mechanical detents: Ball bearing + spring-loaded notched ring (tactile feedback)
- OLED display: 0.96" screen shows current mode + reflection prompt
- Embedded control: RP2040 microcontroller, I2C communication
- Fabrication mix: 3D printed housing, laser-cut base, milled PCB, turned brass components
Week-by-Week Build Plan
- Week 2: Laser-cut base board + vinyl graphics
- Week 3: Embed RP2040 + OLED on custom PCB
- Week 4: 3D print knob + mechanism housing
- Week 5: Integrate rotary encoder (input device)
- Week 6: Optional: Cast brass bezel (molding & casting)
- Week 7: CNC machine encoder plate + flywheel (if lathe access)
- Week 8+: Assembly, testing, iteration
Project Management Setup
Git Workflow
Repository structure established for weekly documentation:
htmaa2025/
├── index.html (homepage)
├── weeks/
│ ├── week01/index.html
│ ├── week02/index.html
│ └── ...
├── images/
│ ├── week1/
│ ├── week2/
│ └── ...
├── files/ (CAD, code, datasheets)
└── README.md
Commit strategy: One commit per week minimum, with descriptive messages. Tags for major milestones (e.g., v1.0-dial-prototype
).
Documentation Standards
- Process over perfection: Document failures, pivots, and iterations—not just successes
- Image captions matter: Every photo should answer "what am I looking at and why does it matter?"
- Design files downloadable: STLs, F3D, Gerbers—make work reproducible
- Reflections required: "What I learned" section for each week, written honestly
Why This Project?
I've attempted HTMAA three times (2022, 2023, 2024) and conflicts derailed me each year. This is my last realistic shot before leaving Boston in January 2026.
Orbis matters because it synthesizes everything I care about: deliberate design, embodied cognition, precision craft, and tools that respect human agency. It's also wildly ambitious for a beginner in fabrication—which means I'll learn more from near-failure than from safe success.
The adjacency with "Designing AI for Human Flourishing" isn't accidental. Both courses ask: How do we build things that make us more thoughtful, not just more efficient? Orbis is my answer—a physical artifact that makes reflection legible, deliberate, and scalable.
← Back to homepage |
Week 2 →