Architecture
Under the Hood
Git Happened is the physical version-control layer. A vision provider supplies observations. The current live implementation uses Roboflow for the raccoon demo.
VISUAL INPUT
↓
VISION PROVIDER
↓
NORMALIZED OBSERVATIONS
↓
GIT HAPPENED
↓
PHYSICAL COMMITS / DIFFS / HISTORY
Current live implementation: Roboflow raccoon Workflow (ash-morales/git-happened-raccoons).
Live demo
Raccoon video
VIDEO
↓
ROBOFLOW
↓
DETECTIONS / TRACKING
↓
STABILIZED PHYSICAL STATE
↓
GIT HAPPENED COMMITS
Roboflow watches every frame. Git Happened remembers what mattered.
Roboflow owns
- Detection
- Localization
- Tracking
- Confidence
- Visual observations
POST /ash-morales/workflows/git-happened-raccoons · 55% confidence
Git Happened owns
- State interpretation
- Meaningful-change filtering
- Physical commits
- Diffs
- History
- Persistence and presentation
Experimental image versioning
We also prototyped sequential image commits using Roboflow detection, object naming, and physical diffs. That implementation is currently disabled while we evaluate the right long-term vision provider and cost model.
Code preserved under archive/roboflow-still-image and behind ENABLE_STILL_IMAGE_VISION.
Limitations
- Instances are not re-identified across frames. A raccoon that walks across the yard may look like a move or a remove/add.
- Empty inference is shown as empty. We do not invent objects to make the demo succeed.
- Repos, commits, and the demo timeline persist in this browser via IndexedDB. Supabase keys may be present for a future durable backend, but they are not the live store yet. Footage is never committed to git.