LOADING MAP SHEET
Private preview · Arcwise AI
One proposed interface for resolution, evidence, proximity, and physical-world context.
“What should we know before screening this location?”
I can suggest common factors such as access, terrain, utilities, and hazards, but I cannot verify the site or the freshness of any underlying source.
“What should we know before screening this location?”
The location needs to be resolved before any fields are trusted. This sample would request the project’s screening fields and return a review queue rather than a go/no-go decision.
ONE INTERFACE
Arcwise is being designed as a narrow place layer: enough structure for an agent to work, enough evidence for a person to review, and typed limits when the answer is not available.
The same core question appears in different forms: what matters here, and what evidence can support the next decision?
PROPOSED PRODUCT SURFACE
01POST /v1/ask
Describe the decision and the location. The proposed planner would select only the context needed, then return a structured answer with review boundaries.
See the proposed interfaceWhat context would materially change this site screen?
02POST /v1/resolve
Resolve an address, coordinate, or place reference without hiding weak matches. Ambiguous inputs should ask for clarification instead of producing a plausible wrong point.
See the proposed interfaceResolve: 14 Market Square, Example City
03POST /v1/context
Request the physical-world fields the workflow actually needs. Each value stays attached to its status, timing, and source notes.
See the proposed interfaceFields: slope · flood context · grid proximity
04POST /v1/nearby
Screen candidate locations by proximity and network assumptions while keeping the calculation method visible to the reviewer.
See the proposed interfaceOrigin: candidate site · method: declared