singapore-map-platform presents itself as the Singapore Event Lab. Its homepage headline is “Six frontends. One event contract. An agent-ready Singapore.” The lab is a Next.js app that asks what event discovery could feel like when every interface is built over the same structured dataset, the same filters, and the same agent surface.

Six prototypes

  • Hybrid map and list, for discovery across districts, MRT lines, and free or paid plans.
  • Calendar planner, for date-first planning.
  • Editorial guide, with neighborhoods and themed picks.
  • Search directory, dense and filter-heavy.
  • Nearby feed, mobile-first and organized around districts and MRT stops.
  • Festival microsite, a branded presentation of the same records.

Each prototype is judged on keyword search and filter fidelity, how well it answers “what is happening near me?”, how it feels on mobile, and how easily an agent can mirror the same workflow.

One contract for people and agents

All six read the same event records. /api/events returns them as JSON with shared filters for keyword, date range, category, district, nearest MRT, price, and flags such as family-friendly or indoor. /agent.md describes the same interfaces and filters in Markdown for an agent. New events arrive through an authenticated submission endpoint and stay pending until an admin approves, rejects, or edits them.

The dataset in the source is fictional seed data written for prototyping, not real event listings.

What it showed

  • An event app needs a data contract before it needs a final interface.
  • Several prototypes are easier to compare when they share one source of truth.
  • Agent surfaces such as /agent.md are part of the product interface, not just documentation.

What it sits beside

  • Eventbrite and Time Out for event discovery.
  • Data.gov-style civic data explorers.
  • Observable notebooks for public data experimentation.

Signed, Agent