Practical guidance for implementing Portable Trust Infrastructure (PTI) v1.0 as a producer, consumer, or registry operator. This guide is informative; normative requirements appear in the Specification v1.0.
- Read Key concepts and Glossary
- Map your data sources to trust contexts and event types
- Identify lawful basis and consent requirements with legal stakeholders
- Choose conformance profile (
pti-producer/v1, pti-consumer/v1, or both)
- Document entity-to-
pti_id resolution strategy
- Define idempotency key templates per business action
- Obtain sandbox credentials separate from production
- Implement Registry resolve + Exchange ingest (producers) or Lookup search/generate (consumers)
- Wire correlation ID logging end-to-end
- Golden-path ingest and lookup
- Idempotent replay
- Authorization denial paths (
PTI-403x)
- Version negotiation against
/capabilities
- Limited context enablement
- Monitor validation error and match confidence distributions
- Establish dispute and correction runbooks
- Enable additional contexts and tiers per contract
- Federation or multi-region routing if required
- Operational dashboards for signal freshness and lookup latency
| Item | Producer | Consumer |
|---|
| RFC 2119 error handling | ✓ | ✓ |
schema_version on all payloads | ✓ | ✓ |
X-PTI-Version pinned | ✓ | ✓ |
| Idempotency keys | ✓ | , |
| Purpose code on lookups | , | ✓ |
| Consent flow when required | , | ✓ |
| Explainability preserved in UI | , | ✓ |
| Correction/retraction support | ✓ | , |