The current v0.1.0 codebase is a research prototype and deterministic local simulator. It is not a production security boundary.

Security-relevant reports may include:

• approval-binding bypass;
• state-machine transition bypass;
• duplicate mutation not detected by the evaluator;
• unsafe automatic retry after unresolved ambiguity;
• idempotency-key payload mismatch accepted;
• evidence corruption or misleading invariant classification;
• accidental inclusion of credentials, personal data, or production endpoints.

Do not publish secrets or exploit details in a public issue. Use GitHub private vulnerability reporting when available. Otherwise, open a minimal issue requesting a private contact channel without including sensitive details.

TEST_SIGNING_KEY is intentionally public and explicitly marked as a non-production test fixture. It must never be reused as a real secret.

A passing scenario does not prove production exactly-once execution, cryptographic integrity, distributed safety, or secure integration with an arbitrary external service.