How it works

One photograph, taken from a known spot on a known day

Everything else in the app, the map, the history, the AI, the quests, exists to help you make, understand, act on, or care about that single thing. Here is the loop, step by step, and what the record keeps at each one.

The loop

From standing there to a report someone acts on

  1. 1

    Pick a site, then a viewpoint

    A vantage is not “somewhere near the stupa”. It is a stored position, bearing and tilt: a spot on the ground and a direction to face. The app holds a set of them for each site, and a quest points at whichever one has gone longest without being revisited, rather than at whichever is most photographed.

  2. 2

    Line the phone up

    The screen scores how well your position, heading and tilt match the stored vantage, using GPS, compass and the motion sensors together. When the match is genuinely close and the GPS accuracy is good enough to trust, the frame locks. One colour in the whole app means locked, so it reads at a glance in daylight.

  3. 3

    Take the photograph

    The image is written to the phone's own storage and recorded in a database on the device before anything is sent anywhere. A photograph taken at a viewpoint on a particular day cannot be retaken, so the phone is the record and the network is a copy of it.

  4. 4

    Note what you can see

    A short condition report: what has changed, what looks damaged, what is missing. The app looks at the photograph and suggests cracks it thinks it has found, drawn as dashed outlines so nobody mistakes a suggestion for a finding. You decide how serious it is. The AI never does.

  5. 5

    It reaches whoever is responsible

    The report appears on the custodian's dashboard alongside the site's coverage and its median time to acknowledgement. A custodian can acknowledge it, mark it in progress, or resolve it with a note, and export the whole set as CSV or GeoJSON for a real GIS workflow. More on the custodian side.

What makes it evidence

The difference between a photo album and a monitoring record

Anybody can photograph a monument. What makes a series usable to a conservator is that every frame carries enough information to be compared with the others, and that the record is honest about how good that information was.

A measurement is never faked

If the GPS never got a fix, the record stores unknown, not zero. Zero would read as a perfect reading, and one such row would quietly poison a decade of comparisons.

"By eye" never dresses up as "measured"

Conditions are sometimes bad: dense tree cover, a crowd, a phone with a confused compass. You can still frame the shot by eye and record it. The record then says it was done by eye, and it looks different on screen. A refusal to lock is a valid outcome, never an error.

Nothing is ever deleted

A photograph is evidence. A mistake is corrected by adding a new record that says what it supersedes, never by writing over the old one. That is what lets somebody in ten years reconstruct not just what was seen but what was believed at the time.

Where you do it

Three places, and only three

The app has exactly three destinations. They are the idea of the product rather than a navigation convenience, which is why there is no Home, no Explore, no Profile and no Rewards tab. Adding one is meant to require a hard decision.

The explorer

Tīrtha

a sacred crossing

The live map, and the front door. Your position against the heritage sites around you, a place that speaks as you reach it at the depth you chose, a fade between an old photograph and today, and routes that point at whatever has gone longest without a resurvey.

Evidence

Sākṣī

witness

The loop the whole product exists for: pick a viewpoint, line the phone up with it, take the photograph, and note the condition of what you can see. The record is written to the phone before anything reaches the network.

Knowledge

Dhamma

the teaching

Ask about Buddhist texts or heritage conservation and get an answer built only from real, cited passages, or an honest refusal when the sources will not support one.

Offline first

It has to work where there is no signal

A phone in the Sacred Garden at Lumbini can go hours without a usable connection, and the moment you are standing at the vantage is not reschedulable. So every record is written to a real database on the phone first, and synchronised afterwards whenever a network turns up.

The map works from tiles already on the device. The reference content (sites, viewpoints, history, narration) ships inside the app. Even the knowledge engine has an offline path: the built-in collection of source texts still answers, and an optional small model can be downloaded to the phone to phrase those passages, though it is never permitted to add a fact of its own.

The network is an optimisation, not a dependency. Nothing about the loop above requires one.