> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kviria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirmation

> Why a place the user named only in part waits for their yes before its coordinate is given.

When the request names a place only in part, Kviria does not give its
coordinate yet. "Take me to rite spot" is `find` with the name `rite spot`,
which names Rite Spot Cafe in part, so the answer is `one_unconfirmed`. Its `target` carries the name, the
category and the distance, but no `location`.

```text theme={null}
You:   "Is it Rite Spot Cafe (59 m)?"
User:  "yes, that one"     -> confirm, answer yes -> one, with the location and "confirmed": true
User:  "no, not that one"  -> confirm, answer no  -> many with the other places listed, or unclear
```

Send the user's answer as the next call, as `confirm` with `answer` yes or
no, with the `state` from the held answer.

Kviria also holds a place it found from a request that does not name it.
These resolve at once, without a question:

* a place the user named in full;
* a pick from the list the user just heard;
* "it" or "there", for a place settled earlier;
* a kind of place ("a cafe");
* a street corner;
* an exact address.

## Why

A word the user says can appear in the name of one nearby place without
meaning that place. "Help", "home" and "three" each match some business
name. A wrong coordinate handed to navigation is the most costly mistake
a location answer can make. The hold makes the user's own yes the last
step wherever the request left the place open.

## Turning it off

The `confirmation` field sets the policy:

* `"on"`, the default: a place named in part comes back as
  `one_unconfirmed`.
* `"off"`: it comes back as `one` at once, with its location. Use this
  only for agents with no person in the loop, which check the place some
  other way.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.