Public product lead: Paybond Kit — proof-gated release and receipts for AI agents. Harbor, Ledger, and Signal remain real runtime surfaces behind Kit; they are architecture and deep-dive docs, not co-equal public heroes.
The same vocabulary is defined in code at apps/admin/lib/public-content/product-surfaces.ts and reused across the public site, docs, and llms.txt.
Customer-owned rails (prefer Stripe Connect / x402) move funds. Paybond applies policy and binds signed completion evidence to proof-gated release/refund and portable receipts — it does not claim to settle, hold, or custody customer money.
Surfaces at a glance
| Brand | Subtitle | One-line job | Route | Marketing | Stack order |
|---|---|---|---|---|---|
| Kit | Developer SDK | Release or refund on signed completion evidence — one signed receipt | /kit | Primary | 1 — integrates |
| Harbor | Evidence evaluation | Signed intents, evidence evaluation, release/refund | /harbor | Secondary / docs | 2 — evaluates |
| Ledger | Platform provenance | Append-only signed history for audits and exports | /ledger | Secondary / docs | 3 — record |
| Signal | Platform standing | Optional standing derived from verified outcomes | /signal | Secondary / docs | 4 — build standing |
Lifecycle (architecture)
When you need the internals, read the stack top to bottom:
Kit integrates → Harbor evaluates → Ledger records → Signal builds standing
- Kit — Developer SDK: integrate your agent runtime with Paybond policy middleware, sessions, and evidence hooks. Authorization is a capability you invoke through Kit — not something the SDK performs on its own.
- Harbor — Evidence evaluation: run the signed intent lifecycle — intents, evidence checks, and deterministic release or refund decisions on customer-owned rails.
- Ledger — Platform provenance: record an append-only, signed history for audits and exports.
- Signal — Platform standing: optional portable receipts and standing from verified outcomes.
Stack diagram
Agent runtime
│
▼
Kit
Developer SDK
│
▼
Harbor
Evidence evaluation
│
▼
Ledger
Platform provenance
│
▼
Signal
Platform standing
How this maps to runtime services
Public messaging leads with Kit. Harbor, Signal, and Ledger pages describe capabilities that stay behind the SDK; Gateway remains the authenticated API front door in API documentation rather than a marketing surface.
For the Kit-first platform picture, start with Paybond platform overview.