← Back to Home

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.

Early Orbis dial sketch with annotations Detailed technical sketch of Orbis mechanism

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:

How Orbis components interconnect Why Orbis matters for decision-making

Design Research & Precedents

1. Microsoft Surface Dial

Form factor reference: 98mm diameter × 58mm height, 320g weight

What Orbis adapts: Physical detents, rotary input, but smaller scale (68mm diameter) for desktop instrument feel

2. Horological Design Language

Exposed watch movement mechanism Rolex Daytona chronograph with green dial Vacheron Constantin Overseas skeleton watch

Design inspirations (not literal replication):

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.

Midjourney render: top-down view of Orbis dial Midjourney render: isometric view showing mechanism Midjourney render: side view with crown detail

Key design decisions emerging from these explorations:

Technical Scope (HTMAA Implementation)

For this course, Orbis focuses on the Dial component—a standalone rotary interface with 5 detent positions.

Core Features

Week-by-Week Build Plan

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

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 →