Falcon and FN-DSA

Step 1: Fix the algorithm contract

1. CLASSIFY library integration | API/protocol design | Falcon implementation | provisional FN-DSA evaluation | security review | vector harness | Falcon-to-FN-DSA migration.
2. TREAT FN-DSA as an upcoming post-quantum signature scheme currently being defined by NIST and based on Falcon; FIPS 206 is still in development.
3. IDENTIFY the exact scheme/version, parameter set, signature encoding, pure/prehash behavior, context/domain binding, key representation, randomness owner, target platforms, side-channel boundary, and required interoperability peers.
4. READ references/status-parameters.md before choosing names, sizes, encodings, or claiming FN-DSA/FIPS behavior.
5. LABEL deployed Falcon v1.2 as Falcon. Label pornin/c-fn-dsa output as provisional FN-DSA tied to its exact commit, never as final or FIPS-conformant FN-DSA.
6. STOP when the protocol leaves the algorithm identifier, parameter set, signature format, message preprocessing, or encoding implicit.
7. ROUTE standardized vector acquisition to nist-cavp, generic invalid-input corpus work to wycheproof, and broad post-quantum migration policy outside this skill.

Completion: every serialized key/signature and signing request binds one exact scheme, version, parameter set, format, and message-processing mode.

Step 2: Inspect the implementation boundary