goldenmatch-kg drops goldenmatch in as that resolve stage, wherever a framework
exposes a seam for it.
The three integrations
Why a separate package
Each framework wants a different object shape, and each pulls a heavy dependency tree. Keeping the adapters here means GoldenMatch itself stays framework-agnostic and dependency-light, while the integrations can track each framework’s API on their own schedule.Choosing between this and GoldenGraph
- Adopting an existing KG pipeline? Use
goldenmatch-kg— it improves the resolve stage of a pipeline you already have. - Building the pipeline yourself? Use GoldenGraph, which owns the whole path and stores the result bi-temporally.