INFRASTRUCTURE / 2025–PRESENT
Momentra
community event data infrastructure: an event aggregator, event database, and events API for trustworthy public events.
Active
The problem
“What would have to be true before you trusted the system enough to stop checking behind it?”
The context
Community calendars rely on information scattered across organizations, websites and publishing workflows.
The technical approach
Find event information across trusted organizations, resolve identities, reconcile conflicting details, preserve provenance, and track changes. Source pages are captured as immutable archives and replayed through several extraction methods at once, comparing the results and flagging disagreement instead of averaging it away. Every field keeps its source URL, extraction method and transformation history, and a record that drifts from the expected schema fails closed rather than publishing degraded data. Structured records are then available through APIs and related interfaces.
The system or artifact
Structured event records with source context, changes and interfaces for downstream systems. The sketch above shows the conceptual flow, not a production architecture.
What I learned
Extraction is only the beginning. Identity, responsibility and recency all affect whether information is useful. The reliability comes from the unglamorous parts: retry, recovery, and always knowing where a value came from.
Where it stands
This is part of my current work.
Visit Momentra for product details ↗