P3 — Parcel A Augmented-Reality Heritage Tour

Dashboard · Mandate · Plan · Reports · P1 Museum · P2 Recovery · P3 AR Tour · P4 Legal Gate

Project 3 — Llandough Parcel A augmented-reality heritage tour

Create a guided, location-aware AR tour showing what stood on Llandough Parcel A and explaining the longer history of its setting through source-linked digital wireframes. Existing research and browser-based storytelling give the project a starting point, but an AR experience, exact-site historic models, device testing and user pilot remain to be delivered.

Mandate and brief

Accessible heritage interpretation without false certainty

Core products: mapped tour route; source-linked waypoints; confidence-coded spatial layer; digital wireframes/historic scenes; guided script; AR-capable phone/browser prototype; device/accessibility tests; and a documented pilot/release acceptance decision.

Location control: the Roman villa/farm documented south of the church must remain at its evidenced location. Do not depict it as being on Parcel A unless site-specific evidence supports that placement. Nearby archaeology may be shown as a separate contextual waypoint.

Early monastery/ecclesiastical history: check the source, date and exact location before showing a structure on Parcel A. Where the evidence supports only a broader landscape interpretation, show it as context or a visibly hypothetical reconstruction.

Independence: P3 can begin now; new P2 records are useful dependencies for refinement but do not block route planning or the initial prototype specification. The Argentina museum is separate, and the tour has value without a museum building.

Milestones → work packages → tasks

12 starter tasks · 2 complete · 1 in progress · 9 not started

P3-M1 — Evidence and spatial confidence baseline

WP-P3-01 · site and source control

Output: mapped Parcel A tour route, with on-parcel and contextual sources separated.

  • DONEP3-T01 — Identify existing historical/archaeological source corpus relevant to Parcel A and nearby landscape
  • DONEP3-T02 — Identify existing visual storyboard/browser tour as an input, not an AR deliverable
  • IN PROGRESSP3-T03 — Map proposed Parcel A route, historic features, source references and location confidence

P3-M2 — Evidence-backed historic wireframes

WP-P3-02 · Roman and ecclesiastical layers

Output: a source-graded layer specification; geometry is placed only where location permits.

  • NOT STARTEDP3-T04 — Verify exact location of Roman villa/farm evidence before placing a scene on Parcel A
  • NOT STARTEDP3-T05 — Audit early ecclesiastical/monastic attribution, location, dating and source basis
  • NOT STARTEDP3-T06 — Define visual conventions for on-parcel fact, nearby context and hypothetical reconstruction

P3-M3 — Guided AR prototype

WP-P3-03 · models and visitor route

Output: wireframe content, source-linked waypoints and guided route storyboard.

  • NOT STARTEDP3-T07 — Specify the Roman-period wireframe and required geometry/source inputs
  • NOT STARTEDP3-T08 — Specify an early ecclesiastical/monastic layer only to the confidence the sources allow
  • NOT STARTEDP3-T09 — Storyboard guided route, evidence-linked waypoints, audio/text and visitor learning outcomes

P3-M4 — Pilot and release acceptance

WP-P3-04 · access, device and user tests

Output: tested prototype and explicit decision on public release.

  • NOT STARTEDP3-T10 — Build a phone/browser prototype before selecting specialist AR glasses
  • NOT STARTEDP3-T11 — Test accessibility, permission to access, route safety, privacy and device positioning
  • NOT STARTEDP3-T12 — Run documented pilot and pass source-accuracy, usability and acceptance tests

Product acceptance and controls

Location confidence before visual detail
  • Every waypoint has source reference, location method and confidence status.
  • On-parcel evidence, nearby context, regional history and hypothetical scenes use visibly different labels/styles.
  • Start with a device-agnostic phone/browser model; choose AR glasses only if a test demonstrates user benefit.
  • Confirm lawful route access, positioning accuracy, route safety, accessibility, privacy and low-connectivity fallback before a pilot.
  • Keep version history so new P2 material can revise a wireframe without destroying the prior accepted source/model state.

Highlight report — 22 October 2026

AMBER · pre-development

Completed inputs: existing historic/archaeology source corpus identified; existing browser-based visual tour/storyboard identified as an input.

In progress: route and spatial source mapping.

Not delivered: approved on-site Roman/monastic wireframes, functioning AR software, AR-glasses tests, field positioning and access checks, pilot or release-ready tour.

Next actions: perform the site/location audit; define confidence legend and wireframe products; build a low-cost prototype plan.

Decision requested: authorise the bounded source/spatial work package and set an acceptance reviewer before exact-site models progress.

Risks and dependencies

Accuracy before spectacle
  • Wrong-site depiction: no in-situ wireframe without location evidence.
  • False certainty: make uncertainty explicit and visually accessible to visitors.
  • Site access/device limitations: test permission, route and technical fallback before pilot.
  • P2 discovery feeds the tour by controlled change; neither all-source closure nor P1 completion is a start prerequisite.