CSIDH and CTIDH

Step 1: Fix the construction and security contract

1. CLASSIFY CSIDH | CTIDH | dCSIDH/dCTIDH | class-group action | NIKE integration | parameter review | constant-time implementation | fault-hardening | optimization study.
2. IDENTIFY exact paper/specification revision, source commit/archive, parameter set and prime, secret-exponent distribution, public-key encoding, action algorithm, validation algorithm, attack model, protocol role, target platforms, and claimed classical/quantum security.
3. READ references/status-parameters.md before selecting parameters or making security/standardization claims.
4. KEEP CSIDH-family commutative group actions separate from SIDH/SIKE, signature schemes, and generic supersingular-isogeny constructions. SIDH/SIKE breaks neither prove nor disprove CSIDH security.
5. TREAT every CSIDH/CTIDH parameter and implementation as a research artifact unless a separately reviewed deployment profile establishes otherwise; never call it NIST/IETF standardized or certified.
6. STOP when the protocol leaves construction, parameter tuple, public-key validation, transcript/KDF, or attack-cost model implicit.

Completion: every key/action binds one exact construction, implementation revision, parameters, validation algorithm, protocol, and dated security model.

Step 2: Inspect the project boundary

RUN from the repository root:

python3 scripts/inspect-project.py --root . --json