Clear workflows
Can someone understand the path through the system without fighting the interface?
I build developer tooling and validation systems around the parts of engineering work that need to stay reviewable: evidence records, guarded model calls, parser diagnostics, project dossiers, and self-hosted infrastructure.
I am a computer science student at the University of Hawaiʻi at Mānoa, expected to graduate in Autumn 2026, building towards software engineering roles through practical, inspectable projects.
Earlier spreadsheet and app projects still matter because they taught me how much boundaries and verification matter when a system depends on calculations. The current through-line is developer-facing systems: what was built, what evidence supports it, and where the decisions live.
Started with spreadsheet-native modelling work where formulae, build comparisons, and verification discipline mattered.
Moved towards local-first tools that keep AI-assisted work, evidence, records, and decisions inspectable.
Built standards, dossier checks, source-backed claims, and validation entrypoints around project work.
Treating deployment, checks, provenance, and maintenance as part of the system rather than the afterthought.
Can someone understand the path through the system without fighting the interface?
Can a claim be traced back to source records, validation output, or a clear decision?
Can it actually be deployed, hosted, observed, and maintained after the demo works?
Forecasting workflow project with biweekly stakeholder meetings, progress demos, and feedback cycles around financial modelling, dashboards, and backend foundations.
Local document retrieval and citation project with weekly stakeholder meetings for source context, project direction, and feedback on Faculty Senate document workflows.
Funded education-focused project with recurring progress reports and a planned presentation to the Education Committee.