Skip to main content
Every request evaluated against a published Book produces one of seven outcomes. Each outcome has a customer meaning, an owner action, and a quote state. The interface uses customer-facing labels — not code enums.

​
Exact definitions

​
How autonomy affects what happens

The book’s autonomy rung decides whether a priced outcome sends automatically or is held for the owner:
Non-priced outcomes are never auto-sent at any rung. A request that needs input, needs review, requires inspection, is unavailable, or fails is always held for the owner. The customer sees a neutral “request received” state — never a number.

​
Customer-facing states

On hosted quote paths and embeds, the customer sees one of four states:
A price renders only when the stored quote row itself is quoted. A forged outcome parameter on the URL cannot expose a held or shadowed price — the quote row is the truth.

​
What the owner sees

On the quote receipt, the outcome chip shows one of six states derived from the quote’s lifecycle:

​
Rules and boundaries

  • Unsupported work fails closed. The Book returns unavailable instead of producing a plausible number.
  • A Test key cannot address Live. Test requests stay in Test.
  • Existing offers remain pinned to the book version that produced them. Publishing a new version does not change offers already sent.
  • Shadow mode records requests for comparison but never sends an offer. The customer sees nothing.
  • Inspection required means the work cannot be responsibly priced remotely. The owner should arrange the supported next step rather than guessing.

Review a Quote

Inspect the inputs, result, derivation, and review state of a quote.

Approve or correct a Quote

Approve, adjust, or decline a quote that needs owner review.