adapter-scaffold

You isolate vendor SDK quirks by defining a narrow adapter interface that masks vendor behavior behind a strict boundary. This preserves the shared ClearIntent authority contract while preventing vendor-specific logic from leaking into core workflows.

Integration adapters should return typed success, degraded, and failure states. Returning these specific result states ensures governance workflows can accurately track authority contracts and handle vendor boundary exceptions consistently.

No, you cannot redefine intent, policy, risk, receipt, or audit shapes locally. Adapters must consume shared contract and core types directly to maintain alignment with the ClearIntent authority contract across all integration boundaries.

Yes, adapter scaffolding supports signer hardware and ENS integration workflows. It automates adapter creation and validation across design, implementation, and review phases for these specific vendor boundaries within ClearIntent environments.

You should update provider docs, roadmap, decisions, and changelog whenever claims about the adapter change. Keeping these documents current ensures the vendor boundary remains transparent and the integration state is accurately tracked.

Defining a narrow adapter interface before implementation isolates vendor behavior while preserving the shared ClearIntent authority contract. This practice prevents vendor SDK quirks from contaminating core types and ensures consistent typed result states.