AWS-LC

PATHS: resolve bundled references/ and assets/ from the activated skill directory. Resolve source/build/install paths separately in the target project.

1. Select the boundary and revision

1. CLASSIFY: source build | direct C/C++ integration | OpenSSL migration/upgrade | OpenSSL 3 provider | FIPS deployment requirement | cross-compilation.
2. RECORD the exact AWS-LC tag/commit, target OS/architecture, compiler, static/shared choice, install prefix, and consuming application's dependency graph. Preserve the project's existing pin; choose a reviewed release for a new integration and update it deliberately.
3. READ the selected revision's BUILDING.md, INCORPORATING.md, public headers, and release notes. The authored baseline is v5.12.0, not a claim about the latest release. Read the AWS overview for portfolio context, not build flags or validation authority.
4. FIPS requirement -> READ references/fips.md before choosing a source revision or compiler. Direct API compatibility, a FIPS build, service approval, and CMVP validation are separate claims.
5. Source/toolchain/cross-compilation -> READ references/build.md.
6. Direct linkage or migration/upgrade -> READ references/integration.md.
7. OpenSSL 3 fetch/provider APIs -> READ references/provider.md. Keep application translation units on OpenSSL's headers; direct AWS-LC linkage is a different arrangement.

DONE: selected route, immutable revision, toolchain, artifact layout, and required runtime behavior are explicit.

2. Build without changing the host crypto library