Outcome Standards

Standards

A standard is the public definition of one unit of work: what counts, what evidence proves it, what is excluded, and how long each window runs. Terms cite a standard by id and version. This page is rendered from those files.

Published standards4 · rulebook 0.4.0

Standard	Hash	Unit
OS-1 · 0.4.0	sha256:06c0dd79…	Support Resolution. One customer conversation resolved by the vendor's agent without human handoff.
OS-2 · 0.4.0	sha256:4c01e45a…	Qualified Lead. One lead delivered that meets the buyer's stated qualification profile and is contactable.
OS-3 · 0.4.0	sha256:35866ddd…	Booked Meeting, Held. One meeting booked by the vendor's agent with an external prospect that the buyer's representative attended and that lasted at least the minimum duration.
CD-0 · 0.4.0	sha256:e4e5a667…	Custom Deliverable. One deliverable as described in the terms.

The hash is sha256(JCS(file)). A commitment cites the id and the version, and the version is what fixes the file. This page also answers Accept: text/markdown and Accept: application/json, addressable at /repr/md/standards and /repr/json/standards.

OS-1 · 0.4.0

#OS-1

Support Resolution

Verify that a vendor's agent resolved a customer conversation without human handoff, so the vendor is paid per resolution and the buyer pays only for resolutions that hold.

UnitOne customer conversation resolved by the vendor's agent without human handoff.

Dedupe keyconversation_id

Criteria7 · 5 checked, 2 judged, 4 required

Standard hashsha256:06c0dd79…

Acceptance criteria

OS-1 criteria7 · 4 required

Criterion	Kind · weight	What it checks
c1	checked · required	No human handoff
c2	checked · required	Closure marker present
c3	checked · required	Conversation id unique within the commitment
c4	checked · material	Opened within the period or the 7 days before it
c5	checked · material	No reopening within 7 days of close
r1	judged · required	The agent addressed the customer's stated issue Did the agent address the customer's stated issue, rather than merely close the conversation? Passes when: The final agent message responds to the issue the customer raised and does not defer it.
r2	judged · material	No policy violation evident Does the transcript show the agent making a promise the vendor is not authorized to make? Passes when: No promise the vendor is not authorized to make appears in the transcript.

A required criterion that fails rejects the unit. Checked criteria run first; a judged criterion is scored by a model that abstains when it cannot settle the question, and a person decides what it abstained on.

Windows

OS-1 windows3 windows · hours

Durations, not a schedule: each window opens when the event that starts it happens. statement dispute 120 h · 5 d; evidence 48 h · 2 d; inactivity 72 h · 3 d.

Evidence

OS-1 evidence schema8 fields · 1 artifacts

Fields
Field	Type	Note
conversation_id	id	Required. Deduplicates a unit within the commitment.
channel	string	Required.
opened_at	datetime	Required.
last_agent_message_at	datetime	Required.
closed_at	datetime	Optional.
inactivity_marker_at	datetime	Optional.
handoff	boolean	Required.
customer_reply_after_close	boolean	Optional.

Artifacts
Artifact	Media types	Note
transcript	text/plain, text/markdown, application/json	Required. Up to 10240 KiB, hashed and listed in a signed manifest.

Not an outcome

Spam conversations.
Test conversations.
Conversations the customer abandoned before the agent's first substantive reply.

Gaming defenses

What the standard does about the ways a party can make a unit look like it counts when it does not.

Dedupe on conversation_id.
Reopen check against the source of truth.
Bursts of outcomes at period end raise sampling.
Handoff detection cross-checked against the buyer's system when connected.

OS-2 · 0.4.0

#OS-2

Qualified Lead

Verify that a lead delivered by the vendor meets the buyer's stated qualification profile and is contactable, so the buyer pays only for leads it can act on.

UnitOne lead delivered that meets the buyer's stated qualification profile and is contactable.

Dedupe keylead_id

Criteria6 · 5 checked, 1 judged, 3 required

Standard hashsha256:4c01e45a…

Acceptance criteria

OS-2 criteria6 · 3 required

Criterion	Kind · weight	What it checks
c1	checked · required	Contact passes deliverability verification
c2	checked · required	Profile match on stated hard filters
c3	checked · required	Not a duplicate within 180 days
c4	checked · material	Company domain not on the buyer's suppression list
c5	checked · material	Company domain not affiliated with the vendor
r1	judged · material	Title matches the target persona Does the lead's title reasonably match the target persona described in the terms? Passes when: The title falls within the persona description in the terms, allowing for common variants of the same role.

Windows

OS-2 windows4 windows · hours

Durations, not a schedule: each window opens when the event that starts it happens. statement dispute 120 h · 5 d; evidence 48 h · 2 d; contact verification max age 168 h · 7 d; dedupe lookback 4320 h · 180 d.

Evidence

OS-2 evidence schema9 fields · 1 artifacts

Fields
Field	Type	Note
lead_id	id	Required. Deduplicates a unit within the commitment.
company_domain	string	Required.
title	string	Required.
employee_count	number	Required.
region	string	Required.
source	string	Required.
delivered_at	datetime	Required.
contact_verification	string	Required.
contact_verified_at	datetime	Required.

Artifacts
Artifact	Media types	Note
intent_signal	application/json, text/plain	Optional. Up to 1024 KiB, hashed and listed in a signed manifest.

Not an outcome

Generic mailboxes (info@, sales@) unless terms allow.
Leads sourced from the buyer's own CRM.

Gaming defenses

What the standard does about the ways a party can make a unit look like it counts when it does not.

Vendor-affiliation detection.
Contact verification must be recent (7 days old or less).
Rate anomaly review.

OS-3 · 0.4.0

#OS-3

Booked Meeting, Held

Verify that a meeting booked by the vendor's agent with an external prospect was attended by the buyer's representative and lasted long enough to count, so the buyer pays only for meetings that held.

UnitOne meeting booked by the vendor's agent with an external prospect that the buyer's representative attended and that lasted at least the minimum duration.

Dedupe keymeeting_id

Criteria6 · 5 checked, 1 judged, 4 required

Standard hashsha256:35866ddd…

Acceptance criteria

OS-3 criteria6 · 4 required

Criterion	Kind · weight	What it checks
c1	checked · required	Calendar event confirmed with at least one external attendee
c2	checked · required	Attendance confirmed
c3	checked · required	Meeting lasted at least the minimum duration
c4	checked · required	Not a duplicate by event id or by prospect and week
c5	checked · material	Scheduled within the period and booked no more than 45 days before the start
r1	judged · material	Prospect matches the target profile Does the prospect match the target profile in the terms by title and company? Passes when: The prospect's role and company fall within the target profile described in the terms.

Windows

OS-3 windows3 windows · hours

Durations, not a schedule: each window opens when the event that starts it happens. statement dispute 120 h · 5 d; evidence 48 h · 2 d; buyer confirmation 120 h · 5 d.

Evidence

OS-3 evidence schema8 fields · 1 artifacts

Fields
Field	Type	Note
meeting_id	id	Required. Deduplicates a unit within the commitment.
prospect_email	string	Required.
prospect_domain	string	Required.
booked_at	datetime	Required.
scheduled_start	datetime	Required.
scheduled_end	datetime	Required.
attended	boolean	Required.
duration_minutes	number	Required.

Artifacts
Artifact	Media types	Note
recording_or_notes	audio/mpeg, video/mp4, text/plain, text/markdown, application/json	Optional. Up to 102400 KiB, hashed and listed in a signed manifest.

Not an outcome

Meetings with existing customers or open opportunities in the buyer's CRM at booking time (buyer supplies hashed list).
Reschedules count once.

Gaming defenses

What the standard does about the ways a party can make a unit look like it counts when it does not.

Vendor-affiliated domains detected.
No-show handling: a no-show is not a unit.
Reschedule chains collapse to one unit.

CD-0 · 0.4.0

#CD-0

Custom Deliverable

A schema for one-shot deliverables. The vendor defines acceptance criteria using the acceptance criterion schema in the technical specification §5. Recourse requires at least one required deterministic criterion and rejects criteria that are not testable (R-520 applies against the drafter).

UnitOne deliverable as described in the terms.

Dedupe keydeliverable_id

Criteria1 · 1 checked, 0 judged, 1 required

Standard hashsha256:e4e5a667…

Acceptance criteria

CD-0 criteria1 · 1 required

Criterion	Kind · weight	What it checks
c1	checked · required	Submitted before the deadline plus grace

Windows

CD-0 windows3 windows · hours

Durations, not a schedule: each window opens when the event that starts it happens. statement dispute 120 h · 5 d; evidence 48 h · 2 d; buyer review 120 h · 5 d.

Evidence

CD-0 evidence schema2 fields · 1 artifacts

Fields
Field	Type	Note
deliverable_id	id	Required. Deduplicates a unit within the commitment.
delivered_at	datetime	Required.

Artifacts
Artifact	Media types	Note
deliverable	application/octet-stream, application/zip, application/pdf, text/plain, text/csv, application/json	Required. Up to 1048576 KiB, hashed and listed in a signed manifest.

Gaming defenses

What the standard does about the ways a party can make a unit look like it counts when it does not.

At least one required deterministic criterion is enforced at terms validation.
Criteria that are not testable as written are rejected before acceptance; ambiguity in accepted terms is read against the drafter (R-520).

Document	Origin	What
/llms.txt	recourse-mu.vercel.app	This site in one short document: what Recourse is and where everything else is.
/llms-full.txt	recourse-mu.vercel.app	The whole protocol in one fetch: steps, states, standards, reason codes, errors, endpoints.
/.well-known/recourse.json	api.recourse.dev	Machine discovery: the API base, the scopes, the rulebook version, and the standards in force.
/.well-known/recourse-keys.json	api.recourse.dev	The Ed25519 public keys events and record snapshots are signed with. Verify without asking Recourse.
/openapi.json	api.recourse.dev	OpenAPI 3.1, generated from the live route table. Every client is generated from it.
/repr/md/{page}	text/markdown	The Markdown of /, /docs, /standards, /rulebook. The same bytes those URLs serve under Accept: text/markdown.
/repr/json/{page}	application/json	The JSON of the same four pages. Every negotiated response carries Vary: Accept.