License key validation limits
A teammate wants an AI agent to implement a license-key generation and validation scheme in Rust for your desktop product: keys that encode the tier and expiry and can be verified offline. When would you NOT delegate the design to the agent, and what failure modes make AI the wrong tool for the crypto-bearing parts?
Implement
review_license_key_scheme(decisions: list[str]) → list[str]Examples
in
[["primitive=ed25519","private_key_location=build_server","signature_compare=constant_time","expiry_check=enforced","cli_parsing=agent","key_encoding=agent"]]out[]in
[["primitive=hmac_sha256","private_key_location=binary","signature_compare=equality","expiry_check=enforced"]]out["keep-private-key-out-of-binary","own-primitive-asymmetric-signature","use-constant-time-compare"]in
[["cli_parsing=agent","key_encoding=base32"]]out["enforce-expiry-on-verify","keep-private-key-out-of-binary","own-primitive-asymmetric-signature","use-constant-time-compare"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 20 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.