Add ISM-X Authy v4 (Open Cutline): FastAPI gateway + SQLite + Ed25519

[Freeky7819]

What’s inside

• New authy_v4_open/ module:
  • FastAPI gateway: /issue, /verify, /revoke, /did, /healthz
  • Compact Ed25519 token (header.payload.signature)
  • SQLite audit + revocations (auto-init), file-based keypair
  • Dockerfile + docker-compose, .env.example
  • openapi.yaml, README.quick.md, RELEASE_NOTES_v4_open.md
• Root .gitignore updated to exclude local secrets/keys

Security notes

• No HSM/TPM, no OIDC (feature flags OFF)
• Keys are local/dev; rotate by deleting authy_v4_open/keys/ and restarting
• Set METRICS_SECRET to a random 64-hex string in .env

Context

This PR integrates the ISM-X Authy v4 (Open Cutline) used by our MCP fork. It’s a safe public demo; enterprise features (Vault/TPM, OIDC, approvals, SIEM) live in the internal repo.

[Limeload]

@Freeky7819 These additions bring in a strong security model, but right now the project isn’t at a stage where an external attestation layer aligns with our roadmap.
I’d love to revisit this later as an optional plugin or enterprise extension, once the base MCP server is fully stable.

POV: Really appreciate your enthusiasm, but I’d like to keep the main repo focused on stable, educational use first.

[Freeky7819]

Thanks, Shraddha, totally understood and I fully agree with keeping the core stable and educational for now.

I’ll keep maintaining the ISM-X Attestation Bridge as an optional security extension, so that once the MCP core reaches the “plugin-ready” stage, we can easily integrate it as a drop-in companion.

In the meantime, I’ll make sure the branch stays aligned with upstream (no core interference) and document the modular hooks that could be exposed later.

Appreciate your thoughtful feedback and openness — and I’m really glad this direction can still inform future architecture.

[Limeload]

@Freeky7819

Sounds great, Damjan — really appreciate your collaboration and the care you’re taking to keep things modular and aligned.
Thanks again for contributing thoughtfully — this setup will make it much easier to evolve the project when we’re ready for plugin support.