Systems, interfaces, and reviewable work.

Problem

API responses change in small ways that are easy to miss during review. A renamed field or changed type can pass through a changelog and still break consuming code.

Architecture Notes

• Parse the old and new JSON structures into comparable trees.
• Classify structural changes by the risk they create for consumers.
• Keep the workflow CLI-first so it can run locally, in CI, or before a release.
• Print terminal output that helps a developer see the change quickly.

Problem

Large JavaScript files can hide the path from one function to another. Before changing behavior, it's useful to see the call relationships without reading the whole file line by line.

Architecture Notes

• Parse source files and extract function declarations and call expressions from the AST.
• Generate a graph that favors readable relationships over compiler-level completeness.
• Support code review, onboarding, and refactoring where control flow needs a quick audit.
• Keep the tool small instead of turning it into a broad analysis platform.

Problem

Property data is often scattered across sources, repeated under slightly different names, and separated from the building it belongs to. A listing-first product can look confident while carrying those errors forward.

Architecture Notes

• Use the physical building as the main record instead of letting listings define the model.
• Keep verdict logic outside the presentation layer so each conclusion can be reviewed.
• Use Supabase with typed boundaries between storage and the application.
• Build the Next.js interface around comparison, source review, and correction.

Problem

Route-sharing is not just a shortest-path problem. Timing, trust, repeated trips, and local habits all affect whether a shared route is useful.

Architecture Notes

• Model route records as paths that can be reused by a community.
• Match users through compatible timing, direction, and repeated travel patterns.
• Design the interface for recurring trips rather than one-off searches only.
• Treat mobility data as shared infrastructure that needs careful handling.