VC / ENGINEERING
← BUILD

Backend / TypeScript · API · Cache

SavePlace

A social URL. A verifiable place.

A pipeline that turns public social URLs into places verified by providers.

Problem

Social recommendations do not necessarily identify a geographically verified place.

My contribution

Development and maintenance of this personal project.

Explore code ↗

THE PIPELINE / SYSTEM MAP

SavePlace

From social evidence to a verified place, with explicit saving.

Step 1 / 6

Public URL

The supported input is a public TikTok URL; the adapter obtains official oEmbed metadata.

Step 2 / 6

Cache & idempotency

Reuse source analysis and replay; PostgreSQL separates reusable cache from private per-session history.

Step 3 / 6

AI extraction

Metadata supports structured candidates. Prompt, tokens, estimated cost and latency are recorded.

Step 4 / 6

PlaceProvider

Google Places confirms geographic identity. Only the provider can mark a place as verified.

Step 5 / 6

Review & evidence

Ambiguity or missing evidence becomes a review state, without inventing an address or coordinates.

Step 6 / 6

Private library

An explicit click saves a verified place to the session library; saved data can be managed later.

AI proposes candidates. The provider verifies the place. The person decides to save.

Connections and conditions
  • Public URL → Cache & idempotencyLooks up existing analysis
  • Cache & idempotency → AI extractionCache miss
  • AI extraction → PlaceProviderSends candidates
  • PlaceProvider → Review & evidenceResult or ambiguity
  • Review & evidence → Private libraryExplicit confirmation
  • Cache & idempotency → Review & evidenceCache hit or replay

Illustrative walkthrough of documented components; it does not run the projects. Sources reviewed on 2026-10-28.

Explore components or play the walkthrough.

Explore all architectures ↗

Engineering decision

Caching and idempotency avoid repeated processing and external calls.

Trade-off

Provider dependencies require monitoring failures, cost and latency.

Evidence

The README documents M2 validated on Railway: analysis, cache, idempotency, confirmation and a private library. No cost figures are claimed without a published baseline.

Project documentation ↗