Identity primitives before integrations

Stack an integration on top of fragile identity and you carry the fragility into every downstream system. Platforms solve identity internally — reasonably well, within their walls — and then spill it at their seams. The point where your Gmail meets your Obsidian meets your Slack meets your CRM is where the model breaks and every connector becomes a pile of workarounds.

The answer isn't better connectors. It's identity primitives that survive crossing a seam. A representation of *who you are and what you're trying to do* that the next surface can read without re-establishing the entire context from scratch. Integrations then become composable instead of combinatorial.

What this lets stakeholders do: stop rebuilding the same identity scaffolding in every tool. Trust that an action taken in one surface is attributable and traceable in another. Compose new tools into the stack without re-signing every social contract.

What's still open: what's the canonical identity primitive that both respects self-sovereignty and survives the platform layer's refusal to cooperate?