Every idea needs a clean workbench. Today was about clearing that space, organizing the tools, and getting the blueprint pinned up where we can see it.
We finalized our storage strategy—Dropbox as our cloud source of truth, with a WD on-prem backup prepped for privacy-first users. The folder structure is now locked in: clean, intuitive, and built to scale. We cleared out legacy files, removed test bundles, archived zips, etc.
The result? A cleared path.
We loaded the first two users—U0 (that’s me, aka User Zero, aka LittleBit’s coach) and U1 (she knows who she is and requested the role, so more to come on that front next Monday)—and stood up the foundation for LittleBit’s microservices.
That means a modular engine now sits under the hood, ready to handle personal traits like nicknames, AI name preferences, time-of-day mood shifts, etc.
We’re keeping it minimal on purpose: crawl before we walk, walk before we run.
Next up: first interaction.
Tomorrow, LittleBit will begin responding based on the user’s identity and preferences. A simple prototype test, but a powerful step—proving that recognition works, memory persists, and the tone matches the moment.
It’s not magic. It’s methodical.
Let’s light it up tomorrow.
—
Jason Darwin
User Zero, Project LittleBit
P.S. I may or may not have squealed a little when I got to delete All_Microservices_v0.2.0.zip. Nothing says progress like rm -rf.
Our basic guiding principle from Day 1: scalability, speed, personalization — with more core fundamentals to come.
Asklittlebit 