Posts 1 and 2 in this series explained the problem and showed what the connector code looks like before SYNAPSE. This post skips straight to showing it working. Open the live demo → What you are looking at The demo runs a three-model legal document pipeline: A named entity recognition model extracts parties, jurisdictions, and dates from a contract clause An obligation classifier assigns each entity a role — licensor, licensee, jurisdiction A compliance scorer checks the obligations against a GDPR policy Each model was built by a different team. Each one expects a completely different input format and produces a completely different output format. In a standard pipeline, you would write custom connector code between every model pair — and maintain it every time any model updates its schema. In the demo, there is no connector code. There are adapter functions. The one thing to watch for When Hop 2 appears, look at the left panel — the native input the classifier receives from its ingress adapter.…