hivvan.devOUTPUT / IDENTITY> BACKEND SYSTEMS WITH JAVA AND PYTHON.DATA INTEGRITY. EXPLICIT STATE.READY
Backend Software Developer

Héctor V.

Forge

Active Development

Forge: Forge is a local-first execution engine for declarative data pipelines. It reads bounded CSV files and cursor-paginated REST APIs, processes records in batches, and writes them to PostgreSQL. Pipeline versions are immutable, while execution state, checkpoints, and batch receipts are stored durably. If a worker stops after PostgreSQL commits a batch but before the control checkpoint advances, the next worker reconciles the stored receipt before continuing.

forge.viewer
Recovery proof

1 / 4

Forge execution detail showing 10,000 records processed, one retry, one worker recovery and verified crash-recovery evidence.

Forge validates each manifest before publication and stores it as an immutable version with a checksum. Each execution therefore runs from the exact definition it was created with.

Lens

Active Development

Lens: I built Lens to turn noisy operational events into traceable incidents. Events are normalized and deduplicated before deterministic scoring, workflow changes enter activity history, and notifications move through an outbox with leasing and retries.

lens.viewer
Dashboard

1 / 4

Lens dashboard with incident metrics, priority distribution and priority queue.

The score combines frequency, recurrence, source criticality and event impact, stays within [0, 100], and is stored with its factor breakdown.

Tracer

Active Development

Tracer: I built Tracer as a local-first personal finance app backed by SQLite. It stores EUR amounts as integer cents and rebuilds ledger and dashboard projections from recorded events. CSV imports are reviewed before reaching the ledger, with local tools for backup, restore validation and recovery.

tracer.viewer
Overview

1 / 5

Tracer overview with monthly projections, financial readings and a weekly planner.

Tracer uses a configurable local home for its SQLite database, documents and recovery files. The runtime listens on the loopback interface by default, so financial data stays on the user's machine.