What problem does it solve? Building onchain compliance with Chainlink ACE requires navigating two distinct scopes: self-deployed open-source contracts in the smartcontractkit/chainlink-ace repository and the managed ACE Platform with its Coordinator and Reporting APIs. This Skill routes questions to the correct source of truth, preventing confusion between OSS contract capabilities and managed Platform/Beta limitations. ## Core Features & Use Cases - Policy Chain Design: Recommends PolicyEngine configurations, policy ordering, extractors, mappers, and terminal outcomes (PolicyRejected, Allowed, Continue) for compliance rules. - Cross-Chain Identity Guidance: Explains CCIDs, IdentityRegistry, CredentialRegistry, and KYC/AML credential patterns without storing PII onchain. - Scope Separation: Distinguishes self-deployed Foundry-based contracts under BUSL-1.1 from managed Platform features like the Coordinator API, Reporting API, and auditor workflows. - Use Case: A developer building an ERC-3643 regulated token asks which policies to attach. The Skill recommends a policy chain with restrictive checks first, names required extracted parameters, and flags licensing and audit requirements before mainnet deployment. ## Quick Start Ask the assistant to design a Chainlink ACE policy chain for a KYC-gated ERC-20 token and explain which contracts to deploy.
