Typed Persona REST Adapter and JSON:API Envelope

Overview

Keep transport, Persona resource envelopes, and domain decisions separate. The adapter should preserve raw identifiers and metadata, tolerate new resources and fields, and expose explicit mutation evidence rather than flattening every response into a brittle model.

Prerequisites

• Endpoint inventory and approved API version
• Language runtime with HTTP, JSON, and constant-time comparison support
• Domain boundary defining what may contain PII

Instructions

Step 1: Define the transport core

Centralize the API base, bearer header, dated version, timeouts, request IDs, and safe telemetry. Do not retry mutations blindly.

Step 2: Model JSON:API generically