gmz.dev
Systems, tools, and documentation by Martín Gómez.
v0.1 · working document
index file for current systems, notes, and references. not final; updated as needed.

Overview

gmz.dev is meant to behave like a README for the tools and systems in use – not a marketing site. The goal is to keep a plain record of what exists, how it works at a high level, and where to look if more detail is needed.

Tone guideline: write as if explaining the system to yourself six months from now.

Scope

  • Small calculators and logic layers (SiteTax and related tools).
  • iOS pipelines (Watermarkd and similar tools).
  • Links to fuller docs or external surfaces when they exist.

Notes on style

  • Prefer simple language over clever names.
  • Capture assumptions; they are easy to forget.
  • Short sections are fine; this is allowed to be incomplete.

Systems (current)

Short descriptions only. Detailed diagrams or code should live in separate docs or repositories.

SiteTax calculator logicstatus: shipping

Logic to decide when work is treated as taxable repair vs. capital improvement (NJ focus). Backed by a few clear rules rather than a giant decision tree.

  • Inputs: job description, location, type of work, form flags (if supplied).
  • Outputs: taxable / non-taxable result, with a simple explanation.
  • Constraint: better to be explicit about assumptions than silently guess edge cases.

Doc: /docs/sitetax-logic.html

Watermarkd rendering pipelinestatus: v1

iOS pipeline for importing an image, applying text/graphic overlays, and exporting at a predictable size and quality.

  • Inputs: source image, overlay text, position/scale, export settings.
  • Outputs: exported image ready for sharing or posting.
  • Considerations: export performance, safe text sizes, and not overcomplicating the controls.

Doc: /docs/watermarkd-pipeline.html

Docs (entry points)

These are suggested entry points for deeper documentation. They live as separate HTML files under /docs.

Architecture overviewplanned

High-level description of how front-ends (Next.js, SwiftUI) connect to engines (SiteTax, pipelines, future tools) and storage (SQLite, Firestore, etc.).

Doc: /docs/architecture.html

Patterns & interfaceswip

Notes on shared UI patterns (inputs, result cards, sliders, export flows) and internal API shapes that keep tools consistent.

Doc: /docs/patterns.html

Notes / logongoing

A running text file or log for small decisions that are too minor for a big doc but worth recording (e.g. tax edge case tweaks, export defaults).

Doc: /docs/notes.html