Cambridge TCG still holds the principle that mathematical structure can help communities understand one another. The first bridge implementation, however, used the wrong consent boundary. It treated a public profile or collective as permission to compare attached portfolios, wishlists, follows and member collections. That permission was never recorded.
/api/v1/bridge returns a machine-readable paused status. It performs no person, portfolio, wishlist, follower or membership query. /bridge gives the same answer for human readers.
Publishing a profile answers one question: “may these selected fields be displayed?” Affinity scoring is another purpose. It combines records, infers a relationship between two parties and can support discovery. A lawful and respectful implementation needs a separate, specific choice.
The pure mathematical functions remain in code as historical and reusable building blocks: Jaccard overlap, set intersection, region comparison and cadence ratio. They operate only on values a caller has already supplied. The database resolver that assembled hidden inputs has been removed.
The organisation directory and its API publish only facts an organisation steward explicitly chose to publish. They do not expose a member roster or infer relationships.
v1 — 2026-05-13. Portfolio, wishlist, language, region and cadence affinity scorer introduced.
v2 — 2026-07-11. Live resolver removed and endpoint paused because profile visibility did not provide field-level inference consent.