# HeadlessDomains EPP Gateway Conformance Checklist

Version: 0.1
Updated: 2026-06-11
Ready for TCP gateway: `False`
Ready for EPP OT&E: `False`

## Summary

Mapped for a future EPP gateway, but not ready for EPP OT&E until transport, XML, session lifecycle, and EPP evidence are implemented.

## Implemented Checks

- `command_mappings_complete`: EPP command mappings point at the HTTP registrar API and internal registry service commands.
- `error_mapping_shared`: The registrar error catalog includes HTTP status, EPP result code, EPP result label, and retryability.
- `poll_mapping_defined`: Audit events and pending backend work are mapped to future EPP poll messages.
- `idempotency_mapping_defined`: EPP clTRID maps to the internal registry service idempotency_key.

## Missing Checks

- `tcp_tls_server`: TCP/TLS EPP server process is not implemented.
- `xml_parser_serializer`: EPP XML parser/serializer is not implemented.
- `session_lifecycle`: Registrar greeting, login, session state, and logout are not implemented.
- `epp_ote_suite`: EPP OT&E fixtures, credentials, sample XML, command logs, and evidence archive are not implemented.

## Next Build Order

1. Create separate headlessdomains-epp-gateway service skeleton.
2. Add TCP/TLS listener, greeting, login, logout, and session lifecycle.
3. Parse and serialize EPP XML for mapped domain commands.
4. Route parsed commands into the internal registry service contract.
5. Add EPP OT&E fixtures, credentials, sample XML, logs, and evidence archive.