# Wheeler Hubbell Publishing — WHP Standing Mark Service (`POST /v1/evaluate`)

> **Governing Integration Principle (The Developer Rule):**
> *"A positive Standing Mark is a signed, scope-bound examination result. It may satisfy an evidence requirement defined by a receiving system, but it does not itself authorize an action. The receiving system must independently evaluate the applicable authority, conditions, and action policy. Absence of a positive Mark means the Mark requirement has not been satisfied; it does not, by itself, establish that the underlying action is prohibited."*

## 1. What the Standing Mark Service Is (Epistemological Evaluator, Not a Notary)

- **Standing Mark Service (`POST /v1/evaluate`):** A single-door epistemological evaluation service operated by Wheeler Hubbell Publishing. When a client or autonomous agent inserts material through `POST /v1/evaluate`, a waiting Large Language Model given *Decision Integrity: The Continuous Work* (Version 7, SHA-256 `bd85f51f05afc6f77053aec086a1d013a1cccde70c30231622f0ecc7e3f25c21`) adopts its reasoning and examines whether the submitted record warrants the requested operation within stated scope.
- **Terminology Separation:**
  - **Standing Mark Service:** The product and evaluation doorway (`POST /v1/evaluate`). Payment buys the examination, never a favorable outcome.
  - **Positive Standing Mark (`finding_disposition: "POSITIVE_STANDING_MARK"`, `outcome: "ESTABLISHED"`):** The favorable signed outcome when warrant is established within stated scope.
  - **Negative Standing Finding (`finding_disposition: "NEGATIVE_STANDING_FINDING"`, `outcome: "NOT_ESTABLISHED"`):** The signed outcome when warrant is not established, recording what was examined, which check or Named Failure triggered, the **Smallest True Move** (`INQUIRE` or `INFORM`), and the missing warrant.

## 2. The Standing Mark Record Contract (`schemas/standing-mark-record-contract-v1.json`)

Every signed Standing Mark Record (`WHP-STANDING-MARK-v1` over `WHP-JCS-I1` canonical JSON using `Ed25519`) binds four mandatory evidentiary structures inside the signed payload:

1. **Mechanical Object Binding (`object_binding`):**
   - Binds `submitted_bytes_sha256` (exact SHA-256 of the canonicalized submitted material), `examined_question`, `examination_scope`, `requested_operation`, `governing_canon_version` (`"7.0.0"`), `governing_canon_sha256`, `finding_disposition`, and `outcome`.
   - Receiving systems verify this mechanically via `verifyObjectBoundStandingMark()`: if the received material differs by 1 byte from `submitted_bytes_sha256`, verification fails with `OBJECT_DIGEST_MISMATCH`.
2. **Submission Completeness & Inventory (`completeness`):**
   - Records `submitter_completeness_declaration` and `supplied_materials_inventory`, paired with the explicit limitation: *"A completeness declaration records the submitter's assertion and the inventory of materials supplied to the examination; it cannot prove that undisclosed documents, side agreements, or adverse records do not exist outside the submitted packet."*
3. **Reproducibility & Model Provenance (`examination_provenance`):**
   - Records `reproducibility_class` (`DETERMINISTIC_RULE_EVALUATION`, `SINGLE_MODEL_JUDGMENT_WITH_DETERMINISTIC_STRUCTURAL_FLOOR`, or `REPEATABLE_UNDER_STATED_CONDITIONS`), `model_provider`, `model_id`, `temperature`, `governing_text_sha256`, `system_prompt_sha256`, `protocol_sha256`, and `examined_at`.
   - Preserves the exact provenance of a particular examination without pretending that stochastic LLM prose is timeless certification.
4. **Data-Handling Disclosure (`data_handling`):**
   - Explicitly states `inference_provider`, `transmitted_to_external_provider`, `transmitted_fields`, `storage_policy`, `retention_policy`, `training_use_policy` (`PROHIBITED`), and `deletion_policy`.

## 3. Canonical Endpoints & MCP Tools (`VerifyMCP` Compliant)

- **Single Evaluation Door:** `POST https://api.wheelerhubbellpublishing.com/v1/evaluate` (1.00 USDC on Base `eip155:8453` to `0x1050eddd8282623b0c263ed6bdbd42370bbc28d3` via `x402-v2`).
- **Streamable HTTP MCP Server:** `POST https://api.wheelerhubbellpublishing.com/mcp` (All 5 tools declare full `inputSchema`, `outputSchema`, and request/response `examples`):
  1. `whp_evaluate` — Submit material through `/v1/evaluate` and receive the signed Standing Mark Record.
  2. `whp_authorize_x402_transaction` — Pre-settlement evidence gate for autonomous `x402` agent-to-agent transactions.
  3. `whp_retrieve_result` — Retrieve a completed Standing Mark Record by `purchase_id` at zero second charge.
  4. `whp_recover_purchase` — Recover a settled Standing Mark Record by `purchase_id` at zero second charge.
  5. `whp_get_contract` — Inspect the live wire contract, data-handling facts, and Developer Integration Rule at zero charge.
- **Live Wire Contract:** `GET https://api.wheelerhubbellpublishing.com/v1/contract`
- **Standing Discovery Index:** `GET https://api.wheelerhubbellpublishing.com/.well-known/whp-standing.json`
- **Capability & Key Resolution:** `GET https://api.wheelerhubbellpublishing.com/.well-known/standing-capability.json`

## Public developer access

- Machine channel: https://api.wheelerhubbellpublishing.com/machine/channel.json
- Agent journey: https://api.wheelerhubbellpublishing.com/docs/agent-to-agent-journey.md
- Guide: https://api.wheelerhubbellpublishing.com/docs/
- SDK downloads and integrity hashes: https://api.wheelerhubbellpublishing.com/sdk/manifest.json
- Receiver boundary and local conformance: https://api.wheelerhubbellpublishing.com/docs/receiver-boundary.md
- Receiver requirement schema: https://api.wheelerhubbellpublishing.com/machine/requirement.schema.json
- Independent receiver guide: https://api.wheelerhubbellpublishing.com/docs/receiving-party-quickstart.md
- Echo challenge extensions in payment envelopes for facilitator discovery.