Philosophy note01
SELECTED ENTRY
Why I stopped thinking like a UX portfolio and started designing systems
A shift from showing screens to showing structure, logic, and real build potential.
Selected noteJOURNAL
Decision logsfrom the archive.
Notes on the decisions behind the systems: what changed, what was clarified, and why the work moved in that direction.
5 archive entriesReal notes from the process behind the systems and tools.
Tradeoffs visibleThe point is to show how decisions get made, not just the polished result.
Structure over polishReasoning matters as much as presentation.
JOURNAL STRUCTURE
Two kinds of notes: philosophy and design decisions.
Philosophy captures the principles behind CCR515. Design Decisions record the tradeoffs behind specific systems and builds.
ARCHIVE NOTE
The archive supports the systems instead of replacing them. Some notes explain the operating philosophy. Others trace concrete choices made inside the work.
PHILOSOPHY
Working principles behind the systems.
Broader notes about structure, energy, and why the portfolio is built this way.Decision log02
Why decision logs matter more than polished case studies
The value of showing tradeoffs, iteration, and reasoning instead of only polished final output.
Read noteDecision log03
Designing tools that reduce human energy expenditure
A working principle behind much of the automation and workflow design in this portfolio.
Read noteDESIGN DECISIONS
Choices made inside real projects.
Project-specific entries about system structure, interface direction, and product logic.Decision log01
Building a 0DTE simulator around structure instead of chaos
Why high-pressure environments become more usable when they are turned into systems.
Read noteDecision log02
The architecture behind my anniversary album app template
How a personal storytelling project became a repeatable product system.
Read noteDecision log03
Why PartyFlow belongs on Systems, not just as a SaaS idea
A note on treating PartyFlow as workflow proof: lead capture, package browsing, owner follow up, and status handling in one visible system.
Read noteDecision log04
Why Live Systems needed its own page
Why embedded prototypes needed a separate place to be tried directly without turning the Systems catalog into an app wall.
Read note