--- title: "Artifact Site Camera" date: "2026-07-17" canonical: "https://raytally.com/en/ideas/2026-07-17-bronze-age-sword-find-poland/" generator: "RayTally · dev-prompt-v4" signal: query: "bronze age sword find poland" observed_at: "2026-07-17T00:33:07.089Z" active: false ended_at: "2026-07-16T21:40:00.000Z" window_hours: 168 sources: - url: "https://notesfrompoland.com/2026/06/19/detectorist-finds-2700-year-old-bronze-age-sword-in-poland/" boundary: "Published at 2026-06-19." - url: "https://www.britishmuseum.org/our-work/national/treasure-and-portable-antiquities-scheme" boundary: "No publication timestamp is present in the source record." - url: "https://doc.arcgis.com/en/survey123/get-started/faqgetanswers.htm" boundary: "No publication timestamp is present in the source record." - url: "https://digventures.com/digital-dig-team/" boundary: "No publication timestamp is present in the source record." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-17-bronze-age-sword-find-poland/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Artifact Site Camera Guides phone photos of a suspected artifact by capturing the wider scene, scale, orientation, and soil layer, then creates a submission record that preserves site context. ## Product concept A mobile camera for hikers, farmers, and metal-detecting enthusiasts that creates a complete discovery record while a suspected artifact is still in place. When users spot a possible artifact, the first screen tells them not to clean or move it, then uses framing guides to capture a wide shot, scale, burial depth, and orientation. The app locks the time and coordinates and compiles a report with a site sketch and notes on uncertainty for submission to a museum or heritage agency. If the object has already been moved, it clearly marks the missing context and guides users to capture the surrounding soil and original location. Standard visual-identification apps rush to answer “what is this?”; this preserves site information that cannot be recovered once the object is moved. ## Why now (backed by facts) In June 2026, a Polish metal detectorist found a Bronze Age sword buried upright in woodland, protected and reported the site before heritage staff joined the recovery. Related searches reached roughly 1,000+ and grew by about 200% in a trend snapshot, but had declined by the observation on July 17, 2026, 00:33 UTC; the trend ended on July 16, 2026, 21:40 UTC. The story made “not immediately pulling out the object” a key part of the event, giving users and heritage institutions a clear example that the first set of photos after a discovery may matter more than identifying the object right away. ## Direction (model inference, not independently verified) Target user: Hikers, farmers, and metal-detecting enthusiasts open it when a suspected artifact has just emerged from soil and has not been cleaned or removed. If it has already been moved, they can still document the original location, surrounding soil, and missing context. Minimal entry point: Start with four offline capture steps: wide shot, close-up with scale, orientation and burial depth, and surrounding soil. Then use the phone’s camera and location services to lock time and coordinates and generate a shareable PDF, without object identification. The strongest case against: The strongest case against this is that reporting rules and intake formats vary by region. If heritage agencies do not accept app-generated records, users will revert to their usual practice of taking photos and then calling. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Create localized guidance pages for specific questions such as “what to do if I dig up a suspected artifact” and “how to report a metal-detecting find.” Ask metal-detecting clubs, local museums, and farmer groups to distribute QR codes so the app appears before users are likely to find an object. ## Competitors & gaps (model inference) - Portable Antiquities Scheme (PAS): PAS accepts public submissions of archaeological finds, but its core workflow starts with registration and contact after a discovery. This idea moves the process into the minutes while the object remains in place, first preserving orientation, depth, scale, and surrounding soil. - ArcGIS Survey123: Survey123 can already collect photos, time, and location offline, but it is a configurable general-purpose field form. The gap here is an out-of-the-box capture sequence for accidental finders, with an on-site constraint not to move the object. - Digital Dig Team: Digital Dig Team serves organized archaeological projects and professional field documentation. This targets chance finds during hiking, farming, or metal detecting, before they enter a formal excavation workflow. ## How it makes money (model inference) Free for individuals; charge museums, local heritage agencies, and archaeological organizations an annual institutional fee for localized capture forms, intake queues, and standard report templates. ## Trend background Theme: Polish Bronze Age sword discovery Trigger query (original English): bronze age sword find poland Approx. search volume: 1000+ (approximate) Approx. increase: +200% (approximate) The trend data is a historical snapshot from the moment it was captured; volume and increase are approximate and only explain “why now.” Do not write them into product copy as precise market numbers. ## Sources - Detectorist finds 2,700-year-old Bronze Age sword in Poland (https://notesfrompoland.com/2026/06/19/detectorist-finds-2700-year-old-bronze-age-sword-in-poland/) - The Portable Antiquities Scheme (PAS) (https://www.britishmuseum.org/our-work/national/treasure-and-portable-antiquities-scheme) - FAQ for submitters—ArcGIS Survey123 (https://doc.arcgis.com/en/survey123/get-started/faqgetanswers.htm) - Digital Dig Team - the future of fieldwork (https://digventures.com/digital-dig-team/) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.