Æthos · Co-founder & CTO · Right now
Helping people carry reflection into action, and return to it later.
Æthos helps people carry what they capture and reflect on into deliberate action, return to it later, and understand what has changed. I co-founded it and lead its engineering and product architecture, shaping the product with my co-founder and building the software from its data models to the experiences people use.
The situation
Æthos brings together journaling, guided experiences, reflection, and personal artifacts. The engineering problem is continuity: how can someone return to their material as it changes without losing what they originally said, what a previous experience used, or what they chose to keep?
That question runs through the data models, interaction design, and background processing. It also raises product decisions that no choice of technology can settle on its own.
What I do
With my co-founder, I translate product direction into architecture, workflows, and release milestones, and I lead the hands-on Flutter development. That includes local-first storage, versioned documents, cloud integrations, and shared patterns that technical and non-technical collaborators can build on.
My current engineering work separates original material, interpretations, participation records, and accepted artifacts. Sessions need clear rules for saving, resuming, submitting, and completing. Background processing needs to handle retries and stale results without silently changing an accepted record.
The Journal work applies the same principle to an export: someone sees an exact preview, deliberately accepts it, and can reopen that accepted artifact even if its source material changes later.
I also turn user feedback into product revisions. One critical revision was onboarding that explains what Æthos is, what to expect, and how to use it. My co-founder owns the final Journey copy; my contribution is the engineering and authoring system that supports it.
Where it stands
The app progressed from development and closed testing into active deployment. Current engineering work includes implemented shared session and recovery components, relationship review, and durable Journal export.
Research into interpretations and relationships is ongoing and does not yet establish validated outcomes for users. The a.Pen and a.Hat companion devices, for handwriting and screen-light audio, remain architecture, research, and early tooling work; physical end-to-end integration is still ahead.
The hardest discipline so far has been scope: deciding what each release needs, and holding to it.
Give the product a path forward.
Working toward a usable product and unsure how the pieces should fit? Tell me what exists and what you need it to do next.
Discuss your system