Veldarium Worth Portfolio build · 2026
All six systems

Freight, dispatch & logistics

FreightFlow

Dispatchers choose carriers under conflicting windows, capacity, and cost. A first-available plan looks fast and loses. The constrained plan has to be shown winning, with the comparison auditable, not just claimed.

Product thesis: Dispatch under real constraints. A naive plan loses, a constrained plan wins, and the comparison is shown, not claimed.

Cabberefwenf/FreightFlow · main @ 7a68dcb4 (2026-10-22)

Interactive demo in development
Conceptual interface illustration, not a screenshot of a live application.

Primary workflow

A logistics command system. Dark, map-and-network-first, with a recovery comparison at its center.

  1. Command view with KPI drilldowns, then shipments, dispatch, carriers, routes, costs, exceptions, analytics, and simulator views.
  2. Validated shipment creation and lifecycle, dispatch with overlap rejection, and explainable carrier ranking with an explicit decision trace.
  3. Dijkstra routing with equipment rules, required stops, and closures.
  4. Charge-level profitability in integer units, with negative-margin handling.
  5. Immutable scenario comparison against the persisted executed recovery.
  6. Guided Iron Relay recovery: brief, disrupt, evaluate, decide, recover, analyze, reset.

Architecture

  • Next.js 16, React 19, TypeScript, Tailwind 4, Zod, Recharts. Single route with 11 in-app views driven by a reducer store.
  • Pure domain modules: carrier, dispatch, exceptions, finance, KPIs, recovery, route, scenario, state machine, schemas. No backend, no database, no auth.
  • Seeded fixtures in a data module. Versioned IndexedDB persistence (schema v1), with filters and simulator inputs intentionally ephemeral.
  • Frozen demo clock. SVG network renderer plus Recharts analytics.

Engineering decisions

  • Keep the domain pure and the store a reducer, so dispatch decisions are reproducible from the same seed.
  • Persist executed state, keep scenarios immutable, and compare the two instead of overwriting history.
  • State limitations in the product itself: synthetic network, not live telematics, not hours-of-service compliance, not a commercial rating engine.

Technical challenges

  • Eleven open, unmerged, stacked PRs sit on top of a 3-commit main. Branch-tip test claims are not main capabilities and must not be presented as the demo.
  • Snapshot-only seed edits (named drivers, deterministic equipment-coherent weights) are not in the repo. Remote main still labels drivers Driver A.11 style and randomizes background weights.
  • The app brands itself Veldarium Works while this portfolio is Veldarium Worth. That naming decision belongs to the founder; no rename is made here.

Demonstration scenario

  1. Iron Relay: a critical shipment, Detroit to Nashville, 31,800 lb, 48 pieces, with assembly commitments and stated exposure in the fixture.
  2. A disruption lands. Evaluate carriers on cost, service, and risk with the decision trace visible.
  3. Choose the recovery, execute it, and compare the executed recovery against the immutable scenario.
  4. Reset and try another decision. The guided flow returns to the deterministic start.

Engineering evidence

  • Domain test file contains 14 unit test blocks, counted from the file. The repo test doc claims 14 unit and 5 browser tests pass; neither was re-run in VW-100 recon. [OBSERVED file count; DOC-CLAIMED pass result, UNVERIFIED]
  • A CI workflow exists on main (typecheck, lint, test, build, Playwright). No CI run results were observed. [OBSERVED, workflow file only]
  • In-product engineering handbook states its own limitations explicitly. [OBSERVED]
  • Welcome modal labels the demo as synthetic data, no login, browser-local persistence. [OBSERVED]

OBSERVED means read from repository evidence at the stated commit. DOC-CLAIMED means a repository document states it but it was not re-run during reconnaissance. UNVERIFIED means no supporting evidence was obtained. See the engineering inventory.

Known limitations

  • No verified public deployment URL. Deployment doc states no production deployment or URL was verified. portfolio.json has deploymentUrl null.
  • Browser and responsive behavior were not verified in VW-100 recon. The CSS has breakpoints and a reduced-motion rule; that is not a browser result.
  • Screenshot files referenced in the README were not verified (binary fetch limitation, not evidence of absence).
  • Return-to-portfolio link shows Destination not configured when its portfolio URL variable is unset.
  • Roadmap honestly lists unbuilt items: URL-backed state, multi-exception recovery, migration harness, keyboard shortcuts, visual-regression and accessibility audits, verified deployment.

Sandbox readiness

IndexedDB persistence, schema-versioned, stale schemas rejected. Reset returns to the deterministic start. No session duration or timeout was observed in code. A persistent visible DEMO indicator beyond the welcome modal was not observed. 60-minute exploration depth is UNVERIFIED.

Current portfolio status: Demo unavailable in this harness: no deployment verified, demoUrl null, allowlist empty.