# omp-spt is an OMP-native adapter

Status: accepted (2026-07-14)

omp-spt supports OMP integration only. Its product surfaces are native OMP endpoints and daemon-driven OMP roles; the inherited Claude Code plugin, hooks, injection machinery, ccs integration, Claude-specific requirements/tests, and former RPC bridge are lineage rather than supported compatibility surfaces. Keeping either alternate harness path would make multiple lifecycle contracts share one adapter identity and had already produced wrong-adapter setup and update behavior, so the port uses a clean OMP-native cutover instead.

The same cutover applies to traceability: the active requirement registry
contains OMP-observable contracts only. Claude-specific requirements are
retired rather than generalized or kept active, because OMP evidence cannot
prove a contract whose stated behavior depends on Claude hooks, ccs, or the
Claude plugin.