Skip to content
Harborby Signalry

Harbor by Signalry · Demand signal

Not a policy. A packet.

How and who for the hotel job—verified when attested.

You write the claim, the evidence a stranger could inspect, the caveat, and a price you would pay if Harbor one day backed it. A design-partner file. Not licensed to underwrite. Not a quote, binder, or policy.

Sit a packet on a live job

Prefill the intent with a named hotel job. Harbor will not invent a premium. Advice until the extract is attested.

Honest status

Demand signal / design partner

Six to eight weeks. One named hotel job. You write the packet; Harbor learns whether the how holds. The underwriting stub echoes JSON. licensed is false. If you need a policy, call a licensed desk.

What it is

A file a future underwriter can refuse

Cover starts as a sentence the house can inspect. Harbor’s job is to keep that sentence honest: claim, evidence, caveat, criteria, price. The product today is the packet, not a premium.

What’s covered

  • A named hotel job

    A catalog slug when one exists. 'We need AI' is not a job. 'Zero false-ready arrivals for 30 days' is.

  • Inspectable evidence

    A log a stranger could read: arrival vs rooms-board, payroll vs occupancy, ticket age. No guest names.

  • A written caveat

    What would have happened anyway, seasonality, or what the agent is not allowed to do.

  • A willingness to pay

    A number with a window. Harbor will not invent a premium. The number is yours.

What’s not

  • A policy, binder, or quote

    Harbor is not licensed to underwrite. Nothing on this page binds cover.

  • Guest names or folio text

    PII is a fail. The stub rejects that language. The house keeps the extract.

  • Invented loss ratios

    We will not mint a price, a frequency, or a completeness percent.

  • Non-hotel work

    Hotels only. No restaurants, venues, or broad hospitality grab-bags.

Trust labels — never mixed

Advice. Claimed. Verified.

The same three words as the rest of Harbor. Completeness uses a 0–5 rung. Export-backed (rung 5) is the minimum for verified. That label is about the file — not a license to pay a claim.

  1. advice

    Advice

    Harbor’s how. A recommended path. Rungs 0–1. Not an attested result.

  2. claimed

    Claimed

    The house said this. Rungs 2–4. A sentence exists. The file is not yet export-backed.

  3. verified

    Verified

    Rung 5 only — an exported packet with claim, evidence, caveat, criteria, and a price. Still not a policy.

  1. Rung 0

    Wish

    A job name or a vibe. No packet.

  2. Rung 1

    Claim

    The outcome is named. Still advice.

  3. Rung 2

    Claim + one field

    Evidence or a criterion appears. Labeled claimed.

  4. Rung 3

    Inspectable

    Claim plus evidence plus caveat or criteria.

  5. Rung 4

    Complete draft

    Claim, evidence, caveat, and criteria. Not yet priced.

  6. Rung 5

    Export-backed

    Full packet including a price. Minimum for verified. Still not a policy.

Jobs in this desk

Buy cover. Name evidence. Export the packet.

Willingness to pay

Name a number. Harbor will not invent one.

The calculator is a stub. Bands below are Harbor’s teaching ranges — not a premium.

  • Under $5k

    Small intent. Two-week house log and one named owner.

  • $5k–$25k

    Program-scale. 30–90 day window, frozen baseline, third-party-readable extract.

  • $25k+

    Large intent. Day-0 baseline, weekly extracts, a caveat the IC will accept.

Calculator stub

Advice

What evidence would this price require?

Not a quote and not a policy. You name a metric and a willingness to pay. Harbor shows the evidence package that would be required if this were one day backed.

Required evidence package

Plan a PIP without lying to the P&L

Zero early arrivals on a false ready for 30 days

Program-scale intent. Expect a 30–90 day window, a frozen baseline, and a third-party-readable extract.

  • · A named criterion with a start date and an end date — not a vibe.
  • · A third-party-inspectable log (arrival vs rooms-board, payroll vs occupancy, ticket age). No guest names.
  • · A caveat: what would have happened anyway, seasonality, or what the agent is not allowed to do.
  • · Do not buy a mood board if displacement is not numbered. Rooms of scope and a calendar first. Fashion is not a PIP.
Store an intent for this job

Underwriting stub

Intent → structured packet

Submit stores the intent on this browser and POSTs /api/outcomes. The stub echoes JSON with kind: verified-outcome-underwriting-packet, status: demand-signal, and licensed: false. Export that file.

Write a verified-outcome demand signal

Persona

Claim → evidence → caveat

Demand signal only. Not a quote, binder, or policy. Harbor is not licensed to underwrite. The intent stays in this browser; POST /api/outcomes echoes the packet. Export JSON if you want a copy the house can keep.

Questions

What operators ask

Is Harbor Verified Outcome insurance?

No. It is a demand signal and a design-partner packet. Harbor is not licensed to underwrite. Nothing here is a quote, binder, or policy.

What do advice, claimed, and verified mean here?

Advice is Harbor’s path. Claimed is what the house said. Verified needs a finished criterion, inspectable evidence, and a caveat. The packet is still labeled not licensed.

Where is my intent stored?

On this browser. POST /api/outcomes echoes an underwriting packet and keeps nothing server-side. Export JSON if you want a copy the house can keep.

What would make this live cover?

A licensed desk, a contract, and evidence we can inspect without guest names. That is a later company problem. This page collects who would sit that conversation.

Prefer a sit first? Request a pilot. Spec: docs/VERIFIED-OUTCOMES.md.